On Aug 26, 2009, at 3:59 PM, Albrecht Dreß wrote:
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.
I guess it's not empty--I tried the "gpg2 --sign -a" test, and it produced a signature block without prompting me for a passphrase.
Now, does Balsa also work if you start it from the same console for which running gpg2 as above was successful?
Yes.
Can you check from balsa's startup messages that it *really* uses a gpg[2] engine which exists (maybe the install location changed...)?
[me ~]$ balsa ** Message: init gpgme version 1.1.8** Message: protocol OpenPGP: engine /usr/bin/gpg2 (home (null), version 2.0.11) ** Message: protocol CMS: engine /usr/bin/gpgsm (home (null), version 2.0.11) ** Message: protocol (null): engine /usr/bin/gpgconf (home (null), version 2.0.11)
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.
OK--I upgraded again, and ran Balsa that way, and the only sign (to me!) of anything wrong comes at lines 302ff:
_gpgme_cancel_with_err (ctx=0x168f950): enter: ctx_err=117440523_gpgme_remove_io_cb (data=0x1da0a40): call: setting fd 0x1c (item=0x1da0a60) done gpgme:gpg_io_event (gpg=0x168eb80): call: event 0x7f514cdae510, type 1, type_data 0x7fff79b5b13c
_gpgme_cancel_with_err (ctx=0x168f950): leave gpgme_op_sign_start (ctx=0x168f950): error: Bad passphrase <GPGME> But I wouldn't say I got any insights from it!
Did you see anything from adding debug output to the agent?
Not on the console. Peter
Attachment:
pgpdF9jNYtPLz.pgp
Description: PGP signature