Arch Linux

Can you still see the keyring with seahorse? gnome-keyring-3.12 mainly changes socket locations and environment variables that are assigned after that, there's no change in the keyring format or naming of keyrings.

Added screenshot of gnome-keyring 3.10.1-2. Screenshot of 3.12.0-1 to come.

Added screenshot of gnome-keyring 3.12.0-1.

Downgrading to 3.10.1-2 and rebooting restores the login passwords keyring.

How do you start GNOME? Is your keyring password the same as your account password? Your 3.10.x screenshot doesn't show much difference to my setup and in my case things are still working after upgrade.

I use XFCE with the "Launch GNOME services" option ticked. This launches gnome-keyring as:
/usr/bin/gnome-keyring-daemon --daemonize --login

I believe the passwords are the same - or maybe blank as I use lightdm autologin + XFCE. If not, I at least used whatever worked with 3.10.2-1 :)

With help from grawity on #archlinux, it seems that the GNOME_KEYRING_CONTROL variable is no longer set.

Adding this to /etc/profile restored functionality for me:
export GNOME_KEYRING_CONTROL=$XDG_RUNTIME_DIR/keyring

After this, logging out and in again restored full keyring functionality.

d_garbage found the commit causing this here:
https://github.com/GNOME/gnome-keyring/commit/2ca51a0aef5b1bc41f2e71d2b65edc8478dab69d

I noticed today that the above modification to /etc/profile doesn't quite cut it if you use programs that autostart that call secrets.freedesktop.org via dbus. This causes dbus to launch gnome-keyring-daemon - and incorrectly.

I fixed this by creating an new script to launch at startup:
#!/bin/bash
source /etc/X11/xinit/xinitrc.d/30-dbus
eval $(/usr/bin/gnome-keyring-daemon --replace --daemonize --components=gpg,pkcs11,secrets,ssh)
export GNOME_KEYRING_CONTROL GNOME_KEYRING_PID GPG_AGENT_INFO SSH_AUTH_SOCK

I then disabled the "Launch GNOME services" option from within XFCE.

This seems to init gnome-keyring-daemon properly. As we replace the instance launched by dbus, it fixes the problem - although in an ugly way.

Some login managers do have pam_gnome_keyring.so in their PAM configuration. Is this sufficient to work in all situations? Perhaps some PAM configuration has to be updated...

That will work when the user uses a display manager... but it's not in the configuration for a login without a display manager.

Just wondering if there are any more recent thoughts on this?

At this stage, I have to do the following:
1) Add this to /etc/profile
export GNOME_KEYRING_CONTROL=$XDG_RUNTIME_DIR/keyring

2) Launch gnome-keyring at login via:
#!/bin/bash
source /etc/X11/xinit/xinitrc.d/30-dbus
eval $(/usr/bin/gnome-keyring-daemon --replace --daemonize --components=gpg,pkcs11,secrets,ssh)
export GNOME_KEYRING_CONTROL GNOME_KEYRING_PID GPG_AGENT_INFO SSH_AUTH_SOCK

Both of these are required - however it does work after the above two steps.

I had problems with mysql-workbench and gnome-keyring and the /etc/profile workaround (alone) worked. I'm using Xfce.

Status on this? Has anyone talked to upstream?