You are not logged in.
Hi again!
Now that I have moved away from LightDM in favor of startx, accessing gnome keyring is not as seamless as it was via lightdm. I tinkered with using export/eval in my .bashrc file (see below)
eval $(/usr/bin/gnome-keyring-daemon --start --components=pkcs11,secrets)
export GNOME_KEYRING_CONTROL GNOME_KEYRING_PID
As I have read this should allow the non-prompting and auto unlock of the keyring on login. I know that if I blank out the password for the keyring via seahorse, it will halt the one time pop up on login but there are ramifications to that. I don't mind passing the creds (yes, the login password and keyring pass are the same) on each reboot/login but would be nice to have it work as it does with either lightdm or gdm.
UPDATE:
Reviewing the wiki, it appears I did not have the pam bits in place in the file: /etc/pam.d/login
and removed the above lines from the .bashrc and put the following:
eval $(/usr/bin/gnome-keyring-daemon --start --components=pkcs11,secrets,ssh)
export SSH_AUTH_SOCK
in my .xinitrc before the exec i3
Marking as resolved
thanks for help!
/sb
Last edited by Stratoblaster (2019-07-04 18:14:55)
Supercalifragilisticexpialidocious
Offline
You have to start the gnome keyring in your pam session. If you don't use a display manager, then you have to add it to /etc/pam.d/login I think.
Edit: You found it as well ![]()
Last edited by progandy (2019-07-04 18:15:37)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' | alias ENGLISH='LANG=C.UTF-8 ' |
Offline
Indeed - I was missing a few bits. all is working perfectly now. This setup is working exactly as I wanted it to and loving it!
Thank you for the feedback!
/sb
Supercalifragilisticexpialidocious
Offline