Bug#834368: [pkg-gnupg-maint] Bug#834368: gnupg: update to gnupg2 broke gpg-agent autostart

On Mon, 15 Aug 2016 15:40, nome...@debian.org said: > I did not further debug it, but one guess is that there is no DISPLAY > variable set, so pinentry fails? That might be the case; I can't tell for sure because I am not not running systemd. However gpg-connect-agent updatestartuptty /bye

Bug#834368: gnupg: update to gnupg2 broke gpg-agent autostart

On Mon, 15 Aug 2016, Joachim Breitner wrote: > I stumbled over the same problem. I tried to fix this using > $ systemctl --user enable gpg-agent > and > $ systemctl --user start gpg-agent > and indeed it would start the gpg-agent, but using it failed with I used gpgconf --launch gpg-agent

Bug#834368: gnupg: update to gnupg2 broke gpg-agent autostart

Hi, On Mon, 15 Aug 2016 07:57:43 +0900 Norbert Preining wrote: > Do you have any idea on how to fix this complete misbehaviour? I stumbled over the same problem. I tried to fix this using $ systemctl --user enable gpg-agent and $ systemctl --user start gpg-agent and indeed it

Bug#834368: gnupg: update to gnupg2 broke gpg-agent autostart

Package: gnupg Version: 2.1.14-5 Severity: serious Justification: breaks unrelated software Dear all, I am relying heavily on gpg-agent to provide ssh keys from my hardware token. This worked without too many problems with the previous /etc/X11/Xsession.d/90gpg-agent With the update to