Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

After Thunderbird update, Thunderbird seems to be stuck in update mode

  • 4 ответа
  • 1 имеет эту проблему
  • 47 просмотров
  • Последний ответ от heckner

more options

Hi,

My Problem: After an update Thunderbird does not let me access any functions, and just stays with an "empty" screen (see below)

What happened/lead to the problem? Thunderbird requested to be updated. After the update run, thunderbird was restarted (as requested). This is how it looks after restart (see image 1) Almost none of the functions work.

What might be the cause? From my guess it seems that Thunderbird is still in the mode to complete the update. For some reason it cannot complete the update cycle- As you can see in the second screenshot it still says a restart is necessary. When I click on the button, thunderbird restarts, but still with the same (empty) screen.


System Info: Windows 10 I currently use thunderbird 91.10.0

What I already tried:

  • I already tried to use "safe mode" . But it didn't help either
  • I already tried to uninstall / reinstall thunderbird. But still I get in this endless update cycle.
  • Tried to instal 91.1.0
Hi, My Problem: After an update Thunderbird does not let me access any functions, and just stays with an "empty" screen (see below) What happened/lead to the problem? Thunderbird requested to be updated. After the update run, thunderbird was restarted (as requested). This is how it looks after restart (see image 1) Almost none of the functions work. What might be the cause? From my guess it seems that Thunderbird is still in the mode to complete the update. For some reason it cannot complete the update cycle- As you can see in the second screenshot it still says a restart is necessary. When I click on the button, thunderbird restarts, but still with the same (empty) screen. System Info: Windows 10 I currently use thunderbird 91.10.0 What I already tried: * I already tried to use "safe mode" . But it didn't help either * I already tried to uninstall / reinstall thunderbird. But still I get in this endless update cycle. * Tried to instal 91.1.0
Приложенные скриншоты

Выбранное решение

Hi, I was able to fix it myself. It seems that my "global-messages-db.sqlite" in my profile was no accessible any more. I tried to open it using Notepad++ and received a Windows Error "0x80071129" with a cryptic error message. Background info (which makes partially sense in this respect). I have stored my thunderbird profile in my "Documents" Folder on C:\. Parts of this folder (including thunderbird profile) are synced to my synology (for backup reasons). So I suspect that at the very moment of the update the sqlite sync failed.

How I resolved the problem?

I right clicked on start to use Windows Powershell (as Administrator)... I am not sure whether this was necessary. I started chkdsk /F only to learn that it can only be run during the next startup. So I rebooted. And guess what: That resoled the problem!

Прочитайте этот ответ в контексте 👍 0

Все ответы (4)

more options

Hold the shift key when you start Thunderbird. If it starts, remove any non English dictionaries and restart.

more options

Hi thanks for your reply. But when I start Thunderbird.exe while holding the Shift key it shows me this dialogue (no option to remove english dictionaries).

more options

Further information my problem:

When I use Tools->Developer Tools->Error Console , I see this:


Unexpected event profile-after-change URLQueryStrippingListService.jsm:224 Unknown Collection "thunderbird/query-stripping" RemoteSettingsClient.jsm:160 Uncaught TypeError: this.asyncConnection is null

   createNounTable resource:///modules/gloda/GlodaDatastore.jsm:1519
   defineNoun resource:///modules/gloda/Gloda.jsm:909
   <anonymous> resource:///modules/gloda/NounMimetype.jsm:574
   <anonymous> resource:///modules/gloda/GlodaFundAttr.jsm:18
   <anonymous> resource:///modules/gloda/Everybody.jsm:7
   <anonymous> resource:///modules/gloda/GlodaPublic.jsm:8
   listener resource:///modules/activity/glodaIndexer.jsm:99
   listenerWrapper resource:///modules/activity/glodaIndexer.jsm:71
   addListener resource:///modules/gloda/GlodaIndexer.jsm:695
   init resource:///modules/activity/glodaIndexer.jsm:73
   <anonymous> resource:///modules/activity/activityModules.jsm:22
   <anonymous> chrome://messenger/content/msgMail3PaneWindow.js:26

GlodaDatastore.jsm:1519:9 Uncaught TypeError: this.asyncConnection is null

   createNounTable resource:///modules/gloda/GlodaDatastore.jsm:1519
   defineNoun resource:///modules/gloda/Gloda.jsm:909
   <anonymous> resource:///modules/gloda/NounMimetype.jsm:574
   <anonymous> resource:///modules/gloda/GlodaFundAttr.jsm:18
   <anonymous> resource:///modules/gloda/Everybody.jsm:7
   <anonymous> resource:///modules/gloda/GlodaPublic.jsm:8
   <anonymous> resource:///modules/gloda/Facet.jsm:11
   <anonymous> chrome://messenger/content/glodaFacetTab.js:6

GlodaDatastore.jsm:1519:9 Uncaught TypeError: this.asyncConnection is null

   createNounTable resource:///modules/gloda/GlodaDatastore.jsm:1519
   defineNoun resource:///modules/gloda/Gloda.jsm:909
   <anonymous> resource:///modules/gloda/NounMimetype.jsm:574
   <anonymous> resource:///modules/gloda/GlodaFundAttr.jsm:18
   <anonymous> resource:///modules/gloda/Everybody.jsm:7
   <anonymous> resource:///modules/gloda/GlodaPublic.jsm:8
   <anonymous> chrome://gloda/content/overlay.js:6

