Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

Шукати в статтях підтримки

Остерігайтеся нападів зловмисників. Mozilla ніколи не просить вас зателефонувати, надіслати номер телефону у повідомленні або поділитися з кимось особистими даними. Будь ласка, повідомте про підозрілі дії за допомогою меню “Повідомити про зловживання”

Докладніше
Вирішено

Upgrade from 155.0 to 155.0.1 was unstable, reverted

Forrest

I updated to 155.0.1 via the update modal yesterday, on MacOS Tahoe, and it didn't restart as normal. The main message pane was blank with "No Message Found" (screenshot attached).

I tried installing a fresh 155.0 over, that did not work; but, a restore of the prior app from my Time Machine did work -- that is, the application not the user profile data.

I just thought this was strange; never ran into it.

If there is an issue and I can help test it usefully, I happy to do so (I have backups! LOL).


Forrest

I updated to 155.0.1 via the update modal yesterday, on MacOS Tahoe, and it didn't restart as normal. The main message pane was blank with "No Message Found" (screenshot attached). I tried installing a fresh 155.0 over, that did not work; but, a restore of the prior app from my Time Machine did work -- that is, the application not the user profile data. I just thought this was strange; never ran into it. If there is an issue and I can help test it usefully, I happy to do so (I have backups! LOL). Forrest
Вкладені знімки екрана
Читати цю відповідь у контексті

Вибране рішення

So, there was a quick update to 156.0, which I performed and the problem has resolved.

So, I have no idea what the issue was. But it's fixex, for me, for now.

Усі відповіді (3)

So you are back on version 154.0?

No, I downgraded from 155.0.1 to 155.0 and things were stable again. I'm not entirely sure what happened -- I'm willing to 'try again' as I do have backups, but I wanted to put this info out there in case I ran into something that needs more info.

Вибране рішення

So, there was a quick update to 156.0, which I performed and the problem has resolved.

So, I have no idea what the issue was. But it's fixex, for me, for now.

Запитати

Щоб відповідати на повідомлення, ви повинні ввійти у свій обліковий запис. Поставте нове питання, якщо ви ще не маєте облікового запису.