[pkg-gnupg-maint] Bug#791379: Bug#791379: gpg2 fails to use agent started by Xsession; automatically started agent works ok

[Daniel Kahn Gillmor]

Hi Joey--

On Fri 2015-07-03 23:31:57 -0400, Joey Hess wrote:
> Package: gnupg-agent
> Version: 2.1.0-1
> Severity: normal

I'm a little surprised by this version of gnupg-agent -- i don't think
it's available anywhere in debian for quite some time.

> Every time I log in, gpg2 fails to access my secret key;
> something is preventing it from using the gpg agent to prompt for
> the passphrase:
>
> joey at darkstar:~>ps -fax |grep gpg-agent
> 15743 ?        Ss     0:00 /usr/bin/gpg-agent --daemon
> 15967 pts/2    S+     0:00          \_ grep gpg-agent
> joey at darkstar:~>gpg2 --decrypt me.gpg 
> gpg: encrypted with 4096-bit RSA key, ID 17065459, created 2009-06-17
>       "Joey Hess <id at joeyh.name>"
> gpg: public key decryption failed: Operation cancelled
> gpg: decryption failed: No secret key
>
> If I kill the gpg-agent process started by Xsession, and let gpg2
> start the agent up for itself, it works:
>
> joey at darkstar:~>kill 15743
> joey at darkstar:~>ps -fax |grep gpg-agent
> 16008 pts/2    S+     0:00          \_ grep gpg-agent
> joey at darkstar:~>gpg2 --decrypt me.gpg 
> gpg: encrypted with 4096-bit RSA key, ID 17065459, created 2009-06-17
>       "Joey Hess <id at joeyh.name>"
> hi
>
> This is a new problem seen after an upgrade today, and it happens every
> time.
>
> (gpg v1 is able to use the gpg-agent started by Xsession without
> difficulty)

My guess is that you're using pinentry-gnome3 and preferring it over
pinentry-gtk2 -- there is a bugfix for gnupg-agent in unstable at the
moment (2.0.28-3) to pass through DBUS_SESSION_BUS_ADDRESS, and it is
already present in 2.1.6, which should be uploaded to experimental
sometime today or tomorrow.

        --dkg