我的系统日志充满了这些消息
Nov 22 13:14:36 virtuale-2 gnome-keyring-daemon[2413]: couldn't create socket directory: /root/.cache/keyring-CI8ZC1: Permission denied
Nov 22 13:14:36 virtuale-2 gnome-keyring-daemon[2413]: couldn't bind to control socket: /root/.cache/keyring-CI8ZC1/control: Permission denied
Nov 22 13:14:40 virtuale-2 gnome-keyring-daemon[2421]: couldn't create socket directory: /root/.cache/keyring-LQDED1: Permission denied
Nov 22 13:14:40 virtuale-2 gnome-keyring-daemon[2421]: couldn't bind to control socket: /root/.cache/keyring-LQDED1/control: Permission denied
该进程不存在!
pgrep -a keyr
pgrep -a gnome
无法找到它来自哪里
grep -irl gnome-keyring-daemon /etc
怎么阻止呢?
答案1
长话短说- 添加到以inonly_if=xdm,gdm,kdm,sddm,lightdm,<your preferred DM>
结尾的行之后。[...] pam_gnome_keyring.so auto_start
/etc/pam.d/system-auth
它来自于(它并不真正属于的地方)pam_gnome_keyring.so
中的引用/etc/pam.d/system-auth
,而它又源自其他几个 PAM 配置文件,因此gnome-keyring-daemon
每次运行su
或时都会启动一个实例sudo
,例如:
[root@disclosure:~]# grep keyring /etc/pam.d/system-auth
-auth optional pam_gnome_keyring.so
-session optional pam_gnome_keyring.so auto_start
答案2
找到了解决方法...
removepkg gnome-keyring-daemon
但我更喜欢禁用它并知道谁尝试启动此过程。
答案3
@elbarna 的建议对我不起作用,但removepkg gnome-keyring-40.0-x86_64-1
确实有效。