Enigmail hanging on send - Thunderbird 52.1.1
OpenPGP addon for Mozilla Thunderbird
Brought to you by:
pbrunschwig
Menu
▾
▴
1 Attachments
#687 Enigmail hanging on send - Thunderbird 52.1.1
My Thunderbird version recently updated to 52.1.1. Since then, I am unable to send PGP encrypted emails. Basically, when I click send, I am presented with the 'Sending Message' dialog and it never completes - the progress bar just keeps rolling across the screen. After I press 'cancel', I am returned to my message, but the Send button is now grayed out. Even clicking the padlock to unlock and send unencrypted does not 'un-gray' the Send button.
There is a bizarre workaround that i believe the typcial user would not try - if I copy the body of an email that will not send, close that compose window, open a new window, create a message to the same recipient with the same subject, and paste the body, I can send successfully. I have verified that sending unenrypted emails works fine, as does receiving both encrypted and unencrypted emails.
A log file is attached. Please let me know if I can pass on any additional information!
Update! Not sure what this did, but in the course of poking around, I noticed that there was an enigmail package for Ubuntu 16.04:
https://www.ubuntuupdates.org/package/core/xenial/universe/security/enigmail
I installed this, stopped Thunderbird, restarted, attempted to send an encrypted message and, lo and behold, it worked! I did stop/restart Thunderbird previously with no success, just FYI. So, I am not certain what installing the enigmail package did exactly, and maybe it has nothing to do with why things started working, but I appear to be fine now! You may close this ticket - and I apologize for bothering you - thanks for the fantastic plugin!
Please don't assign bugs to me. In our setup Owner means "I'm working on it".
I don't know yet what the reason is. But the following should solve the issue:
1. kill all gpg/gpg2 processes
2. restart Thunderbird
I also experienced that. Killing gpg2 solved the issue and retrying the same action was successful without hang. Unsure what caused it. I'm on Linux, too (Mint 18.1), which also is Ubuntu-based. I was using the XPI from AMO and switched to nightly recently. Unsure If it happened there also, will report if so.
But mind: I have other troubles with TB, too, such as attachments and images of messages that I moved to IMAP folders being inaccessible until I reset that folder in its properties. Grateful for any hint how to solve that, too.
Yes, toward the end of the day yesterday, it started happenning again. So, I checked processes and found a gpg process running that seemed a bit odd. It had a fairly lengthy execution line with several parameters. In retrospect, saving the comand string might have proven helpful... anyway, I killed it and immediately a dialog popped up which said something about 'mail not sent'. No compose window was open at that time.
Apologies on trying to figure out what to do with the box labeled 'Owner'. In my experience (including when I create web UI code), an input field is meant to be filled out. If it is not supposed to be filled out it shouldn't be present. If it must be present for some reason it should be notated somewhere that it is for internal use only. Do bear in mind that I spend quite a bit of time reading through the requirements of exactly how to post a bug to y'all. It was no trivial process. I had to create a sourceforge account, log into my yahoo webmail account (that is the email address I give to the world but is not my primary - it gets auto-forwarded to my primary) and move the 'click here to verify' message out of spam, test/retest/develop my use case so that I could accurately describe it, and then follow the intructions for how to get to the debug log so I could attach it. A difficult process... and what thanks do I get? A complaint about the fact that I was apparently not supposed to fill out a field on a form that was sitting there asking for input....
Got it! Still hanging... here's the process data:
lee 15748 29228 0 09:45 ? 00:00:00 /usr/bin/gpg2 --charset utf-8 --display-charset utf-8 --use-agent --batch --no-tty --status-fd 2 -a -t --encrypt --trust-model always --encrypt-to 0xF626AAC2 -r 0x28A73EDC73158A2A -u 0xF626AAC2
That's a regular encryption command. Whatever it is, it must be related to some change in Thunderbird, as the same version of Enigmail runs fine on Thunderbird 45.
ugh... just figured out that there appears to be no workaround if attempting to attach files to an encrypted message. Wonder if I need to drop back to an older version of thunderbird... or should I post my issue over with them?
Restarting Thunderbird should usually help as well.
Rolling forward to Thunderbird 54.0b1 seems to have resolved things for me.
I got some more details that allow me to hopefully fix this. Could I ask you to downgrade to Thunderbird 52.1.1 again and try the following beta version and let me know if that works for you:
https://enigmail.net/download/beta/enigmail-1.9.8a.xpi
I'm on TB 52.1.1. Is that some backport or something not available in the nightlies? Depending on that: does it make sense if I downgrade Enigmail from yesterdays nightly to this beta to test? I have no means to trigger the issue, only had it rarely and sporadic, but only when replying IIRC. Killing gpg2 and just retrying to send the message usually did work, so I have no means to reproduce the bug.
Last edit: Olav Seyfarth 2017-05-23
It's not a backport, it's a simple local fix. Not even committed yet.
----- Originale Nachricht -----
Von: Olav Seyfarth nursoda@users.sf.net
Gesendet: 23.05.2017 - 18:28
An: "[enigmail:bugs]" 687@bugs.enigmail.p.re.sf.net
Betreff: [enigmail:bugs] #687 Enigmail hanging on send - Thunderbird 52.1.1
Uhhh.... sadly, I may not be able to downgrade for you. At least, not if it means when uninstalling beta, dropping the ppa, then reinstalling 52.1.1 that I have to reconfigure all of my email connections -- I have 5 mail accounts, 3 of them IMAP, with gigabytes of email. Can I do an uninstall/reinstall of tbird and somehow not lose all of this local info and then point 52.1.1 to the same config in my home folder?
Yes absolutely. Your data is in your home directory and the Thunderbird files are globally installed. You don't need to reconfigure anything.
----- Originale Nachricht -----
Von: Lee Roder leeroder@users.sf.net
Gesendet: 23.05.2017 - 18:30
An: "[enigmail:bugs]" 687@bugs.enigmail.p.re.sf.net
Betreff: [enigmail:bugs] #687 Enigmail hanging on send - Thunderbird 52.1.1
I just tested enigmail-1.9.8a.xpi on OS X with Thunderbird 52.1.1 (64-bit), which has the same issue.
1.9.8a does not fix it, outgoing PGP-signed email still occasionally hangs.
My workaround: cancel sending, answer "yes" when prompted whether to save as draft, immediately open the draft and send again - works flawlessly every time.
Yes, 1.9.8a does not fix the error.
Even though I tried many times, I was not able to reproduce the error. I believe it happens for mails with attachements (but that's only speculative). If the error happens next time, please perform the following steps before doing anything else:
Here are two logs hopefully created as requested. One just as the message sending is hanging, and one after saving a draft and re-sending.
Here is another. I wiped the log before, and as the next mail hangs, this is the log.
I'm having the same issue.
Thunderbird 52.1.1 (64-bit), on macOS Sierra.
Same issues here, on latest Linux Mint. TB 52.1.1 64-bit, gpg2 2.1.11.
Thanks for all the logs. I was able to narrow down the problem. I have some hopes that the following version fixes the issue. Could some of you try this and let me know if the problem persists?
https://enigmail.net/download/beta/enigmail-1.9.8-a4.xpi
Last edit: Patrick Brunschwig 2017-06-16
Looks like 1.9.8-a3 is working for me with TBird 52.1.1!!!