Arch Linux

rasoran

Member

Registered: 2013-03-25

Posts: 29

[SOLVED] gdm(?) not longer sets SSH_AUTH_SOCK

As the title says, SSH_AUTH_SOCK is not being set. I'm using a complete GNOME and gdm setup. gnome-keyring-daemon launches fine and if I set SSH_AUTH_SOCK=/run/user/1000/keyring/ssh then it works as expected. I checked through my dotfiles and I'm not overriding the variable anywhere. It seemed to have happened at the most recent gdm-3.16.3-1. Any ideas?

Last edited by rasoran (2015-09-21 03:54:03)

trichards

Member

From: Tennessee, USA

Registered: 2013-12-10

Posts: 4

Website

Re: [SOLVED] gdm(?) not longer sets SSH_AUTH_SOCK

Looks like you've encountered this bug: https://bugs.archlinux.org/task/44583 There is a workaround described in the comments, but it's definitely less than ideal.

From what I've experienced, this issue is flaky and session-oriented. If you sign in to your desktop session and find that your SSH_AUTH_SOCK isn't correct, then sign out and/or reboot. After you finish booting / sign back in, it might be fixed (no guarantees).

rasoran

Member

Registered: 2013-03-25

Posts: 29

Re: [SOLVED] gdm(?) not longer sets SSH_AUTH_SOCK

Well it's working again. I did some reinstalling of various gnome keyring related packages but I don't that helped. I read through the bug report you linked and I believe what fixed it was removing ~/.local/share/keyrings. Although they did report that it's rather uncertain when it might or might not work. Well anyhow, marking as resolved although the actual issue is still unclear.