Since a few days ago my Gnome-keyring daemon hasn't been starting up properly.

After logging in:

ps aux | grep keyring
user       3496  0.0  0.0 214408 15800 ?        SLl  13:30   0:00 /usr/bin/gnome-keyring-daemon --daemonize --login

Apps complain about not being able to access the keyring (and fail to do so), some shortcuts are very slow CTRL+ALT+T for terminal or Print screen can both take up to a minute between key press and action)

Seahorse does not show the login keyring

$ /usr/bin/gnome-keyring-daemon
$ ps aux | grep keyr
user       3496  0.0  0.0 214408 15800 ?        SLl  13:30   0:00 /usr/bin/gnome-keyring-daemon --daemonize --login
user       8524  0.1  0.0 211004 12468 pts/5    SLl  13:38   0:00 /usr/bin/gnome-keyring-daemon

Then, as soon as an app wants to access I get the keyring password prompt. Once unlocked, the keyring works properly.

I had a look to startup apps for my session and I only have one command that is relevant:

/usr/bin/gnome-keyring-daemon --start --components=ssh

I added /usr/bin/gnome-keyring-daemon to startup apps, but it will prompt for the keyring password after each login, which wasn't happening before.

Any idea on what happened and how to fix this please?

  • 3
    I actually wonder if an update might have caused this. I am experiencing the exact same issue, and I have just about exhausted every single resource I have just shy of doing a complete reinstall. I hope that someone might have figured this one out. I am able to get the daemon to start up OK, but I cannot get the keyring to unlock at log in time. – Terrance Mar 31 '17 at 2:53
  • 3
    Strangely this is affecting me since today on 16.04. – Byte Commander Jun 3 '17 at 22:14
  • I have the same problem on a gnome-shell (from Ubuntu Gnome 16.04) install. Started recently. So it seems not unity-related... – Rmano Jul 26 '17 at 11:22
  • 1
    @ByteCommander 's method solved the problem for me. Thanks... – Rmano Jul 26 '17 at 13:48

I'm facing the same issue,

as an temporary solution try to run the following after login

gnome-keyring-daemon --start --replace --foreground --components=secrets,ssh,pcks11

When I'm doing this it prompts me to enter my secret to unlock my keyrings.

  • It still asks for the password to unlock the keyring – Laurent May 12 '17 at 23:57
  • 4
    This worked great! But I just needed to remove the --start option because it's not compatible with --replace – Anwar May 22 '17 at 13:58
  • chrome was taking to long to load, in terminal i type gnome-keyring-daemon, then close and open chrome , now i am able to type my password, thankyou – christianbueno.1 Sep 16 '17 at 16:38

I could work around this problem by uninstalling dbus-user-session (and its dependendants xdg-desktop-portal and xdg-desktop-portal-gtk). Those packages came in through installing flatpak.

Thanks to Olaf who brought me on the right track (https://forum.ubuntuusers.de/topic/gnome-keyring-daemon-doppelt/)

  • this seem to work for several people, including me. See this bug report starting at #67 for more info. bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1689825 – Antonios Hadjigeorgalis Jul 17 '17 at 22:09
  • This should be the top answer as it permanently fixes the issue without any other side effects - except maybe that the application that wanted dbus-user-session installed might be slightly upset, but better just that one than the whole system. – Byte Commander Aug 4 '17 at 12:36
  • It didn't solved it for me – Laurent Aug 14 '17 at 3:38

I've been able to fix the slow shortcut and hanging chromium, by commenting out one line in /etc/pam.d/lightdm

# session optional        pam_gnome_keyring.so auto_start

The issue seems to affect more users btw: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1689825

  • 1
    It still asks for the password to unlock the keyring – Laurent May 12 '17 at 23:57
  • Hmm... I have the same problem, with gnome-shell and gdm, so this is probably not directly related. Thanks anyway, will explore pam... somewhere the gnome-keyring-daemon will have to be started – Rmano Jul 26 '17 at 11:21
  • I run gnome-sheel too, so looking at the config I found a similar line in /etc/pam.d/gdm-password. I commented it out but it didn't solve the issue. – Laurent Aug 14 '17 at 3:40

I had exactly the same problem. Basically, whenever I started up, I could see the gnome-keyring-daemon as a process (ps -ef | grep keyring). If I manually issued the gnome-keyring-daemon using --start option, it would not start up the one fault instance already running. By a process of manual deduction, I found that if I killed that process and started a new keyring, then everything worked perfect. so here is what I did to make the solution "sticky"....

go to menu - system configuration - startup apps

delete the gnome-keyring-daemon entry that is already there (if you have one)

create a new gnome-keyring daemon with the following properties:

Name = Gnome Keyring Daemon
Command = /usr/bin/gnome-keyring-daemon --replace --daemonize --components=pkcs11,secrets,ssh
Comment = Gnome Keyring Manager Daemon

Save the startup item, but make sure it has a small delay - I added 10 seconds, and set the option "On"

Now Reboot, and it worked flawlessly for me. It seemed to be the --replace and --daemonize settings that made the difference on my VirtualBox Mint 18.3 cinnamon and a Lenovo G710 Laptop, having tried various combinations of other suggestions on here.

protected by Community Jan 22 at 16:10

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.