Thunderbird 91 extensions don't load
When TB recently updated from 78.14.0 (64 bit) to 91.2.0 (64bit), all my extensions did not load. I reviewed and verified they are compatible with 91. Toggling the enable/disable in add-ons manager did nothing although some mysteriously did get disabled. Restarting TB from scratch had no impact. (I note that closing TB tends to cause a crash.)
I was able to get the most extensions to function if I re-installed them into TB but the minute I closed TB and restarted, they all went away again.
I note that clicking on "Check for Updates" causes an "Updating add-ons" message to appear.....forever.
What gives? This is only slightly less painful than the transition to 78.....argh!
Valgt løsning
Reporter,
I don't think making a new profile is a proper solution or workaround here (though I haven't thoroughly read everything). But if it comes to that, don't delete your old profile.
Perhaps you are seeing Bug 1732515 - TB 91 - ANY addon causes problems - no add-ons work and does not shut down cleanly?
If not, I would file a bug report https://bugzilla.mozilla.org/enter_bug.cgi?product=Thunderbird
Læs dette svar i sammenhæng 👍 1Alle svar (1)
A note of thanks to the TB team.
I've tested the workaround with both my WIN10 TB91 and WIN7 machines and it appears to work.
In addition to my Win10 TB78-TB91 transition debacle I had another WIN7 machine running TB78 with an identical profile that was poised to do the upgrade on restart. I was able to keep the WIN7 TB78 instance running while sorting my WIN10 instance issues but was nearing a point where I was being forced to reboot my WIN7 TB78 machine. Per the workaround, I reconfigured the profile to disable the enable/disable online prompt and held my breath as I restarted the machine and TB.
The fabulous news was that the TB78-91 transition went without much of a hitch. I did lose a few add-ons to compatibility issues but the core set were updated and booted as enabled.
I only wish this workaround was known about two weeks earlier! I could have avoided rebuilding the entire profile on the WIN10 machine but I really appreciate the support.
Bravo team for tracking this down.