User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36 Steps to reproduce: all email attachment can not been saved -out of thunderbird- to map on harddrives since update to 53.0b2 beta Actual results: prgram crashes, have to start up again Expected results: simple: copy attachment to some map in a HD directory at pc or server

I can't reproduce this, but I haven't tried all possible variations: local folder, IMAP folder, with/without local storage, etc. If you have a crash ID, see Help > Troubleshooting, paste it here. Also, try with add-ons disabled, see Help menu. BTW, what's a "map"? Something lost in translation?

I use pop3, in emails I get several pdf and other attachments, which I use at work. Saving thise attachments into my pc in a map f.i. c:\docuements\map1 or \\server\g\map2 Normally I can save this directly from email with save button. Now this function failes, and gives crash of thunderbird. test: I can open txt file into notepath, and than write file down to map. test: disable all add-ons. no succes also in safe mode: no succes

You mean folder? When I click "Save", a dialogue comes up to select the folder to save to. I can save with no problem. If you have a crash, please paste the crash ID here, see Help > Troubleshooting Information.

right, folder... now it worked 1x, saved file, but: next email to safe file...: crash full programm again

Thanks. Wayne, crashes are your speciality.

Hi MAN! this works!! super, hope you can help me with this. by the way: when I open emailbox, and scrol throug emails, I can open a email, than: right-click on an email (file) attachment and paste it to an open folder. But when using the paste to button, it won't work. problem is: I have first to open the folder, where I want to have the copy of the attachment, and than goto the email, right-click on the attachment and paste it into the opened folder.... As a work around one in the hour ok, but it's not workable... Hope you understand, what I mean.

No, I really don't understand what you're saying. There are two ways to save an attachment: - Click "Save" or right-click the attachment and then select "Save". - Drag the attachment to a folder. You cannot "paste" it to a folder (did you mean drag and drop?). And there is no "paste to" button. If you want to take this further, install an English version in parallel, then we're both speaking the same language. In any case, someone will look at the crash.

ok I dragged it to a folder. the other way is not functioning

Got something weard.. my system works also with NAS system. The connection was not as fast as always last days. I reset the NAS last night, and now, I can safe attachments from email to mij C:\\ drive and to the NAS drives as-well. ONLY When I want to open the attachment (pdf) I only can write it in a folder, but can not open is. Now I have to write the attachment a second time, and than -just before ok click) I see the (at first time) written file, I can R-click on the file at screen and than chose for f.i. adobe to open is. Think there is something wrong with the "write button/show file possibility" (R-click in email, at the place of te attachment in the email, chose write/open/un.../delete) do you understand? (I am just an enduser, writing something i do not understand)

Sorry I don't understand what you're saying. As I said in comment #8: If you want to take this further, install an English version in parallel, then we're both speaking the same language. I'm constantly confused about whether you're referring to UI in Thunderbird or Windows. "R-click on the file at screen and than chose for f.i. adobe to open is." - Windows UI, right? "R-click in email, at the place of te attachment in the email, chose write/open/un.../delete" - Thunderbird UI, right? Right-click on the attachment in TB has: "Open, Save As, Detach, Delete". So let's focus on the first two functions: "Open" and "Save As". Does "Open" always work? If not, under which circumstances doesn't it work? Does "Save As" always work? I understand it sometimes doesn't work, you even get a crash. Can you please save to a *local* drive, not a NAS. Then after you saved, I understand that you cannot open the saved file in Windows? Is the file truncated/short/corrupt? Why don't you save an image attachment, then it's pretty obvious whether the file is truncated/short/corrupt. It is also important to know where your e-mail that contains the attachment is stored. In a local folder? On an IMAP server? If so, is the corresponding folder selected for offline use? TB 52 has a bug where large attachments in IMAP non-offline folders are truncated, bug 1355350.

I take the commands just from Tb I inform you, that my restart of the NAS gives an onther situation: I can write the attachment to a folder. on C and also at the NASSo: my 1e probles is solved by itselves. but, IN Tb, when I want to open the same attachment, -so NOT write, but open it-, It will not be opened. The work around i found: is to first write the attachement to a file, and than -- again, use Tb to write the file in the same directory, but than, when I am in the directory (through Tb) -i can see the same file, (from the 1e writing) and than i can open the file (without writing it down). So I can not open an attachemnt IN the tb mail.

OK, so now you're saying that you can *save* the attachment into a folder. Good. However, opening the attachment in TB doesn't work. TB will open the attachment with the application you have configured in Tools > Options, Attachments, Incoming. If that's incorrectly configured, the attachment won't open. Have you tried various types of attachments? PDF, images, MS/Libre/Open Office documents? Nothing opens?

OK! That's it.! I changed the statement t: always ask me...what to do, and it's ok now! I use Tb for 5 or 10 years now. never changed a thing in this environment. but double trouble with update and also bad network connections at same time....gives this ****. // but also to write to c:\ gave failures...so without network connectivity to NAS Now I can open, and write files wwhere and when I want again. As if nothing happened.....thnx for helping me! What I learned, is that I need to stop using the beta versions.....updates may not change these thing for me, without a message. tnx!

(been away for a few days) jorgk, All crashes are version 52 or newer. Earliest crash I find is bp-a014420d-9a4a-4deb-b94f-0974b2170329 2017-03-29 52.0b3 20170215082929

I've seen this type of crash in connection with recent Enigmail/gnupg problems. bp-d19cd643-d8c6-4878-b5ed-976350170609 A typical symptom is one or more orphan gpg.exe processes in Windows task manager.

signature changed to shutdownhang | _PR_MD_WAIT_CV | _PR_WaitCondVar | NS_InvokeByIndex, where all the crashes I checked (about 10) all have version 1.9.8.3 enigmail. The graph you see in the bug report under crash signatures isn't as high on the right as on the left, so either the crash rate dropped or there are additional signatures.

TB 56.9b4, Enigmail nightly (about two weeks old), Win 7 32-bit, gpg 2.2.1 I'm still getting the orphan gpg.exe processes on this computer. With an orphan gpg.exe process present Thunderbird crashes upon shutdown. Crash ID bp-cb517e50-1a4a-4da1-97ab-a93650171105 I believe it has got something to do with switching between different Thunderbird/Enigmail versions. There's also TB 52.4.0, Enigmail 1.9.8.3 running on this computer, even though not simultaneously with the beta version. Switching between release and beta version or vice versa seems to produce the gpg.exe orphan processes.

(In reply to Christian Riechers from comment #18) > TB 56.9b4, Enigmail nightly (about two weeks old), Win 7 32-bit, gpg 2.2.1 > > I'm still getting the orphan gpg.exe processes on this computer. > With an orphan gpg.exe process present Thunderbird crashes upon shutdown. > Crash ID bp-cb517e50-1a4a-4da1-97ab-a93650171105 > > I believe it has got something to do with switching between different > Thunderbird/Enigmail versions. > There's also TB 52.4.0, Enigmail 1.9.8.3 running on this computer, even > though not simultaneously with the beta version. > Switching between release and beta version or vice versa seems to produce > the gpg.exe orphan processes. like bug 1410286 Which probably means there is nothing we can do.