#9790: Setting XDG_RUNTIME_DIR in /etc/profile breaks gnome-keyring autologin
----------------------+---------------------------------------
Reporter: wblaszcz | Owner: blfs-book@…
Type: defect | Status: new
Priority: normal | Milestone: 8.2
Component: BOOK | Version: SVN
Severity: normal | Keywords: systemd pam gnome-keyring
----------------------+---------------------------------------
This is the error I get in the system journal (B/LFS 8.1 + GNOME 3.26.0)"
{{{
Sep 20 19:10:21 jupiter gnome-keyring-daemon[717]: couldn't access control
socket: /tmp/xdg-wblaszcz/keyring/control: No such file or directory
Sep 20 19:10:21 jupiter gnome-keyring-daemon[719]: couldn't access control
socket: /tmp/xdg-wblaszcz/keyring/control: No such file or directory
Sep 20 19:10:21 jupiter gnome-keyring-d[717]: couldn't access control
socket: /tmp/xdg-wblaszcz/keyring/control: No such file or directory
Sep 20 19:10:21 jupiter gnome-keyring-d[719]: couldn't access control
socket: /tmp/xdg-wblaszcz/keyring/control: No such file or directory
Sep 20 19:10:21 jupiter gnome-keyring-ssh.desktop[714]: SSH_AUTH_SOCK=/tmp
/xdg-wblaszcz/keyring/ssh
}}}
The is the equivalent entry on a working build (B/LFS 8.0 + GNOME 3.24.x)
:
{{{
Sep 20 17:20:22 jupiter gnome-keyring-ssh.desktop[705]:
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Sep 20 17:20:22 jupiter gnome-keyring-secrets.desktop[707]:
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
}}}
Turns out that SSH_AUTH_SOCK is derived from XDG_RUNTIME_DIR.
Turns out that XDG_RUNTIME_DIR is set by default through pam_systemd.
Looks like /etc/profile is overwriting this variable.
--
Ticket URL: <http://wiki.linuxfromscratch.org/blfs/ticket/9790>
BLFS Trac <http://wiki.linuxfromscratch.org/blfs>
Beyond Linux From Scratch
--
http://lists.linuxfromscratch.org/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
