On Sun, 20 Jan 2019, Norbert Preining wrote:
> Any suggestions how to debug this?
Enabling logging for gpg-agent I see:
2019-01-20 15:44:08 gpg-agent[25582] gpg-agent (GnuPG) 2.2.12 starting in
supervised mode.
2019-01-20 15:44:08 gpg-agent[25582] using fd 3 for browser socket
(/run/user/1000/gnupg/S.gpg-agent.browser)
2019-01-20 15:44:08 gpg-agent[25582] using fd 4 for ssh socket
(/run/user/1000/gnupg/S.gpg-agent.ssh)
2019-01-20 15:44:08 gpg-agent[25582] using fd 5 for extra socket
(/run/user/1000/gnupg/S.gpg-agent.extra)
2019-01-20 15:44:08 gpg-agent[25582] using fd 6 for std socket
(/run/user/1000/gnupg/S.gpg-agent)
2019-01-20 15:44:08 gpg-agent[25582] listening on: std=6 extra=5 browser=3 ssh=4
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>
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>
After switching to pinentry-qt it started to work ...
Thanks
Norbert
--
PREINING Norbert http://www.preining.info
Accelia Inc. + JAIST + TeX Live + Debian Developer
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
