Bug#790049: SSH_AUTH_SOCK no longer set in environment

2017-09-15 Thread Josh Triplett
Package: gnome-keyring Version: 3.20.1-1 Followup-For: Bug #790049 This bug went away for a while, but seems to have recurred. gnome-keyring is running, and /run/user/1000/keyring/ssh exists. If I manually set SSH_AUTH_SOCK=/run/user/1000/keyring/ssh and then run ssh, gnome-keyring pops up its

Bug#790049:

2015-06-27 Thread Richard Ayotte
I had a similar problem rm -r ~/.gnome2/keyrings fixed it form me. -- Richard -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#790049: SSH_AUTH_SOCK no longer set in environment

2015-06-26 Thread Josh Triplett
Package: gnome-keyring Version: 3.16.0-2 Severity: normal File: /usr/bin/gnome-keyring-daemon Recently, I noticed that gnome-keyring's SSH agent no longer seems to set SSH_AUTH_SOCK in the session environment. I can see via ps that the SSH component is running: josh 2321 0.0 0.1 419788 8