Hello,
It looks like similar to the bug 835394.
Manual workaround to set environment variables is:
$ gpg-connect-agent updatestartuptty /bye
As explained in:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835394#43
Norbert Preining <norb...@preining.info> wrote:
> the default was pinentry-gnome3:
>
> 2019-01-20 15:44:30 gpg-agent[25582] failed to unprotect the secret key: No
> passphrase given
> 2019-01-20 15:44:30 gpg-agent[25582] failed to read the secret key
> 2019-01-20 15:44:30 gpg-agent[25582] ssh sign request failed: No passphrase
> given <GPG Agent>
It may happen when gpg-agent doesn't know DBUS_SESSION_BUSS_ADDRESS.
> then I switched to pinentry-gtk-2, same
>
> 2019-01-20 15:47:18 gpg-agent[25582] failed to unprotect the secret key: No
> passphrase given
> 2019-01-20 15:47:18 gpg-agent[25582] failed to read the secret key
> 2019-01-20 15:47:18 gpg-agent[25582] ssh sign request failed: No passphrase
> given <GPG Agent>
It may happen when gpg-agent doesn't know DISPLAY or XAUTHORITY.
> After switching to pinentry-qt it started to work ...
Umm... Strange.
--
