[SOLVED] Upgraded to Bookworm, now GNOME keyring dies--no access to stored SSH key passwords
DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Upgraded to Bookworm, now GNOME keyring dies--no access to stored SSH key passwords
I now have two desktop systems running Bookworm with GNOME 43. The laptop was upgraded last month and I upgraded the desktop this past Sunday afternoon. I have been using the GNOME keyring applet to manage the SSH public key passwords I use as it prompts to save passwords and then lets me SSH to other hosts without out a password prompt.
Some time after the upgrade I wanted to SSH into one of the other systems on my LAN and was greeted with a password prompt for the corresponding public key that had prior been managed by the keyring applet. I noted differences in the running processes between the laptop where the keyring applet is still working and the desktop where it was not.
On an off-chance I cold booted this system and found the keyring applet was working as expected so I went on doing other things for a while. Then I tried again and was prompted for the public key's password. Uggh.
Right after rebooting the process list looked like this which mirrors the laptop:
It appears to me that gnome-keyring-daemon has been restarted for some reason. As a result PIDs 2037 and 3802 are terminated and also /run/user/1000/keyring/.ssh is no longer present along with the pkcs11 and ssh files in the same directory.
I noted in that report and not elsewhere that the system with the daemon shutting down is running snapd while the other is not. I've no idea if that is relevant to this issue but that is the major difference between the two systems other than other installed packages. Upgrading to 12.2 has not resolved this issue.
Maybefrom searching your title or "About 3,850" unrefined "results?"
Not the same. In my case the gnome-keyring-daemon shuts down in an hour or less after logging in. My SSH keys still work to all the other hosts, I just have to remember and enter the pass phrase.
You do clean out your browser Cache once in a while, don't you? I also found a lot of other helpful information with that search on our subject, for example managing or resetting.
The keyring is separate from the browser cache. My mention of Chromium is mostly tangential to the issue of the keyring daemon shutting down on the desktop while remaining running on the laptop through multiple suspend/resume cycles.
It seems a badly formed cron entry that matched text in the daemon command line was responsible for sending it the SIGTERM signal. Another project recommended the use of 'strace' to examine activity of a process for another project I was working on yesterday. This morning I decided to try it with the gnome-keyring-daemon process after a reboot and discovered the daemon was terminating at the top of each hour no matter how long, or short, of time it ran. I recalled that I had a cron entry that was calling 'pkill' at the top of each hour for an unrelated reason.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.