搜尋 Mozilla 技術支援網站

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

了解更多

Cannot drag an email from inbox to a local/file folder after upgrade to 45.3 and upgrade to 45.5.1 hasn't fixed the problem. HELP!?

  • 2 回覆
  • 7 有這個問題
  • 2 次檢視
  • 最近回覆由 Nate93

more options

Upgraded to Tbird 45.3 and can no longer drag any email(s) from the inbox to a file/local folder. Upgrade to 45.5 and 45.5.1 did NOT fix the problem as expected.

Have successfully used Tbird for nearly five(5) years and have never experienced this or similar difficulty. The difficulty/condition described is occurring on a MacBook Pro w/ 2.8 GHz Intel Core i7 processor, running OSX Sierra 10.12.1, if that info helps

What gives and how is this fixed!? HELP (this is becoming more than just annoying), please.

Upgraded to Tbird 45.3 and can no longer drag any email(s) from the inbox to a file/local folder. Upgrade to 45.5 and 45.5.1 did NOT fix the problem as expected. Have successfully used Tbird for nearly five(5) years and have never experienced this or similar difficulty. The difficulty/condition described is occurring on a MacBook Pro w/ 2.8 GHz Intel Core i7 processor, running OSX Sierra 10.12.1, if that info helps What gives and how is this fixed!? HELP (this is becoming more than just annoying), please.

所有回覆 (2)

more options

Restart Thunderbird with add-ons disabled (Thunderbird Safe Mode). On the Help menu, click on "Restart with Add-ons Disabled". If Thunderbird works like normal, there is an Add-on or Theme interfering with normal operations. You will need to re-enable add-ons one at a time until you locate the offender.

more options

Hello Matt,

Thanks for the reply; however, the "solution" suggested unfortunately does not solve the condition.

FWIW, have only one (1) Add-on, 'Lightning' (the calendar), which, after restarting as suggested from "Restart with Add-ons Disabled," was removed from Tbird to make absolutely sure. No avail in either case. Tbird does not work "like normal" and still cannot 'drag' as before changing the MacBook's OSX to Sierra.

Like you, am convinced this is a problem resulting from an 'incorrect setting,' but simply cannot find which one is the culprit. Go figure?

Again, many thanks for your suggestion.