Bug#790049: SSH_AUTH_SOCK no longer set in environment

[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 key unlock dialog. But my session didn't have
this variable set by default.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.13.0-rc7-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-keyring depends on:
ii  dbus-x11 [dbus-session-bus]                  1.11.16+really1.10.22-1
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2+b1
ii  gcr                                          3.20.0-5.1
ii  libc6                                        2.25-0experimental3
ii  libcap-ng0                                   0.7.7-3+b1
ii  libcap2-bin                                  1:2.25-1
ii  libgck-1-0                                   3.20.0-5.1
ii  libgcr-base-3-1                              3.20.0-5.1
ii  libgcrypt20                                  1.7.9-1
ii  libglib2.0-0                                 2.54.0-1
ii  p11-kit                                      0.23.7-3
ii  pinentry-gnome3                              1.0.0-2

Versions of packages gnome-keyring recommends:
ii  libpam-gnome-keyring  3.20.1-1

gnome-keyring suggests no packages.

-- no debconf information