On 12/10/16 22:04, Daniel Kahn Gillmor wrote: > On Wed 2016-10-12 13:02:56 -0400, OmegaPhil wrote: >> Since that point, I have uninstalled pinentry-qt4 and have happily been >> using pinentry-gtk-2. >> >> Installing pinentry-qt (0.9.7-5) and switching to it via alternatives >> results in the following error dialog coming up 4 times in succession >> from Enigmail: >> >> ===================================================================== >> >> GnuPG cannot query your passphrase via pinentry. >> >> This is a system setup or configuration error that prevents Enigmail >> from working properly and cannot be fixed automatically. >> >> We strongly recommend that you consult our support web site at >> https://enigmail.net/faq. >> >> ===================================================================== >> >> The real error comes out in ~/.xsession-errors: >> >> ===================================================================== >> >> gpg-agent[7019]: can't connect to the PIN entry module >> '/usr/bin/pinentry': End of file >> gpg-agent[7019]: failed to unprotect the secret key: No pinentry >> gpg-agent[7019]: failed to read the secret key >> gpg-agent[7019]: command 'PKDECRYPT' failed: No pinentry > > I'm still baffled. i followed exactly the steps that you did and the QT > prompt shows up for me :( > > What version of enigmail are you running? where did you get it from? > > can you turn on debug-pinentry in your dirmngr.conf and see what it says? > > --dkg
Enigmail is v1.9.5 via Get Addons (rather than the Debian package). I started playing with dirmngr.conf but then I realised you meant gpg-agent.conf ;). As soon as I did a killall to have gpg-agent load the new configuration and try again, it worked - I know that gpg2 stuff has updated recently, and my uptime is ~11d, so perhaps the update scripts don't kill off gpg-agent when theres some incompatible change? Thanks
signature.asc
Description: OpenPGP digital signature
