You are not logged in.
Pages: 1
i have gnome display manager at login, where i can choose between dwm and gnome desktop enviroment.
notice that dwm per se starts fine.
i don't know how to tell gdm to unlock my gnome keyring in case i choose the dwm option at login.
according to the wiki i just need to have libgnome-keyring installed and the keyring named login, which i have done.
the possible things to modify i can think of are either /usr/share/xsessions or /usr/share/gnome-session or my .xinitrc,
with something like
eval $(/usr/bin/gnome-keyring-daemon --start --components=pkcs11,secrets,ssh)
dbus-launch --exit-with-session dwm &
but i don't know how to proceed.
Last edited by nicolo (2017-10-10 15:10:53)
Offline
If you're using GDM then your ~/.xinitrc is irrelevant, GDM doesn't use it.
There's an autostart patch for dwm, have you tried this?
https://dwm.suckless.org/patches/autostart
Offline
..and even if it did use it, it would never start GDM because there are two exec lines. The wiki makes that abundantly clear.
Offline
thanks, i did not know about that patch, i will look into it.
(always very useful comments)
Offline
i find that the suggested patch indeed works, if i put the following in autostart.sh
/usr/bin/gnome-keyring-daemon --start
export SSH_AUTH_SOCK
export GPG_AGENT_INFO
export GNOME_KEYRING_CONTROL
export GNOME_KEYRING_PID
Offline
actually, it only works if i was previously logged into gnome desktop, but not upon reboot. i must still be missing something...
Offline
Why do you have...
/usr/bin/gnome-keyring-daemon --start ...
instead of...
eval $(gnome-keyring-daemon --start)
...
?
Offline
no particular reason, i was trying various possibilities.
actually, i'm now confused: yesterday the combination i wrote in post #5 seemed to work, at least until i reboot, while today it does not, even if i just log out and in, neither does
eval $(/usr/bin/gnome-keyring-daemon --start)
export SSH_AUTH_SOCK
export GPG_AGENT_INFO
export GNOME_KEYRING_CONTROL
export GNOME_KEYRING_PID
Last edited by nicolo (2017-10-07 16:07:52)
Offline
is it possible that i'm not configuring correctly /etc/pam.d/gdm-autologin file? at present it looks like
auth requisite pam_nologin.so
auth required pam_env.so
auth optional pam_gdm.so
auth optional pam_gnome_keyring.so
auth optional pam_permit.so
account include system-local-login
password include system-local-login
session optional pam_keyinit.so force revoke
session include system-local-login
session optional pam_gnome_keyring.so auto_start
Offline
i've also tried what's suggested in https://wiki.archlinux.org/index.php/GN … ing_daemon but it doesn't seem to work
Offline
now i'm even more puzzled: even without dwm autostart script (and without any other modification i mentioned previously, not even export), just typing in a terminal in dwm
chromium --password-store=gnome
gives access to my secrets. however for example the network manager does not see the networks that i made available to my user only. could it be that i'm missing something in the way dwm interacts with such programs and makes them use the keyring, rather than in initializing the keyring itself?
Offline
also in the network manager case, just starting nm-applet solves the issue, so it was more due to initializing single programs correctly than making the keyring available at login, which indeed happens out of the box. marking as solved
Offline
Pages: 1