You are not logged in.
Pages: 1
I am setting up sway at the moment and I am facing some struggles with gnome-keyring which I want to use for ssh.
The wiki states that using GDM the keyring should be started and unlocked on login. However, if I want to ssh I am prompted for my keyphrase instead of keyring popup.
I also copied the two files to autostart as mentioned in the wiki, but beside filling my journalctl even more nothing changed.
In journalctl I see 'gdm-password][1182]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring' so in principle it should be there.
Offline
In Sway the only place for autostart is the Sway config. You have to exec_always some binaries. To get all things running there are several things to autostart. One of them should be the polkit gnome (?), keyring stuff etc.. Just google for some i3 or sway configs.
Last edited by equalizer876 (2021-01-04 15:44:32)
Offline
I think I found a reason. The arch wiki recommends to put the following to .bash_profile
if [ -n "$DESKTOP_SESSION" ];then
eval $(gnome-keyring-daemon --start)
export SSH_AUTH_SOCK
fi
But when I log in via DM the .bash_profile isn't sourced. I entered it manually in a terminal and that did the trick.
Should I place it then in .bashrc?
Offline
Read my post again.
Offline
You mean I should place it in sway/config?
The keyring is already started by gdm on login.
Last edited by Simaryp (2021-01-04 15:58:19)
Offline
You mean I should place it in sway/config?
Yes. Take some references of
https://github.com/rbnis/dotfiles/blob/ … way/config
https://github.com/snakedye/wlr_config/ … way/config
Offline
That worked. I appended:
exec eval $(gnome-keyring-daemon --start)
exec export SSH_AUTH_SOCKOffline
Pages: 1