I try to use gnome-keyring because I am using Nautilus and NM-Applet, but it is really a PITA when you don't use gdm/gnome.
I tried Slim with several WMs (awesome,WMFS,subtle,..) and auto unlock for gnome-keyring via PAM. It works fine, but after some time the keyring is locked again.
First I thought this happens when slimlock kicks in, but after adding a few lines to /etc/pam.d/slimlock that problem was gone.
Everything is configured (PAM) like described at gnome and archwiki.
... but gnome-keyring keeps locking itself after some period of time. Does it have some kind of "locking after n minutes of idle"?
Does anyone know a solution? (no solutions are: Not using Nautilus/NM, Using a empty passphrase)
Last edited by Evilandi666 (2011-11-22 12:06:08)
No one has this problem?
I found the solution:
Look in /etc/xdg/autostart. There are 4 files:
Copy the exec linex from those files to your .xinitrc:
[...] /usr/bin/gnome-keyring-daemon --start --components=gpg /usr/bin/gnome-keyring-daemon --start --components=pkcs11 /usr/bin/gnome-keyring-daemon --start --components=secrets /usr/bin/gnome-keyring-daemon --start --components=ssh /usr/bin/awesome
Check after login with ps -A | grep gnome if there is only one instance of gnome-keyring-daemon running - if those lines are executed too earrly you got 4 instances running. Just add it like I did it before awesome starts.
Hope this helps someone, I also put it to the wiki. You now should not get any pkcs11 error anymore when starting seahorse.
Last edited by Evilandi666 (2011-11-22 10:11:08)