Should be fixed now, gnome-screensaver now passes the gnome keyring
environment variable to pam
** Changed in: gnome-screensaver (Ubuntu)
Sourcepackagename: pam-keyring => gnome-screensaver
Status: Confirmed => Fix Released
--
pam-keyring incompatible with gnome-password
https://bugs.laun
The most problematic symptom:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/92032/
...has been fixed in a different way. So this bug is no longer as
important, and arguably does not need to be fixed at all...
Thanks!
--
pam-keyring incompatible with gnome-password
https://bugs.
I will contact upstream or try to make a patch.
For a tighter integration you must wait feisty +1 (I hope)
** Changed in: pam-keyring (Ubuntu)
Importance: Undecided => Low
Status: Needs Info => Confirmed
--
pam-keyring incompatible with gnome-password
https://bugs.launchpad.net/bugs/1
Thank you for the suggestion. Yes, I tried adding "@include common-
pamkeyring" to /etc/pam.d/gnome-screensaver. It does not work because
pam_keyring.so spawns a new instance of gnome-keyring-daemon instead of
unlocking the running daemon already present.
In my opinion, this should not only work
did you try to add
@include common-pamkeyring in the file /etc/pam.d/gnome-screensaver ?
I haven't try since suspend don't work on my laptop
** Changed in: pam-keyring (Ubuntu)
Status: Unconfirmed => Needs Info
--
pam-keyring incompatible with gnome-password
https://bugs.launchpad.net/b
