Red Hat Bugzilla – Bug 608511
Startup of thunderbird 3.1 broken (must delete extension.ini from profile)
Last modified: 2010-07-22 14:25:29 EDT
Thunderbird always worked fine for me including version 3.0.4. The extensions I use simply had their maxVersion raised to 3.1.x, since afaik no API-incompatible changes were introduced towards 3.1.
But since 3.1 now thunderbird doesn't startup anymore. Trying to start it from console looks like it does something, comes back immediately but doesn't show any sign of Thunderbird starting up. I suspect it immediately crashes/shuts down again.
Removing the "extensions.ini" from the profile-directory helps. Thunderbird starts up fine, detects the extensions again (they all work fine) and a new extensions.ini is written to disk. But upon next Thunderbird-restart you'll have to kill that extensions.ini again :-(
This bug affects latest version of lightning (fedora repo) and enigmail (rpmfusion repo).
See #608489 and comments in bodhi update for F-13.
It can be reproduce with a new profile, under i386 and x86_64.
Can't say if it is language (non-english) specific, but, at least "fr" users are affected (and probably "de", as Stefan).
See also https://bugzilla.mozilla.org/show_bug.cgi?id=574458
From comment in update
> xhorak - 2010-07-01 12:12:14 (karma: 0)
> It seems that mozilla is having problem with extensions located in symlinked
> directories (this is case of lightning):
> The shredder problem is covered here:
> Thanks for testing and feedback.
I have test to remove symlinks and copy lightning + lightning-gdata + enigmail in extensions folder. Thunderbird works fine.
- as thunderbird (like firefox) folder seems now stable /usr/lib(64)/thunderbird-3.1 for all minor release
- as a new major version will change folder, but also (generally) breaks plugin compatibility
I think we probably could directly install lightning + enigmail in extension without use the symlink workaround (required in previous fedora version)
Other solution is to wait for a fix to mozilla bug 574458
What your thoughts ?
Well https://bugzilla.redhat.com/show_bug.cgi?id=574458 apparently won't be fixed since a fix for https://bugzilla.mozilla.org/show_bug.cgi?id=551152 is in Trunk:
they've indicated they aren't interested in backporting the changes. there's
nothing more to discuss anywhere.
and any other bug reports will just get closed. Apparently that counts as fixed.
This seems to be fixed in 3.1.1.