Am 26.08.09 21:16 schrieb(en) Peter Bloomfield:
O.k., then the agent is not able to communicate with pinentry... this is *not* a Balsa issue, but a more fundamental one, which will let any application using gpg (or gpgme) fail.I tried "gpg --sign" with the downgraded gnupg2 package, which works with Balsa, and got the same console message, still no popup.
Ummm, actually, you have to run "gpg2", not gpg, sorry...And are you sure the agent's cache is empty, when you run gpg2? Otherwise, gpg[2] will dump the message, but silently fetch the passphrase from the agent without launching pinentry. You can test this by calling 'gpg2 --sign -a', type some text, and then <ctrl>-<d>, which will dump the usual armored signature block.
Now, does Balsa also work if you start it from the same console for which running gpg2 as above was successful?
Can you check from balsa's startup messages that it *really* uses a gpg[2] engine which exists (maybe the install location changed...)?
You could also try to run balsa with "GPGME_DEBUG=5:gpgme-balsa.log balsa" and look into gpgme-balsa.log if it provides more insight. Did you see anything from adding debug output to the agent?
Cheers, Albrecht.
Attachment:
pgpsi45LeZAW3.pgp
Description: PGP signature