Red Hat Bugzilla – Bug 356931
gnome-keyring-pam not working
Last modified: 2015-03-03 17:31:43 EST
Description of problem:
Even though I have set my keyring password to be the same as my login password I
still have to enter it twice (once at the gdm prompt and again the first time I
have to access something in my keyring).
Version-Release number of selected component (if applicable):
[maxx@ice ~]$ rpm -qa | grep gdm
[maxx@ice ~]$ rpm -qa | grep keyring
I have the exact same problem.
I upgraded from F7 to F8 and now evolution keeps asking for the keyring password.
The keyring password is the same as the login password. I checked every thread
on the mailing list, tried everything but it doesn't work.
I fixed my problem. The upgrade from F7 to F8 doesn't install pam keyring rpm. I
installed it, added appropriate lines in /etc/pam.d/gdm and now it works fine.
(In reply to comment #2)
> I fixed my problem. The upgrade from F7 to F8 doesn't install pam keyring rpm. I
> installed it, added appropriate lines in /etc/pam.d/gdm and now it works fine.
Should't it work without pam_keyring rpm? AFAIK, it should be obsolete as
gnome-keyring-pam should takeover this functionality since GNOME 2.20
I noticed that gnome-keyring-pam unlocks the 'login' keyring whereas the
applications were using the 'default' keyring. I changed the default to 'login'
and readded the keys but still no joy.
No, not AWOL. But as far as I can see, there's nothing broken with pam_keyring
per see. It needs to be installed manually and the lined added to the
/etc/pam.d/gdm, just like for F-7.
As was said, gnome-keyring-pam is supposed to take over, but unlocks the wrong
keyring. Maybe this discussion should be brought over to the mailing list to
discuss whether it's gnome-keyring-pam that needs to change, or
NetworkManager... I'll take a look at the problem now.
gnome-keyring-pam not working seems to be this:
pam_keyring works here on F-8, so I'm closing this WORKSFORME. As for
pam_keyring not being setup by default, that was a known problem:
#312531 appears to have been closed before Fedora 8 shipped, so I don't think
The bug title clearly states pam-gnome-keyring not working, and nowhere is
pam-keyring mentioned. I think the bug is just against the wrong component.
Maybe it should be reopened and assigned to the gnome-keyring component, since
it's clearly broken.
Well, I think the significant thing in #312531 is that Matthias Clasen disabled
the auot-unlock checkboxes. I wonder if they were ever turned back on (certainly
that is what is missing in F-8).
I agree though, this looks like a gnome-keyring problem.
Denis - any idea why it WORKSFORYOU but noone else? Are you running pure F-8, or
some rawhide packages as well?
Martin: you're right!, this is clearly filed against the wrong component. A more
active related bug seems to be:
Jonathan: yes, the no-autounlock patch is still present in the f-8 srpm. My
setup is working because I'm using pam_keyring, not gnome-keyring-pam.
Reopening and reassigning this bug to gnome-keyring.
Any progress on this bug?
Any update on this? If there is anything I can do to help please advise.
This is finally working for me on the F9 preview release. Also unlocks the ssh
keys automatically (seems to be integrated through policykit).
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here: