Menu

Signing and decrypting mails stopped working after dist upgrade, gpg-agent seems to sleep

2013-12-02
2013-12-02
  • Fredrik Ismyren

    Fredrik Ismyren - 2013-12-02

    Hello friends!

    I'm using Thunderbird 24.1.1, Enigmail 1.6 and since I did a dist upgrade to Lubuntu 13.10 I've had problems with Enigmail. I did the same upgrade procedure on my laptop with no problems. Really odd.

    Ok back to my main computer. It seems like the gpg-agent can't talk with Enigmail even though the process is running. I used Gpg2 for a while as a temporary solution. That way I had to type the password for every mail but later on this solution stopped working too.

    Here's the problem. When I try to sign a message with my key I get "OpenPGP warning, bad passphrase". When I try to sign from the command line I get "problem with the agent. inactivating agent usage". I'm using the swedish translation so I hope you are able to associate these converted error messages to the ones in english.
    When I use only encryption when sending email then it works. When I try to decrypt a message in my inbox then I get the following error message in the pink bar above the message frame: "OpenPGP Error - verification of signature failed; click on 'details' for more information.

    Please give me a hints I'm going nuts here.

    Cheers,
    Fredrik - Sweden.

     
  • Fredrik Ismyren

    Fredrik Ismyren - 2013-12-02

    Wrong forum. Sorry ..

     
  • Patrick Brunschwig

    Topic moved.

     
  • Fredrik Ismyren

    Fredrik Ismyren - 2013-12-02

    I'm aware that I should seek answers elsewhere too because the signing process fails from the command line. I just hoped that someone had experienced the same problem.

     
  • Patrick Brunschwig

    Your problem is most likely that gpg-agent and its helper tools are not installed properly. You'll need:

    • gpg-agent, matching to the installed version of GnuPG
    • pinentry-qt, pinentry-gtk or similar (i.e. a pinentry that works on graphical desktops)
    • a symlink "pinentry" that points to the installed pinetry-XXX
     
  • Fredrik Ismyren

    Fredrik Ismyren - 2013-12-02

    Patrick! You're an ace! The symlink had been redirected to pinentry-qt4. I changed it to pinentry-gtk-2 and it started working. You made my day!

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.