我在我的KDE等离子体(Arch )中使用。我修改了:
/etc/pam.d/login
auth required pam_securetty.so
auth requisite pam_nologin.so
auth include system-local-login
auth optional pam_gnome_keyring.so
account include system-local-login
session include system-local-login
session optional pam_gnome_keyring.so auto_start还包括:
/etc/pam.d/passwd
#password required pam_cracklib.so difok=2 minlen=8 dcredit=2 ocredit=2 retry=3
#password required pam_unix.so sha512 shadow use_authtok
password required pam_unix.so sha512 shadow nullok
password optional pam_gnome_keyring.so并添加到我的.xintrc中(我使用startx启动等离子,默认情况下是多user.Target)。
eval $(/usr/bin/gnome-keyring-daemon --start --components=pkcs11,secrets)这是可行的,但我的日记上有警告:
lis 11 16:57:47 maciexhome gnome-keyring-daemon[815]: asked to register item /org/freedesktop/secrets/collection/login/10, but it's already registered
lis 11 16:57:52 maciexhome gnome-keyring-daemon[815]: asked to register item /org/freedesktop/secrets/collection/login/10, but it's already registered
lis 11 16:57:53 maciexhome gnome-keyring-daemon[815]: asked to register item /org/freedesktop/secrets/collection/login/10, but it's already registered
lis 11 16:57:57 maciexhome gnome-keyring-daemon[815]: asked to register item /org/freedesktop/secrets/collection/login/10, but it's already registered这是我该担心的吗?
发布于 2019-12-14 10:20:53
如果您正在运行NextCloud,那么您描述的垃圾日志消息有一个错误报告。我得到他们在我的Fedora 29肉桂桌面也。使用nextcloud-client-2.6.1-1.fc29.x86_64。
它看起来是固定在Nextcloud上游(截至2019年12月7日),所以我们正在使用Fedora只是等待包装发布。
显然,客户端的v2.6.0没有表现出这种行为。他们正在确认v2.6.2有修复程序。
https://unix.stackexchange.com/questions/551609
复制相似问题