Every time I start evolution, I get a GNOME Keyring dialog asking me
to enter a password for the default keyring:

http://teasel.6gnip.net/~rah/gnome-default-keyring.png


According to gnome-keyring-manager, the login keyring contains a
password to unlock the default keyring:

http://teasel.6gnip.net/~rah/login-keyring.png

Le mercredi 03 juin 2009 à 11:43 +0100, Bob Ham a écrit :

Yes, but is the login keyring correctly unlocked upon login? Does it
have the same password as your account?

I don't see it anywhere, things seem to have been moved around again.

I wish gnome-keyring would stop getting in the way and asking
me to enter passwords.  It is caching about 5 passwords from
what I can tell and doesn't seem to be remembering ANY of them.
I have gnome-keyring and gnome-keyring-manager installed and
configured the best way I know how, but every time I go to
send a mail (through evolution) or login with ssh I get a
stupid prompt asking me to enter the #(A%&#A password again.

What must one do to get this package to work once and for all?
It's a pain in the arse trying to set things up so they should
work, having it work ONCE, thinking everything is OK, then
later getting a NEW prompt for password, google, research debian
bugs, rinse, repeat...

There seems to be a major disconnect between different components
on the system vis a vis password caching, because nothing is being
cached consistently.

It would appear that the login keyring is not unlocked upon login; the
"Keyring Manager" in GNOME's Administration menu won't allow access.

While trying to unlock the password for the login keyring, using the
same password as my account does not work.  Assuming that the login
keyring must have the same password as my account for correct operation,
this begs two questions:

1. Why is the password for the login keyring different from my account
password?
2. How can I set the login keyring's password to be the same as my
account?

Le mardi 04 août 2009 à 14:20 +0100, Bob Ham a écrit :

Probably because you changed your account password without changing the
password for the login keyring accordingly. Since 2.26.0-3 this is done
automatically.

You can change it manually from the keyring preferences in seahorse,
after which it should follow your account password now.

Cheers,

I've changed my account password and changed it back again.  I still
can't unlock the login keyring.  Here are some relevant versions I have
installed:

ii  gnome-keyring                                  2.26.1-1
ii  gnome-keyring-manager                          2.20.0-1
ii  libgnome-keyring0                              2.26.1-1
ii  libpam-gnome-keyring                           2.26.1-1
ii  seahorse                                       2.26.1-2
ii  seahorse-plugins                               2.26.1-1+b1

The preferences dialog in seahorse (accessed through the
Edit->Preferences menu option) doesn't contain any method of changing
passwords.

Likewise, the seahorse-preferences program (accessed through the
System->Preferences->Encryption and Keyrings system menu option) doesn't
contain any method of changing passwords.

Also, the GNOME Keyring Manager (accessed through the
System->Administration->Keyring Manager system menu option) doesn't seem
to contain any method of changing the password either.  I can't change
the password for the default keyring but the login keyring is
perpetually locked anyway.

How do I find the appropriate keyring preferences?

Aug 13 14:11:29 myrtle passwd[18139]: pam_unix(passwd:chauthtok): password changed for rah
Aug 13 14:11:29 myrtle passwd[18139]: gkr-pam: couldn't change password for 'login' keyring: 1

What is gkr-pam?  Why can't it change the password for the login
keyring?

Le jeudi 13 août 2009 à 13:09 +0100, Bob Ham a écrit :

This is because you need to sync the passwords first. The PAM keyring
module needs the old password to be able to set the new one.

Hmpf, looks like this was removed in 2.26, I don’t know why. It seems to
be fixed in 2.27, I’ll have a look.

Cheers,

There is an option to change the password in the context menu for
keyrings in 2.28.  However, it requires an old password for the keyring
and I don't know the password for the login keyring.

Le dimanche 15 novembre 2009 à 13:45 +0000, Bob Ham a écrit :

It is probably the login password you had at the time the login keyring
was created.

If you have forgotten this password, there is no way to recover it, so
you can just delete that keyring, it will be recreated.

Cheers,

I've deleted the login keyring.  I changed my account password and
changed it back again and the login keyring has been recreated and the
password for it matches my account password.

Unfortunately, the login keyring isn't unlocked when I log in to GNOME;
seahorse has an 'Unlock' option on the context menu for the keyring and
GNOME Keyring Manager shows the keyring is locked.  And I still get
asked to enter the password for the default keyring when starting
evolution.

Le lundi 16 novembre 2009 à 22:23 +0000, Bob Ham a écrit :

Which way are you logging in? Are you using GDM?

Are any keyring-related logs in /var/log/auth.log?

I am using GDM and I'm logging in by typing my username and password
into the greeter.
Nov 16 22:20:11 myrtle gdm[4707]: pam_unix(gdm:session): session opened for user rah by (uid=0)
Nov 16 22:20:11 myrtle gdm[4707]: pam_ck_connector(gdm:session): nox11 mode, ignoring PAM_TTY :0
Nov 16 22:20:12 myrtle seahorse-daemon[7063]: init gpgme version 1.2.0
Nov 16 22:20:12 myrtle gnome-keyring-daemon[7054]: mount_added: assertion `path' failed
Nov 16 22:20:24 myrtle gnome-keyring-ask: could not grab keyboard: 3
Nov 16 22:20:43 myrtle last message repeated 3 times
Nov 16 22:22:39 myrtle gnome-keyring-ask: could not grab keyboard: 3

What's happening about this bug?  I still have to type my password in to
unlock the default keyring.  Every time I log in.  Every time.

Dear all,

I am experiencing the same with gnome keyring 3.4.1-5 under xfce. I have turned
off Launch GNOME services at startup option in Session and Startup config. When
i start firefox I am promted for password to my default keyring which
effectively means that login keyring wasn't unlocked during startup.

I think it is a result of improper configuration. Please see this bugreport
filled for ubuntu:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1022322

If I am to quote from the report author:

The file causing the problem is /etc/xdg/autostart/gnome-keyring-pkcs11.desktop
.. The line
OnlyShowIn=GNOME;Unity
should be changed to
OnlyShowIn=GNOME;Unity;XFCE

I have tried the suggested and the result is positive.

Hope it helps.

Best regards

Jan Korous

I have three systems upgraded from previous stable to "Jessie", all
exhibit this behavior.  Using "kdm" and "kdm-gdmcompat".  Two of the
systems share a common /home via NFS, so I thought it might be because
some part of the login process runs as root and has limited access to
files on NFS, but the most-recent system is a laptop with local /home.

Possibly-relevant contents of /var/log/auth.log...

Jul 28 05:03:09 wirenth gnome-keyring-daemon[1659]: couldn't access
control socket: /run/user/1024/keyring/control: No such file or directory
Jul 28 05:03:09 wirenth gnome-keyring-daemon[1658]: couldn't access
control socket: /run/user/1024/keyring/control: No such file or directory
Jul 28 05:03:09 wirenth gnome-keyring-daemon[1656]: couldn't access
control socket: /run/user/1024/keyring/control: No such file or directory
Jul 28 05:03:09 wirenth gnome-keyring-daemon[1665]: Gkm: using old
keyring directory: /home/davidl/.gnome2/keyrings
Jul 28 05:03:09 wirenth gnome-keyring-daemon[1665]: Gkm: using old
keyring directory: /home/davidl/.gnome2/keyrings
Jul 28 05:03:15 wirenth polkitd(authority=local): Registered
Authentication Agent for unix-session:1 (system bus name :1.39
[/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1], object
path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Jul 28 05:03:24 wirenth gcr-prompter[1927]: bus acquired:
org.gnome.keyring.SystemPrompter
Jul 28 05:03:24 wirenth gcr-prompter[1927]: Gcr: registering prompter
Jul 28 05:03:24 wirenth gcr-prompter[1927]: bus acquired:
org.gnome.keyring.PrivatePrompter
Jul 28 05:03:24 wirenth gcr-prompter[1927]: Gcr: received BeginPrompting
call from callback /org/gnome/keyring/Prompt/p2@:1.8
Jul 28 05:03:24 wirenth gcr-prompter[1927]: Gcr: preparing a prompt for
callback /org/gnome/keyring/Prompt/p2@:1.8
Jul 28 05:03:24 wirenth gcr-prompter[1927]: Gcr: creating new
GcrPromptDialog prompt
Jul 28 05:03:24 wirenth gcr-prompter[1927]: Gcr: automatically selecting
secret exchange protocol
Jul 28 05:03:24 wirenth gcr-prompter[1927]: Gcr: generating public key
Jul 28 05:03:24 wirenth gcr-prompter[1927]: Gcr: beginning the secret
exchange: [...]
Jul 28 05:03:24 wirenth gcr-prompter[1927]: Gcr: calling the PromptReady
method on /org/gnome/keyring/Prompt/p2@:1.8
Jul 28 05:03:24 wirenth gcr-prompter[1927]: acquired name:
org.gnome.keyring.SystemPrompter
Jul 28 05:03:24 wirenth gcr-prompter[1927]: acquired name:
org.gnome.keyring.PrivatePrompter
Jul 28 05:03:24 wirenth gcr-prompter[1927]: Gcr: returned from the
PromptReady method on /org/gnome/keyring/Prompt/p2@:1.8
Jul 28 05:03:24 wirenth gcr-prompter[1927]: Gcr: received PerformPrompt
call from callback /org/gnome/keyring/Prompt/p2@:1.8

I'm using lightdm.  The keyring is used by evolution.  The keyring
password is the same as my login password in /etc/shadow.  I haven't
touched the stuff in /etc/pam.d, and AFAICT it looks fine (ie,
pam_gnome_keyring.so is mentioned everywhere it should be).

I was never able to get to get the keyring to unlock automatically in
Jessie.

A week ago I got a new laptop and did a fresh stretch install and was
hoping the problem would disappear.  The situation is unchanged - when
evolution starts, gcr prompts for keyring password and I have to re-
enter it.

If it would help, I can try to verify I can reproduce this in a kvm
container from a fresh sid install.

Dear Maintainer,

The problem still exists here in all its glory just as it was described in 2009 now,
after sixteen years, after upgrading to Trixie, and in Seahorse (which hides its name)
version 47.0.1-2. The only difference is that this time it applies to the fingerprint
login. (I followed the advice here to right-click on my login keyring in Gnome's
“Passwords and Keys” window and changed my login password there, then finally it
synchronised.) It seems that fingerprints are not part of the login keyring. I deleted and
re-entered my fingerprints but the situation remained the same.

   * What led up to the situation?

I log in using a fingerprint in the Greeter. A dialogue window forces me to enter my login
password even though I just logged in without an error.  But even then, when I call
Evolution, I cannot access my calendars because Evolution cannot access the passwords I
entered when I created each calendar's entry in Evolution. I have to not just quit
Evolution but

evolution --force-shutdown
pkill --echo keyring

and start Evolution again, which causes a dialogue window to appear that asks me for my
login password again. Then I can finally access my calendars.