為了改善您的使用體驗，本網站正在進行維護，部分功能暫時無法使用。若本站的文件無法解決您的問題，想要向社群發問的話，請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問，我們的社群成員將很快會回覆您的疑問。

Avatar for Username

搜尋 Mozilla 技術支援網站

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

了解更多

此討論串已被封存。 如果您有需要幫助，請新增一個新問題

not seeing the details of the e-mails after update to 45.0. SOLVED: caused by Mnenhy extension

  • 2 回覆
  • 3 有這個問題
  • 2 次檢視
  • 最近回覆由 thundermac

thundermac
thundermac
more options

I have the standard mail-boxes in my account, like inbox, sent, ... . If I click on inbox, I see a list of the mails in my inbox and below some more info on whatever e-mail I am looking at in the list (gray bar). If however I double click on that mail to get all the info of that e-mail, I get an empty screen.

This worked before 45.0. When double clicking on the mail, I got a window with only that e-mail, but complete.

Am I doing something wrong? Do I need to use other seetings? Or is this a bug in the programme?

Thanks for the help.

I have the standard mail-boxes in my account, like inbox, sent, ... . If I click on inbox, I see a list of the mails in my inbox and below some more info on whatever e-mail I am looking at in the list (gray bar). If however I double click on that mail to get all the info of that e-mail, I get an empty screen. This worked before 45.0. When double clicking on the mail, I got a window with only that e-mail, but complete. Am I doing something wrong? Do I need to use other seetings? Or is this a bug in the programme? Thanks for the help.

由 Wayne Mery 於 修改

被選擇的解決方法

Do you also see the problem when Thunderbird is started in safe mode? 

Instructions https://support.mozilla.org/en-US/kb/safe-mode
從原來的回覆中察看解決方案 👍 2

所有回覆 (2)

Wayne Mery
Wayne Mery
  • Moderator
  • Top 10 Contributor
more options

選擇的解決方法

Do you also see the problem when Thunderbird is started in safe mode? 

Instructions https://support.mozilla.org/en-US/kb/safe-mode
thundermac
thundermac 提出問題者
more options

Thanks a lot! 

I was the add-on "Mnenhy  0.8.6.1-signed.1-let-fixed" that caused both (this question and the other related one after the 45.0 upgrade) problems.

Disabling it, solved the issue.