spun off from bug 286299 comment 27: extensions or themes installed in Thunderbird 1.0.x don't appear on 1st launch of trunk build. recipe ------ 1. created fresh profile with Tbird 1.0.2. 2. installed Flashgot and Timestamp extensions from UMO. 3. installed and selected to use the Charamel theme. 4. restarted Tbird 1.0.2 to confirm that the extensions and theme worked fine. 5. started 2005061505-trunk Tbird build (tested on Mac OS X 10.4.1). results: got the update wizard, went through that (no updates found, actually). once Tbird trunk started up: * both extensions were listed as active, but their chrome/UI were actually not active at all. * the default Pinstripe theme was used, not Charamel. once I restarted the trunk build, the extensions and theme became active.
I just tried this on Win32 and wasn't able to reproduce. Bug 295732 prevents writing to a couple of the extension files which might be the cause of this bug and appears to affect only Mac OS X and Linux under yet to be determined circumstances. I'll see if I can reproduce on a Mac OS X system hopefully tonight.
I can't think of any reason why this would behave differently in thunderbird than firefox.
I just reproduced this on Mac OS X and this is the Thunderbird version of bug 295729. I am able to comment out the following line in nsExtensionManager.js checkForMismatches and it starts up the first time with compatible extensions and themes enabled and the Charamel theme in use. this._showMismatchWindow(items);
I just tried to duplicate bug 295729 with Firefox and it behaves the exact same way as Thunderbird in that there is no longer a crash but the call to _showMismatchWindow hangs and extensions are not fully installed, etc.
This now WFM on Mac OS X Firefox... could someone please check if this bug is still present in Mac OS X Thunderbird and if now resolve this bug?
I've just updated on windows xp from tb1.0.5 to tb1.1a2 and can't completely reproduce this bug. I've installed the Foxytunes and Image Zoom extensions before the update just for testing purposes and there were some little problems. The Foxytunes extension got disabled, but the Image Zoom extension didn't get disabled (and caused a xul error in the status bar) although there were no updates avalaible for both of them.
(In reply to comment #5) > This now WFM on Mac OS X Firefox... could someone please check if this bug is > still present in Mac OS X Thunderbird and if now resolve this bug? This w4m going from tbird 1.0.2 (old, I know!) to 1.1alpha2. I had the Charamel theme v0.93 and FlashGot v0.5.9.4, both which displayed fine upon starting 1.1a2. marking w4m.
Status: NEW → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → WORKSFORME
forgot to mention: tested on Mac OS X 10.4.2.
I just saw it with trunk version 1.0+ (20050726) on Linux - after automatic update I had to restart twice for a used Theme to become active.
(In reply to comment #9) > I just saw it with trunk version 1.0+ (20050726) on Linux - after automatic > update I had to restart twice for a used Theme to become active. how odd --this also now w4m on linux (fedora core 3, using the Gnome desktop with the default Gnome theme), going from tbird 1.0.6 to 1.1alpha2 (using the same third party theme and extension: Charamel 0.93 and Flashgot 0.5.9.4).
You need to log in before you can comment on or make changes to this bug.