GlodaDatastore.jsm:1519:9 Uncaught TypeError: this.asyncConnection is null

   createNounTable resource:///modules/gloda/GlodaDatastore.jsm:1519
   defineNoun resource:///modules/gloda/Gloda.jsm:909
   <anonymous> resource:///modules/gloda/NounMimetype.jsm:574
   <anonymous> resource:///modules/gloda/GlodaFundAttr.jsm:18
   <anonymous> resource:///modules/gloda/Everybody.jsm:7
   <anonymous> resource:///modules/gloda/GlodaPublic.jsm:8
   <anonymous> resource:///modules/gloda/GlodaMsgSearcher.jsm:8
   <anonymous> resource:///modules/QuickFilterManager.jsm:29
   <anonymous> chrome://messenger/content/quickFilterBar.js:13

GlodaDatastore.jsm:1519:9 Uncaught TypeError: this.asyncConnection is null

   createNounTable resource:///modules/gloda/GlodaDatastore.jsm:1519
   defineNoun resource:///modules/gloda/Gloda.jsm:909
   <anonymous> resource:///modules/gloda/NounMimetype.jsm:574
   <anonymous> resource:///modules/gloda/GlodaFundAttr.jsm:18
   <anonymous> resource:///modules/gloda/Everybody.jsm:7
   <anonymous> resource:///modules/gloda/GlodaPublic.jsm:8
   <anonymous> resource:///modules/gloda/GlodaMsgSearcher.jsm:8
   <anonymous> chrome://messenger/content/tabmail.js:18

GlodaDatastore.jsm:1519:9 Uncaught TypeError: gMailInit is undefined

   <anonymous> chrome://messenger/content/messenger.xhtml:270

messenger.xhtml:270:5

   <anonymous> chrome://messenger/content/messenger.xhtml:270

this.asyncConnection is null GlodaDatastore.jsm:1519 Uncaught TypeError: tabmail.getBrowserForSelectedTab is not a function

   getBrowser chrome://messenger/content/mailWindow.js:812
   messagePaneOnResize chrome://communicator/content/contentAreaClick.js:87
   onresize chrome://messenger/content/messenger.xhtml:1

mailWindow.js:812:28 Uncaught TypeError: tabmail.registerTabType is not a function

   <anonymous> chrome://calendar/content/calendar-tabs.js:376

calendar-tabs.js:376:11 Uncaught TypeError: tabmail.getBrowserForSelectedTab is not a function

   getBrowser chrome://messenger/content/mailWindow.js:812
   messagePaneOnResize chrome://communicator/content/contentAreaClick.js:87
   onresize chrome://messenger/content/messenger.xhtml:1

mailWindow.js:812:28 Uncaught (in promise) TypeError: tabmail.registerTabType is not a function

   init chrome://messenger/content/chat/chat-messenger.js:1609

chat-messenger.js:1609:13 Uncaught TypeError: gFolderDisplay is null

   updateCheckedStateForIgnoreAndWatchThreadCmds chrome://messenger/content/mailWindowOverlay.js:192
   goUpdateMailMenuItems chrome://messenger/content/mailWindowOverlay.js:182
   oncommandupdate chrome://messenger/content/messenger.xhtml:1
   onpopupshowing chrome://messenger/content/messenger.xhtml:1

mailWindowOverlay.js:192:1 Uncaught (in promise) TypeError: tabmail.openTab is not a function

   openTab chrome://communicator/content/utilityOverlay.js:262
   openContentTab chrome://communicator/content/utilityOverlay.js:286
   openAddonsMgr chrome://messenger/content/mailCore.js:577
   openAddonsMgr chrome://messenger/content/mailCore.js:549
   oncommand chrome://messenger/content/messenger.xhtml:1

utilityOverlay.js:262:22 Uncaught TypeError: gFolderDisplay is null

   updateCheckedStateForIgnoreAndWatchThreadCmds chrome://messenger/content/mailWindowOverlay.js:192
   goUpdateMailMenuItems chrome://messenger/content/mailWindowOverlay.js:182
   oncommandupdate chrome://messenger/content/messenger.xhtml:1
   onpopupshowing chrome://messenger/content/messenger.xhtml:1

mailWindowOverlay.js:192:1 Uncaught TypeError: gFolderDisplay is null

   updateCheckedStateForIgnoreAndWatchThreadCmds chrome://messenger/content/mailWindowOverlay.js:192
   goUpdateMailMenuItems chrome://messenger/content/mailWindowOverlay.js:182
   oncommandupdate chrome://messenger/content/messenger.xhtml:1
   onpopupshowing chrome://messenger/content/messenger.xhtml:1

mailWindowOverlay.js:192:1

Furhtermore I cannot access:

Tools->Account Settings not Tools->Preferences

Any help?

Best regards Hannes

more options

Выбранное решение

Hi, I was able to fix it myself. It seems that my "global-messages-db.sqlite" in my profile was no accessible any more. I tried to open it using Notepad++ and received a Windows Error "0x80071129" with a cryptic error message. Background info (which makes partially sense in this respect). I have stored my thunderbird profile in my "Documents" Folder on C:\. Parts of this folder (including thunderbird profile) are synced to my synology (for backup reasons). So I suspect that at the very moment of the update the sqlite sync failed.

How I resolved the problem?

I right clicked on start to use Windows Powershell (as Administrator)... I am not sure whether this was necessary. I started chkdsk /F only to learn that it can only be run during the next startup. So I rebooted. And guess what: That resoled the problem!