Comment 1 for bug 1106110

Hi there!

This morning I had this problem again and I will explain the problem more …

During my Gnome-session gnome-keyring dies (in the background) without any error messages (/var/log/syslog, ~/.xsession-errors).
As you can see in the following command output, there are multiple keyring-folders in /tmp.

#> ps aux|grep keyr
$user 2337 0.0 0.0 51596 7428 ? Sl Feb20 0:00 /usr/bin/gnome-keyring-daemon --start --foreground --components=secrets
$user 18099 0.2 0.1 75620 14032 ? SLl 10:18 0:01 /usr/bin/gnome-keyring-daemon --start --foreground --components=secrets
$user 18926 0.0 0.0 5884 832 pts/1 S+ 10:29 0:00 grep keyr

#> ll /tmp/
drwx------ 2 $user $user 4,0K Feb 20 16:50 keyring-92x5pQ/
drwx------ 2 $user $user 4,0K Feb 20 13:18 keyring-B1KV8T/
drwx------ 2 $user $user 4,0K Feb 20 16:46 keyring-lIhMpd/
drwx------ 2 $user $user 4,0K Feb 21 10:18 keyring-ZciiCm/

It seems there are some similarities with Bug #383926 [0]. I think there could be a temporarily workaround if I would know the equivalent for „$SSH_AUTH_SOCK“.

[0] https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/383926/comments/10

I can use the new keyring-folder in (i.e.) Chromium after a automatic re-auth. (In Chromium the keyring-auth pops up and I can enter my password to get access to the new keyring instance.)
In Thunderbird/Enigmail that doesn't work! There is no re-auth dialog after the keyring-restart (in the background) and I only get a pop-up with the message, that I used a wrong password for encryption (of my email). :-/

For me only a logout→login solves the problem (with Thunderbird/Enigmail). – Or a reboot …
I don't think that the silent deaths of gnome-keyring in the background are ‚normal‘, so I posted this bug-report.

Thanks a lot for taking attention and best regards!