Posted to upstream list, http://lists.gnupg.org/pipermail/gnupg-devel/2009-September/025353.html Not sure, could have sworn this worked at one point, but can't get it to work for the life of me. Both -qt and -gtk-2 seems to work ok, but as soon as I try -qt4, gpg-agent fails, my debug-level advanced output includes: 2009-09-13 14:24:55 gpg-agent[27662] starting a new PIN Entry gpg-agent[27662]: can't connect server: ec=4.16383 2009-09-13 14:24:56 gpg-agent[27662] can't connect to the PIN entry module: End of file 2009-09-13 14:24:56 gpg-agent[27662] command get_passphrase failed: No pinentry gpg-agent[27662.7] DBG: -> ERR
$ rpm -q pinentry-qt pinentry-qt-0.7.6-1.fc11.x86_64
%changelog * Wed Sep 13 2009 Rex Dieter <rdieter> - 0.7.6-3 - drop alternatives, use app-wrapper instead (borrowed from opensuse) - -qt4 experimental subpkg, -qt includes qt3 version again (#523488) further upstream exchanges/testing, seems the problem lies with gpg-agent/pinentry-qt4 interaction. Running pinentry-qt4 by hand seems to work ok.
I get the Qt4 version by default here. Not sure what caused the change though (I was getting the Qt3 for a while then Qt4 just started getting used).
KNode is using Qt4 and KMail is using Qt3, not sure why (they share env since they're both in Kontact).
It should be consistently using the value of pinentry-program ... in ~/.gnupg/gpg-agent.conf
Creepy, installed f12, works fine now, and can no longer reproduce errors.
Odd. I installed F12 and things started to move back to the non-Qt4 one :( .
easy, rpm -e pinentry-qt (and make sure you're preferred one, like pinentry-qt4 *is* installed).