On Tue 2019-07-09 11:58:46 +0200, Emmanuel Revah wrote: > I've followed these steps carefully, on 2 computers, both on Debian > Buster, 64 bit. The only thing that seems logic to me is that there > might be an issue with pinentry-qt itself. > > If I remove all pinentry-* except for qt and clean gpg-agent.conf file > (remove pinentry conf) I get the error "ERR 67108949 No pinentry <GPG > Agent>". > > Any combination of either, only having pinentry-qt installed, or the > config file pointing to it, will result in this error.
this sounds very frustrating, i'm sorry to hear it. I just ran the following test that uses an empty GnuPG homedir: GNUPGHOME=$(mktemp -d) cat > "$GNUPGHOME/gpg-agent.conf" <<EOF pinentry-program $(which pinentry-qt) log-file $GNUPGHOME/gpg-agent.log debug 1024 debug-pinentry EOF export GNUPGHOME gpg-connect-agent 'GET_CONFIRMATION Hello' /bye And it works for me -- i get a graphical QT popup window. > I can use pinentry-qt to get a dialog window, it just does not work with > GPG in my case. > > If this isn't a bug (PEBKAC is always an option for me) or can't be > fixed, I will just use fltk or gtk2 and I'll be fine. If you'd like me > to try out more things, let me know. Could you try out the test above? Once you run it, if it gives you an error, could you look at $GNUPGHOME/gpg-agent.log ? --dkg
signature.asc
Description: PGP signature