Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

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.