FS#30631 - [gnome-keyring] daemon started only when pam_gnome_keyring.so fails
Attached to Project:
Arch Linux
Opened by orbisvicis (orbisvicis) - Wednesday, 11 July 2012, 05:51 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 30 April 2013, 19:51 GMT
Opened by orbisvicis (orbisvicis) - Wednesday, 11 July 2012, 05:51 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 30 April 2013, 19:51 GMT
|
Details
Description:
. gnome-keyring-daemon starts only when pam_gnome_keyring.so fails - it should be the exact opposite . session management module prompts for a password - only the password management module should All the details are at: https://bbs.archlinux.org/viewtopic.php?id=144783 Additional info: * package version(s) extra/gnome-keyring 3.4.1-2 core/pam 1.1.5-4 |
This task depends upon
Aug 27 21:08:30 localhost gnome-keyring-daemon[576]: couldn't access conrol socket: /home/siam/.cache/keyring-HU3Q2k/control: No such file or directory
Aug 27 21:08:30 localhost gnome-keyring-daemon[577]: couldn't access conrol socket: /home/siam/.cache/keyring-HU3Q2k/control: No such file or directory
Aug 27 21:08:30 localhost gnome-keyring-daemon[579]: couldn't access conrol socket: /home/siam/.cache/keyring-HU3Q2k/control: No such file or directory
Aug 27 21:08:30 localhost gnome-keyring-daemon[582]: couldn't access conrol socket: /home/siam/.cache/keyring-HU3Q2k/control: No such file or directory
Edit:
After i updated my system today, my problem is solved. Perhaps this bug is fixed already?
https://bugzilla.gnome.org/show_bug.cgi?id=679892
https://git.gnome.org/browse/gnome-keyring/commit/?id=26a694b1a18a92580d211ec2d18803af0ad05d99
It should have become available in gnome-keyring 3.5.5. This can be closed.