![Thunderbird logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2024-02-12-07-36-53-599028_1.png)
Can't see any emails after upgraded to 115.
My Thunderbird was upgraded to 115 automatically, and now I can't see any emails (old and new). Just a blank page. I don't have a backup. How can I resolve this issue? Tried the troubleshooting mode, but didn't help. I've been using TB since 2006, and have thousands of emails in my profile, so can't just create a new profile.
Обране рішення
Thank you, christ1. As suggested, I changed the theme several times, and restarted Thunderbird as well as the OS multiple times, but those did not solve the issue.
I found one of my accounts showed the garble folder name (username was omitted from the screenshot). I removed that account, restarted Thunderbird, and I could see the folders and emails in the email pane, so it seems that this account caused the issue. I took a profile backup before doing this, and I could reproduce the issue by just restoring the profile. Confirmed that removing the account fixed the problem after TB was restarted.
Читати цю відповідь у контексті 👍 0Усі відповіді (3)
The versions is 115.6.1 (64-bit) on Windows 11.
The error console shows the following error:
Uncaught (in promise) NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]
This seems to be the same issue reported in Bug 1869685.
See if this helps. https://support.mozilla.org/en-US/questions/1418550
Вибране рішення
Thank you, christ1. As suggested, I changed the theme several times, and restarted Thunderbird as well as the OS multiple times, but those did not solve the issue.
I found one of my accounts showed the garble folder name (username was omitted from the screenshot). I removed that account, restarted Thunderbird, and I could see the folders and emails in the email pane, so it seems that this account caused the issue. I took a profile backup before doing this, and I could reproduce the issue by just restoring the profile. Confirmed that removing the account fixed the problem after TB was restarted.