Hello, Boyd. I see that you're not showing your full gpg-agent.conf. Could it be possible that you're having a lc_message parameter in it?
I've been debugging for hours this, and finally came up with the
following
discovery:
gpg-agent.conf:
no-grab
pinentry-program /usr/bin/pinentry-qt4
default-cache-ttl 7200
#lc-messages "es_ES.UTF-8"
lc-ctype "es_ES.UTF-8"
Works! See?
en...@polgara:~/debian/random_package$ debsign
signfile ../random_package-1.dsc David Martínez Moreno <en...@debian.org>
You need a passphrase to unlock the secret key for
user: "David Martínez Moreno <en...@debian.org>"
1024-bit DSA key, ID 0D62001B, created 2001-03-12
gpg: cancelled by user
But if I uncomment 'lc_message' parameter:
no-grab
pinentry-program /usr/bin/pinentry-qt4
default-cache-ttl 7200
lc-messages "es_ES.UTF-8"
lc-ctype "es_ES.UTF-8"
And rerun the agent, it fails when connecting:
en...@polgara:~/debian/random_package$ debsign
signfile ../random_package-1.dsc David Martínez Moreno <en...@debian.org>
You need a passphrase to unlock the secret key for
user: "David Martínez Moreno <en...@debian.org>"
1024-bit DSA key, ID 0D62001B, created 2001-03-12
gpg: problem with the agent - disabling agent use <<<<<<<<<<<<<<< See?
Enter passphrase:
gpg: Interrupt caught ... exiting
debsign: gpg error occurred! Aborting....
Just as a note, this is also broken for me with pinentry-qt.
Best regards,
Ender.
--
Uh, we had a slight weapons malfunction, but
uh... everything's perfectly all right now. We're
fine. We're all fine here now, thank you. How are you?
-- Han Solo (Star Wars).
signature.asc
Description: This is a digitally signed message part.
