Package: gnupg-agent Version: 2.1.8-1 Severity: normal -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi, this is a bit weird. It might be a duplicate of #798956 SSH support is broken with the instance of gnupg-agent that is started via Xsession. The environment is set up correctly, i.e. SSH_AUTH_SOCK=/home/jojo/.gnupg/S.gpg-agent.ssh the process listens on that socket (verified using lsof) and accepts a connection there when I run ssh. But ssh seems to be unable to communicate with the agent and behaves as if it had no valid key. The interesting thing is that after killall gpg-agent && gpg-agent --daemon during a running session, everything works fine. The arguments passed to gpg-agent (--daemon) are the same as with the initial process. Any ideas what might be causing this? Greetings, Joachim - -- System Information: Debian Release: stretch/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnupg-agent depends on: ii libassuan0 2.3.0-1 ii libc6 2.19-22 ii libgcrypt20 1.6.3-2 ii libgpg-error0 1.20-1 ii libnpth0 1.2-1 ii libreadline6 6.3-8+b3 ii pinentry-curses [pinentry] 0.9.5-4 ii pinentry-gnome3 [pinentry] 0.9.5-4 ii pinentry-gtk2 [pinentry] 0.9.5-4 Versions of packages gnupg-agent recommends: ii gnupg 1.4.19-5 ii gnupg2 2.1.8-1 gnupg-agent suggests no packages. - -- no debconf information -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlYWHlAACgkQ9ijrk0dDIGyWkACgnEkJVyCxW1Gu7sSNtnGzmec+ iJMAn18vi1TN+g/4LCouP5YKthOoSz+i =o8Bz -----END PGP SIGNATURE-----