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

[Joachim Breitner]

Hi,

On Mon, 15 Aug 2016 07:57:43 +0900 Norbert Preining <preining at logic.at>
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 would start the gpg-agent, but using it failed with

sign_and_send_pubkey: signing failed: agent refused operation

I did not further debug it, but one guess is that there is no DISPLAY
variable set, so pinentry fails?

Then I found in gpg-agent(1) an entry that says

    In  case  you want to use the included Secure Shell Agent you may
    start the agent using:

         gpg-connect-agent /bye

So I added that to my session file, but I’m not sure if it is the right
way of doing it.

Greetings,
Joachim


-- 
Joachim “nomeata” Breitner
Debian Developer
  nomeata at debian.org • https://people.debian.org/~nomeata
  XMPP: nomeata at joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnupg-maint/attachments/20160815/f2af63bb/attachment.sig>