Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Add attachment hangs if location of last attachment is not reachable

  • 2 回覆
  • 1 有這個問題
  • 1 次檢視
  • 最近回覆由 wallite96

more options

If the folder location of the last attachment is not currently accessible, such as a network share requiring an active VPN tunnel, the Attach dialogue window hangs indefinitely. This is using a Windows install of Version 31.6.0. Thunderbird has to be force closed or the computer restarted. The workaround is to use the Advanced tool Config Editor and clear the mail.compose.attach.dir setting before attempting to attach. Is there a more elegant solution? I would expect a timeout to occur triggering an alternate "local" folder/directory to be displayed in the dialogue box as occurs when the setting is empty; or a box to allow the user to select an accessible location. In any case the indefinite hanging is not a good option.

If the folder location of the last attachment is not currently accessible, such as a network share requiring an active VPN tunnel, the Attach dialogue window hangs indefinitely. This is using a Windows install of Version 31.6.0. Thunderbird has to be force closed or the computer restarted. The workaround is to use the Advanced tool Config Editor and clear the mail.compose.attach.dir setting before attempting to attach. Is there a more elegant solution? I would expect a timeout to occur triggering an alternate "local" folder/directory to be displayed in the dialogue box as occurs when the setting is empty; or a box to allow the user to select an accessible location. In any case the indefinite hanging is not a good option.

所有回覆 (2)

more options

this sounds like bug 442908 perhaps you could assist with the stack trace they seek.

more options

I agree, this is the same bug that has existed for years. It is easily reproduced as described in the bug report. I will attempt to gather more information but I suspect someone more versed in dealing with Windows OS could get useful data with less effort.