Mozilla/5.0 (X11; Linux x86_64; rv:7.0a1) Gecko/20110525 Firefox/7.0a1 SeaMonkey/2.2a1pre Build ID (timestamp): 20110525003002 Yesterday I was still using a SeaMonkey 2.2a1pre build with rv:6.0a1 When starting up this build, suddenly all my extensions turn up enabled, including some which, like e.g. HTML Validator, were incompatible at code level with Gecko 2.0 and later and had been intentionally disabled while waiting for their authors to make the necessary changes.

Please attach a copy of extensions.sqlite and extensions.ini from your profile

When I read comment #1 I had already gone to Safe Mode to disable what I thought were the most "dangerous" extensions (but not yet restarted out of Safe Mode). I'm attaching two additional files in the hope that they will help you, if necessary, to reconstruct the history of the two you asked for.

What time did you start up the new build for the first time? Around 11pm? How old was the previous build you were running?

(In reply to comment #7) > What time did you start up the new build for the first time? Around 11pm? A few minutes before reporting this bug. I had installed this build at 23:04:36 CEST (14:04:36 PDT) which gives you a "not earlier than" point. My CMOS clock is set to CEST. > How old was the previous build you were running? Mozilla/5.0 (X11; Linux x86_64; rv:6.0a1) Gecko/20110417 Firefox/6.0a1 SeaMonkey/2.2a1pre ID:20110417003006

P.S. The reasons I was still on that build from April 17 were: - ChatZilla bug 587629 (now FIXED) - SeaMonkey bug 650785 (which might be due to a misbehaving extension, I'll have to investigate) - perma-orange on SeaMonkey trunk up to and including yesterday.

Ok, that matches better my first theory. Between your previous build and the latest build there has been a schema change in the database and the log file shows an error going through the migration path which makes sense. I think the error might happen when there is also a pending add-on upgrade though I can't immediately see why that error would suddenly re-enable every extensions, if everything it should disable everything, but hopefully testing this scenario should reveal more.

(In reply to comment #10) > Ok, that matches better my first theory. Between your previous build and the > latest build there has been a schema change in the database and the log file > shows an error going through the migration path which makes sense. I think > the error might happen when there is also a pending add-on upgrade though I > can't immediately see why that error would suddenly re-enable every > extensions, if everything it should disable everything, but hopefully > testing this scenario should reveal more. There was indeed a pending add-on upgrade for lightning.xpi, gdata-provider.xpi, and all SeaMonkey 2.2a1pre language packs.

In reply to comment #10 P.S. About enabling vs. disabling: maybe my extensions.checkCompatibility.* preferences (see the attached about:support) could have made a difference?

(In reply to comment #12) > In reply to comment #10 > P.S. About enabling vs. disabling: maybe my extensions.checkCompatibility.* > preferences (see the attached about:support) could have made a difference? That overrides the compatibility, but as you say HTML validator was disabled by you (and the database confirms that) yet it still appears in extensions.ini. Did the add-ons look disabled in the add-ons manager?

(In reply to comment #13) > (In reply to comment #12) > > In reply to comment #10 > > P.S. About enabling vs. disabling: maybe my extensions.checkCompatibility.* > > preferences (see the attached about:support) could have made a difference? > > That overrides the compatibility, but as you say HTML validator was disabled > by you (and the database confirms that) yet it still appears in > extensions.ini. Did the add-ons look disabled in the add-ons manager? In Safe Mode, they all had both (disabled) which is a Safe Mode artefact, and a [Disable] button showing that they were regarded as Enabled, with the exception of a few not compatible at all with SeaMonkey, which had neither [Enable] nor [Disable] (these are: deviantSkin, functions for keyconfig, JS Console output redirector). (I suppose that some earlier version of them had a SeaMonkey <targetApplication> section in install.rdf) Before going to Safe Mode, I didn't check about:addons; about:support started up with no extensions listed at all, then I had a crash when reloading it and another crash on restart from Breakpad. Then I used "Help → Restart with Add-ons Disabled", which crashed at closedown yet still restarted in Safe Mode. I am still in Safe Mode ATM. I got an error page ("C library not found", http://users.skynet.be/mgueury/mozilla/no_tidy_lib.html) from HTML validator at first startup with this build, obviously showing that the extension was running.

Don't know if relevant: immediately before insalling this build, I had to kill the previous build because of a hang, see bug 570316 comment #25; then I restarted the X server because of an openSUSE software update which required it.

In tests I've managed to reproduce the situation I described in comment 10 and it does give the same error as your log and does leave things broken, however it doesn't lead to add-ons being enabled when they shouldn't be, so either there is something additional happening or that is just a red herring.

Is it at all possible that you ran an older build of Seamonkey (something from gecko 1.9.2) just prior to the 7.0a1 based version? That might explain how extensions.ini got so populated

(In reply to comment #17) > Is it at all possible that you ran an older build of Seamonkey (something > from gecko 1.9.2) just prior to the 7.0a1 based version? That might explain > how extensions.ini got so populated Not on that profile. "Just prior" to the 7.0a1 based version I was using the 6.0a1 based version mentioned in comment #8. Of course that profile has been used with a 1.9.1 based version when that was trunk, but it was quite some time ago. There never was a SeaMonkey build based on Gecko 1.9.2 (SeaMonkey went straight from 1.9.1 to 1.9.3, then the latter morphed into 2.0 then 5.0 etc.) -- see the history of SeaMonkey versions and the Gecko versions they were based on at http://en.wikipedia.org/wiki/SeaMonkey#Release_history In order to use the built-in extensions when they were moved from extensions/ to distribution/extensions/ in the unpacked seamonkey-*.tar.bz2 (after bug 627240 was FIXED) I had to "fake" a version upgrade by setting extensions.lastAppVersion to 2.2a0 (instead of 2.2a1pre) then restarting SeaMonkey. At that time, disabled extensions remained disabled. Similarly, at a later time the same maneuver was required to start using the new version of ChatZilla after bug 507629 was FIXED. The last use of a SeaMonkey based on Gecko 1.9.1 on this profile was much earlier than that.

Oops: ...ChatZilla after bug 587629 was FIXED...

Do you have an extensions.rdf in that profile? Might be worth looking at nonetheless. I was comparing the extensions.ini and extensions.sqlite and one thing that struck me as odd was that all but 3 extensions listed in sqlite were also in extensions.ini: deviantSkin functions for keyconfig JS Console output redirector Any idea what might be special about those three, were they installed or uninstalled immediately before the upgrade or something?

(In reply to comment #20) > Do you have an extensions.rdf in that profile? Might be worth looking at > nonetheless. > > I was comparing the extensions.ini and extensions.sqlite and one thing that > struck me as odd was that all but 3 extensions listed in sqlite were also in > extensions.ini: > > deviantSkin > functions for keyconfig > JS Console output redirector > > Any idea what might be special about those three, were they installed or > uninstalled immediately before the upgrade or something? They were installed long ago, long before the extensions were left packed in the profile. AFAICT, their present install.rdf includes no <targetApplication> section for SeaMonkey but only for Firefox. Someday when I come around to it I may remove them altogether.

P.S. There is no extensions.rdf in that profile: not at top level and not in any subfolder at any depth.

(In reply to comment #21) > (In reply to comment #20) > > Do you have an extensions.rdf in that profile? Might be worth looking at > > nonetheless. > > > > I was comparing the extensions.ini and extensions.sqlite and one thing that > > struck me as odd was that all but 3 extensions listed in sqlite were also in > > extensions.ini: > > > > deviantSkin > > functions for keyconfig > > JS Console output redirector > > > > Any idea what might be special about those three, were they installed or > > uninstalled immediately before the upgrade or something? > > They were installed long ago, long before the extensions were left packed in > the profile. AFAICT, their present install.rdf includes no > <targetApplication> section for SeaMonkey but only for Firefox. Someday when > I come around to it I may remove them altogether. Oh I realised that those are the only ones actually marked appDisabled in the DB. So so far I can reproduce a failure here, but there is still something missing where for some reason we ignored the fact that userDisabled was set for about 30 add-ons and still wrote them out to extensions.ini. I'm running out of ideas for why that might have happened unfortunately.

Mozilla/5.0 (X11; Linux x86_64; rv:7.0a1) Gecko/20110604 Firefox/7.0a1 SeaMonkey/2.2a1pre ID:20110604003003 Happened again on restart from crash caused by clicking Reload on about:support where no extensions were listed (which is unusual: about:support is one tab of my "multitab homepage" loaded at every startup, and normally all extensions are listed with version, enabled/disabled status, etc.). Got an additional crash on first attempt to type this comment. I'm attaching a tarball with extensions.* from my profile taken soon after that (after 2nd Breakpad restart, i.e., SeaMonkey was already running again). Between yesterday and today, Console² has been upgraded and enabled (the new "testing" version boasts trunk compatibility) -- could this have upped my number of enabled extensions to some critical number? On this new restart, the browser is somewhat b0rken, I cannot open a second tab. After submitting this comment, I'm going to restart in Safe Mode, try to remember which extensions were user-disabled, and disable them again.

P.S. In case it wasn't clear, this new attachment is in .tar.gz format (not .zip and not .tar.bz2).

P.P.S. I had the usual (bug 659842) crash (which I'm getting at every shutdown now) from "Restart with Add-ons Disabled", but somehow this crash didn't get itself into about:crashes. The following about:crashes entries might perhaps interest you: bp-347bb726-0ff7-42cf-ba50-6adf22110604 04/06/11 16:33 trying to type a first version of comment #24 bp-b373949c-f5cc-4e84-a8cf-a05de2110604 04/06/11 16:26 Clicking Reload in about:support (on restart from which all extensions were found enabled)

I notice that the "Recent updates" EM tab says HTML validator (which I'm keeping disabled until it will have a linux-x86_64 version supporting SeaMonkey trunk) was updated (updated itself?) today to version 0.9.0.5 (I don't know where it comes from: I see only 0.9.0.4 for Windows Firefox at AMO, 0.9.0.6 for Windows and 0.9.0.4 for other platforms at http://users.skynet.be/mgueury/mozilla/download_090.html -- and BTW the EM also says that this version is "incompatible with SeaMonkey 2.2a1pre"): ???... This prompted me to click "Reset all addons to update manually" at the bottom of the drop-down to make sure *my* default is enforced on all addons.

I am seeing this consistently when I switch between versions or OSs. Every time I switch all disabled extensions are re-enabled. For example when I switch between FF 3.6.17 and FF 4.0.1 or between OSX FF 4.0.1 and Windows XP FF 4.0.1. It's quite annoying, but also very reproducible if you want me to try something out. I've attached a zip of my extensions.* files.

(In reply to comment #29) > I am seeing this consistently when I switch between versions or OSs. Every > time I switch all disabled extensions are re-enabled. For example when I > switch between FF 3.6.17 and FF 4.0.1 or between OSX FF 4.0.1 and Windows XP > FF 4.0.1. > It's quite annoying, but also very reproducible if you want me to try > something out. > I've attached a zip of my extensions.* files. Do you have any of the extensions.checkCompatibility prefs set to false? Can you attach extensions.sqlite and extensions.ini from OSX on 4.0.1 and then on Windows on 4.0.1 (I'm assuming you're copying the entire profile across from one to the other, say if that isn't so). Also for the 3.6 -> 4.0 case we won't migrate the disabled state of add-ons if 4.0 has already been used in a profile, so if you run 4.0, look at what is disabled, run 3.6 and then run 4.0 again, the set of disabled add-ons shouldn't have changed. Is that the case? What should work is if you run 3.6 on a fresh profile and then run 4.0, no manually disabled extensions should get re-enabled in that case. Is that working, if not for what extensions is it not working?

Yes, all extensions.checkCompatibility are set to false (I am using Nightly Tester Tools). The profile is the same directory on a shared partition between Windows and Mac (BootCamp). I'm assuming you asking for before/after. I will try to remember next time I switch between them. I'm not seeing the problem now between 3.6/4.0, not sure if it was fixed or I got them locked in as you described. While we are on the subject, when moving between 4.0.1 and 5.0 (either way) the extension Java Console (a global) keeps getting re-enabled. I've attached the dgr.extensions.4to5before.zip and dgr.extensions.4to5after.zip.

The Java Console is something of a special beast in that in their infinite wisdom Sun decided that every new version of the extensions should have its own unique ID. You have the following installed: 6.0.24 in C:\Program Files\Mozilla Firefox 4\extensions with ID {CAFEEFAC-0016-0000-0024-ABCDEFFEDCBA} 6.0.26 in C:\Program Files\Mozilla Firefox 5\extensions with ID {CAFEEFAC-0016-0000-0026-ABCDEFFEDCBA} The reason you lose the disabled setting is simply that with different IDs Firefox thinks they are two different extensions. Bug 654131 (and others) is about attempting to clean up these old things.

Maybe this problem first appeared just after installing the Addon Compatibility Reporter (I'm not sure); but recently there was an update to the ACR (version 0.8.6, which appeared at AMO on July 13). After installing that update, all user-disabled extensions (other than the few which have no SeaMonkey targetApplication section) suddenly woke up again, and several of them loaded web error pages. I had to hand-disable them again. (Sorry, I don't have an extensions.sqlite from when it happened.)

No version change this time, but all extensions were enabled between one run and the next. I have a stdout/stderr log, which looks ominous to me (the dates were output between successive runs of SeaMonkey): inspection of the log seems to indicate upgrade-downgrade across a change in schema. Mon Nov 7 08:57:30 CET 2011 *** LOG addons.xpi: startup *** LOG addons.xpi: Ignoring file entry whose name is not a valid add-on ID: /root/.mozilla/seamonkey/nexrdon9.default/extensions/sm_exts.txt *** LOG addons.xpi: checkForChanges *** LOG addons.xpi: Opening database *** LOG addons.xpi: Add-on modern@themes.mozilla.org modified in app-global *** LOG addons.xpi: Add-on {972ce4c6-7e08-4474-a285-3208198ce6fd} modified in app-global *** LOG addons.xpi: Updating database with changes to installed add-ons *** LOG addons.xpi: Updating add-on states *** LOG addons.xpi: Writing add-ons list *** LOG addons.xpi: Loading bootstrap scope from /root/.mozilla/seamonkey/nexrdon9.default/extensions/restartless.restart@erikvold.com.xpi *** LOG addons.xpi: Calling bootstrap method startup on restartless.restart@erikvold.com version 8 *** LOG addons.xpi: Loading bootstrap scope from /root/.mozilla/seamonkey/nexrdon9.default/extensions/aboutstartup@glandium.org.xpi *** LOG addons.xpi: Calling bootstrap method startup on aboutstartup@glandium.org version 0.1.5 *** LOG addons.xpi: Loading bootstrap scope from /root/.mozilla/seamonkey/nexrdon9.default/extensions/dominant.color@agadak.net.xpi *** LOG addons.xpi: Calling bootstrap method startup on dominant.color@agadak.net version 2 *** LOG addons.xpi: Loading bootstrap scope from /root/.mozilla/seamonkey/nexrdon9.default/extensions/tabstats@glandium.org.xpi *** LOG addons.xpi: Calling bootstrap method startup on tabstats@glandium.org version 0.0.2 *** LOG addons.xpi: shutdown *** LOG addons.xpi: Opening database *** ERROR addons.xpi: Failed to open database (1st attempt): [Exception... "Component returned failure code: 0x80630001 (NS_ERROR_STORAGE_BUSY) [mozIStorageService.openUnsharedDatabase]" nsresult: "0x80630001 (NS_ERROR_STORAGE_BUSY)" location: "JS frame :: resource://gre/modules/XPIProvider.jsm :: XPIDB_openDatabaseFile :: line 4136" data: no] *** LOG addons.xpi: Creating database schema *** WARN addons.xpi: Rebuilding add-ons database from installed extensions. *** ERROR addons.xpi: Error processing file changes: TypeError: this.installLocations is null Mon Nov 7 09:30:16 CET 2011 *** LOG addons.xpi: startup *** LOG addons.xpi: Ignoring file entry whose name is not a valid add-on ID: /root/.mozilla/seamonkey/nexrdon9.default/extensions/sm_exts.txt *** LOG addons.xpi: checkForChanges *** LOG addons.xpi: No changes found *** LOG addons.xpi: Loading bootstrap scope from /root/.mozilla/seamonkey/nexrdon9.default/extensions/restartless.restart@erikvold.com.xpi *** LOG addons.xpi: Calling bootstrap method startup on restartless.restart@erikvold.com version 8 *** LOG addons.xpi: Loading bootstrap scope from /root/.mozilla/seamonkey/nexrdon9.default/extensions/aboutstartup@glandium.org.xpi *** LOG addons.xpi: Calling bootstrap method startup on aboutstartup@glandium.org version 0.1.5 *** LOG addons.xpi: Loading bootstrap scope from /root/.mozilla/seamonkey/nexrdon9.default/extensions/dominant.color@agadak.net.xpi *** LOG addons.xpi: Calling bootstrap method startup on dominant.color@agadak.net version 2 *** LOG addons.xpi: Opening database *** LOG addons.xpi: Loading bootstrap scope from /root/.mozilla/seamonkey/nexrdon9.default/extensions/tabstats@glandium.org.xpi *** LOG addons.xpi: Calling bootstrap method startup on tabstats@glandium.org version 0.0.2 *** WARN addons.manager: Exception calling callback: TypeError: addon is null *** LOG addons.xpi: shutdown Mon Nov 7 10:00:16 CET 2011 *** LOG addons.xpi: startup *** LOG addons.xpi: Ignoring file entry whose name is not a valid add-on ID: /root/.mozilla/seamonkey/nexrdon9.default/extensions/sm_exts.txt *** LOG addons.xpi: checkForChanges *** LOG addons.xpi: Opening database *** LOG addons.xpi: Migrating data from schema 8 *** LOG addons.xpi: Opening database *** LOG addons.xpi: Creating database schema *** LOG addons.xpi: New add-on skypilot@projectit.com installed in app-profile *** LOG addons.xpi: New add-on langpack-cs@seamonkey.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on allamerican@projectit.com installed in app-profile *** LOG addons.xpi: New add-on formhistory@yahoo.com installed in app-profile *** LOG addons.xpi: New add-on charpick@ryanium.com installed in app-profile *** LOG addons.xpi: New add-on {2bc419d0-6cf3-11da-8494-000a95be0946} installed in app-profile *** LOG addons.xpi: New add-on langpack-nl@seamonkey.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on debugQA@mozilla.org installed in app-profile *** LOG addons.xpi: New add-on {4b15ab39-47d7-4b41-9279-9291dcfc8b61} installed in app-profile *** LOG addons.xpi: New add-on {9669CC8F-B388-42FE-86F4-CB5E7F5A8BDC} installed in app-profile *** LOG addons.xpi: New add-on {5399A550-C3A6-11DE-B55D-51FD55D89593} installed in app-profile *** LOG addons.xpi: New add-on {5ffa002f-7e75-4b01-93aa-9c102f58b0ad} installed in app-profile *** LOG addons.xpi: New add-on restartless.restart@erikvold.com installed in app-profile *** LOG addons.xpi: Loading bootstrap scope from /root/.mozilla/seamonkey/nexrdon9.default/extensions/restartless.restart@erikvold.com.xpi *** LOG addons.xpi: Calling bootstrap method uninstall on restartless.restart@erikvold.com version 8 *** LOG addons.xpi: Loading bootstrap scope from /root/.mozilla/seamonkey/nexrdon9.default/extensions/restartless.restart@erikvold.com.xpi *** LOG addons.xpi: Calling bootstrap method install on restartless.restart@erikvold.com version 8 *** LOG addons.xpi: New add-on {3b56bcc7-54e5-44a2-9b44-66c3ef58c13e} installed in app-profile *** LOG addons.xpi: New add-on langpack-en-GB@seamonkey.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on ohcanada@projectit.com installed in app-profile *** LOG addons.xpi: New add-on aboutstartup@glandium.org installed in app-profile *** LOG addons.xpi: Loading bootstrap scope from /root/.mozilla/seamonkey/nexrdon9.default/extensions/aboutstartup@glandium.org.xpi *** LOG addons.xpi: Calling bootstrap method uninstall on aboutstartup@glandium.org version 0.1.5 *** LOG addons.xpi: Loading bootstrap scope from /root/.mozilla/seamonkey/nexrdon9.default/extensions/aboutstartup@glandium.org.xpi *** LOG addons.xpi: Calling bootstrap method install on aboutstartup@glandium.org version 0.1.5 *** LOG addons.xpi: New add-on langpack-zh-CN@seamonkey.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on {1018e4d6-728f-4b20-ad56-37578a4de76b} installed in app-profile *** LOG addons.xpi: New add-on itsalltext@docwhat.gerf.org installed in app-profile *** LOG addons.xpi: New add-on SQLiteManager@mrinalkant.blogspot.com installed in app-profile *** LOG addons.xpi: New add-on EarlyBlue@kairo.at installed in app-profile *** LOG addons.xpi: New add-on duplicate-this-tab@mozilla.org installed in app-profile *** LOG addons.xpi: New add-on {dc5d9a10-2736-11da-8cd6-0800200c9a66} installed in app-profile *** LOG addons.xpi: New add-on LCARStrek@kairo.at installed in app-profile *** LOG addons.xpi: New add-on {a62ef8ec-5fdc-40c2-873c-223b8a6925cc} installed in app-profile *** LOG addons.xpi: New add-on tito@bug554615 installed in app-profile *** LOG addons.xpi: New add-on eo-EO@dictionaries.addons.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on {d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d} installed in app-profile *** LOG addons.xpi: New add-on {3C9A65A6-9563-4485-BA4A-4BCD698BCFB4} installed in app-profile *** LOG addons.xpi: New add-on mandelbrot@kairo.at installed in app-profile *** LOG addons.xpi: New add-on langpack-ro@seamonkey.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on langpack-ja-JP-mac@seamonkey.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on {6AC85730-7D0F-4de0-B3FA-21142DD85326} installed in app-profile *** LOG addons.xpi: New add-on inspector@mozilla.org installed in app-profile *** LOG addons.xpi: New add-on zegrel@gmail.com installed in app-profile *** LOG addons.xpi: New add-on dominant.color@agadak.net installed in app-profile *** LOG addons.xpi: Loading bootstrap scope from /root/.mozilla/seamonkey/nexrdon9.default/extensions/dominant.color@agadak.net.xpi *** LOG addons.xpi: Calling bootstrap method uninstall on dominant.color@agadak.net version 2 *** LOG addons.xpi: Loading bootstrap scope from /root/.mozilla/seamonkey/nexrdon9.default/extensions/dominant.color@agadak.net.xpi *** LOG addons.xpi: Calling bootstrap method install on dominant.color@agadak.net version 2 *** LOG addons.xpi: New add-on {c671b520-abe9-11d8-8ebc-000c6e787bf7} installed in app-profile *** LOG addons.xpi: New add-on remotexulmanager@xulforge.com installed in app-profile *** LOG addons.xpi: New add-on {71e95839-6f7e-470d-be54-77012fec6313} installed in app-profile *** LOG addons.xpi: New add-on vivamexico@projectit.com installed in app-profile *** LOG addons.xpi: New add-on langpack-sk@seamonkey.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on {25ddc458-6ee0-4be6-850f-72b445e4200d} installed in app-profile *** LOG addons.xpi: New add-on abpwatcher@adblockplus.org installed in app-profile *** LOG addons.xpi: New add-on {a2f5c06d-41fe-4444-b9f4-4a3fa25adc77} installed in app-profile *** LOG addons.xpi: New add-on {25A1388B-6B18-46c3-BEBA-A81915D0DE8F} installed in app-profile *** LOG addons.xpi: New add-on langpack-pl@seamonkey.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on langpack-lt@seamonkey.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on slimaddonmanager@opendfki.de installed in app-profile *** LOG addons.xpi: New add-on openinbrowser@www.spasche.net installed in app-profile *** LOG addons.xpi: New add-on {1280606b-2510-4fe0-97ef-9b5a22eafe80} installed in app-profile *** LOG addons.xpi: New add-on pdmts@caligonstudios.com installed in app-profile *** LOG addons.xpi: New add-on {e2fda1a4-762b-4020-b5ad-a41df1933103} installed in app-profile *** LOG addons.xpi: New add-on {e968fc70-8f95-4ab9-9e79-304de2a71ee1} installed in app-profile *** LOG addons.xpi: New add-on {08ab63e1-c4bc-4fb7-a0b2-55373b596eb7} installed in app-profile *** LOG addons.xpi: New add-on xulmine@mozdev.org installed in app-profile *** LOG addons.xpi: New add-on {723AAF16-AF1F-4404-A5D7-0BFE39766605} installed in app-profile *** LOG addons.xpi: New add-on launchy@gemal.dk installed in app-profile *** LOG addons.xpi: New add-on de-AT@dictionaries.addons.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on {11483926-db67-4190-91b1-ef20fcec5f33} installed in app-profile *** LOG addons.xpi: New add-on langpack-pt-PT@seamonkey.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on langpack-uk@seamonkey.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on langpack-it@seamonkey.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on langpack-fi@seamonkey.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on compatibility@addons.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on quickfolders@curious.be installed in app-profile *** LOG addons.xpi: New add-on classicishaddonmanager@dagger2-addons.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on langpack-es-AR@seamonkey.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on {F8147CF4-B9E3-445B-AA87-081ED66548F8} installed in app-profile *** LOG addons.xpi: New add-on {DF3074AA-1298-95DF-4315-72E3C22B503C} installed in app-profile *** LOG addons.xpi: New add-on {a300a000-5e21-4ee0-a115-9ec8f4eaa92b} installed in app-profile *** LOG addons.xpi: New add-on {0538E3E3-7E9B-4d49-8831-A227C80A7AD3} installed in app-profile *** LOG addons.xpi: New add-on {F8147CF4-B9E3-445B-AA87-081ED66548F9} installed in app-profile *** LOG addons.xpi: New add-on langpack-tr@seamonkey.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on langpack-ka@seamonkey.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on langpack-be@seamonkey.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on Seazilla@addons.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on {122352a8-6caf-46ca-998c-784e320cad7c} installed in app-profile *** LOG addons.xpi: New add-on mintrayr@tn123.ath.cx installed in app-profile *** LOG addons.xpi: New add-on langpack-nb-NO@seamonkey.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on {a4ebc7e4-5ffe-4811-b9c6-a782bba8c1c2} installed in app-profile *** LOG addons.xpi: New add-on {9294da78-ac50-4658-a867-84b1275ed227} installed in app-profile *** LOG addons.xpi: New add-on validator@totalvalidator.com installed in app-profile *** LOG addons.xpi: New add-on keyconfig@dorando installed in app-profile *** LOG addons.xpi: New add-on venerablemodern@projectit.com installed in app-profile *** LOG addons.xpi: New add-on fr-classique-reforme1990@dictionaries.addons.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on {F8147CF4-B9E3-445B-AA87-081ED66548FC} installed in app-profile *** LOG addons.xpi: New add-on {59c81df5-4b7a-477b-912d-4e0fdf64e5f2} installed in app-profile *** LOG addons.xpi: New add-on jid0-PyqYRL06UeTdFNkqr76DvHpdKTU@jetpack installed in app-profile *** LOG addons.xpi: Loading bootstrap scope from /root/.mozilla/seamonkey/nexrdon9.default/extensions/jid0-PyqYRL06UeTdFNkqr76DvHpdKTU@jetpack *** LOG addons.xpi: Calling bootstrap method install on jid0-PyqYRL06UeTdFNkqr76DvHpdKTU@jetpack version 1.0 *** LOG addons.xpi: New add-on langpack-ca@seamonkey.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on elemhidehelper@adblockplus.org installed in app-profile *** LOG addons.xpi: New add-on tabstats@glandium.org installed in app-profile *** LOG addons.xpi: Loading bootstrap scope from /root/.mozilla/seamonkey/nexrdon9.default/extensions/tabstats@glandium.org.xpi *** LOG addons.xpi: Calling bootstrap method uninstall on tabstats@glandium.org version 0.0.2 *** LOG addons.xpi: Loading bootstrap scope from /root/.mozilla/seamonkey/nexrdon9.default/extensions/tabstats@glandium.org.xpi *** LOG addons.xpi: Calling bootstrap method install on tabstats@glandium.org version 0.0.2 *** LOG addons.xpi: New add-on mozillium@projectit.com installed in app-profile *** LOG addons.xpi: New add-on firebug@software.joehewitt.com installed in app-profile *** LOG addons.xpi: New add-on jid0-Yia1AkUofBLANOmOYle1V8n713I@jetpack installed in app-profile *** LOG addons.xpi: Loading bootstrap scope from /root/.mozilla/seamonkey/nexrdon9.default/extensions/jid0-Yia1AkUofBLANOmOYle1V8n713I@jetpack.xpi *** LOG addons.xpi: Calling bootstrap method install on jid0-Yia1AkUofBLANOmOYle1V8n713I@jetpack version 0.0.2 *** LOG addons.xpi: New add-on {8620c15f-30dc-4dba-a131-7c5d20cf4a29} installed in app-profile *** LOG addons.xpi: New add-on thunzilla@dolske.net installed in app-profile *** LOG addons.xpi: New add-on langpack-gl@seamonkey.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on american@projectit.com installed in app-profile *** LOG addons.xpi: New add-on {15a7ef52-8a77-426e-9e17-e21af257d7c8} installed in app-profile *** LOG addons.xpi: New add-on langpack-hu@seamonkey.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on langpack-sv-SE@seamonkey.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on {e5ddc45e-eeee-ebee-e50e-e2b445e4200e} installed in app-profile *** LOG addons.xpi: New add-on {eecba28f-b68b-4b3a-b501-6ce12e6b8696} installed in app-profile *** LOG addons.xpi: New add-on {68F35A55-B497-11DB-7897-687ADF132DA7} installed in app-profile *** LOG addons.xpi: New add-on langpack-de@seamonkey.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on {b243fe83-b8a7-47de-855d-21d865243d5d} installed in app-profile *** LOG addons.xpi: New add-on toyfactory@projectit.com installed in app-profile *** LOG addons.xpi: New add-on {bf591015-b599-4125-9428-3cb746ddca31} installed in app-profile *** LOG addons.xpi: New add-on nl-NL@dictionaries.addons.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on jid0-qBnIpLfDFa4LpdrjhAC6vBqN20Q@jetpack installed in app-profile *** LOG addons.xpi: Loading bootstrap scope from /root/.mozilla/seamonkey/nexrdon9.default/extensions/jid0-qBnIpLfDFa4LpdrjhAC6vBqN20Q@jetpack *** LOG addons.xpi: Calling bootstrap method install on jid0-qBnIpLfDFa4LpdrjhAC6vBqN20Q@jetpack version 1.9 *** LOG addons.xpi: New add-on raceday@projectit.com installed in app-profile *** LOG addons.xpi: New add-on langpack-es-ES@seamonkey.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on xsidebar@aleytys.pc.my installed in app-profile *** LOG addons.xpi: New add-on dlman@kairo.at installed in app-profile *** LOG addons.xpi: New add-on {32d96adf-23fc-403d-a1c8-e5cf6a019bee} installed in app-profile *** LOG addons.xpi: New add-on {8f8fe09b-0bd3-4470-bc1b-8cad42b8203a} installed in app-profile *** LOG addons.xpi: New add-on {f13b157f-b174-47e7-a34d-4815ddfdfeb8} installed in app-profile *** LOG addons.xpi: New add-on savedpasswordeditor@daniel.dawson installed in app-profile *** LOG addons.xpi: New add-on langpack-fr@seamonkey.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on {af79f858-4b25-4ca4-822b-b5db1be628fc} installed in app-profile *** LOG addons.xpi: New add-on {1feca320-6b4d-11df-a08a-0800200c9a66} installed in app-profile *** LOG addons.xpi: New add-on orbit@miksworld.de installed in app-profile *** LOG addons.xpi: New add-on langpack-ru@seamonkey.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on langpack-ja@seamonkey.mozilla.org installed in app-profile *** LOG addons.xpi: New add-on modern@themes.mozilla.org installed in app-global *** LOG addons.xpi: New add-on {972ce4c6-7e08-4474-a285-3208198ce6fd} installed in app-global *** LOG addons.xpi: Updating database with changes to installed add-ons *** LOG addons.xpi: Updating add-on states *** LOG addons.xpi: Writing add-ons list *** LOG addons.xpi: Calling bootstrap method startup on restartless.restart@erikvold.com version 8 *** LOG addons.xpi: Calling bootstrap method startup on aboutstartup@glandium.org version 0.1.5 *** LOG addons.xpi: Calling bootstrap method startup on dominant.color@agadak.net version 2 *** LOG addons.xpi: Calling bootstrap method startup on jid0-PyqYRL06UeTdFNkqr76DvHpdKTU@jetpack version 1.0 *** LOG addons.xpi: Calling bootstrap method startup on tabstats@glandium.org version 0.0.2 *** LOG addons.xpi: Calling bootstrap method startup on jid0-Yia1AkUofBLANOmOYle1V8n713I@jetpack version 0.0.2 *** WARN addons.xpi: Exception running bootstrap method startup on jid0-Yia1AkUofBLANOmOYle1V8n713I@jetpack: Error opening input stream (invalid filename?) *** LOG addons.xpi: Calling bootstrap method startup on jid0-qBnIpLfDFa4LpdrjhAC6vBqN20Q@jetpack version 1.9 error: An exception occurred. Traceback (most recent call last): File "resource://jid0-qbniplfdfa4lpdrjhac6vbqn20q-addon-kit-lib/context-menu.js", line 47, in ].join("")); Error: The context-menu module currently supports only Firefox. In the future we would like it to support other applications, however. Please see https://bugzilla.mozilla.org/show_bug.cgi?id=560716 for more information. error: An exception occurred. Traceback (most recent call last): File "resource://jid0-pyqyrl06uetdfnkqr76dvhpdktu-api-utils-lib/hidden-frame.js", line 56, in ].join("")); Error: The hidden-frame module currently supports only Firefox and Thunderbird. In the future, we would like it to support other applications, however. Please see https://bugzilla.mozilla.org/show_bug.cgi?id=546740 for more information.

There are a couple of quite odd things going on with this log. Firstly the shutdown methods for the restartless add-ons never appear to be called, secondly in the first run something attempted to access the database after the add-ons manager had been told to shutdown. This attempt failed (probably because the database was still being asynchronously closed) which would have caused the add-ons manager to assume that the database was broken in some way and so delete it and create a new one. We attempt to recover which extensions were enabled in that case but the code that does that can't work that late in shutdown so you'd have ended up with an empty database. A subsequent launch attempted to rebuild the database but by then the data about which extensions will have been lost. So there seems to be something in your profile that is making strange things happen during shutdown, my guess would be an extension but off the top of my head I can't understand how it could do this. However it should be possible to at least protect the database in the event of something trying to access it after it has been shut down. That should at least should ensure we don't throw away the data when it is unnecessary to do so.

In reply to comment #37: Wouldn't it be possible to save the list of enabled extensions somewhere outside the database (extensions.ini perhaps?) and use that if the database is found on a later startup to be so corrupt that it cannot be used at all and must be rebuilt from scratch? I have a lot of extensions (currently 51 not including themes, language packs or disabled extensions) and that might perhaps be pushing the addons manager to its limits?

(In reply to Tony Mechelynck [:tonymec] from comment #38) > In reply to comment #37: > Wouldn't it be possible to save the list of enabled extensions somewhere > outside the database (extensions.ini perhaps?) and use that if the database > is found on a later startup to be so corrupt that it cannot be used at all > and must be rebuilt from scratch? We do do that already and it actually works pretty well but here something is calling the add-ons manager when it isn't initialized, something that is never going to work out well.

Mozilla/5.0 (X11; Linux x86_64; rv:12.0a1) Gecko/20111223 Firefox/12.0a1 SeaMonkey/2.9a1 ID:20111223003001 I have a hunch that after the landing of about:newaddon the addons would wake up disabled rather than enabled (cf. bug 713280 comment #11) which has at least the advantage of not waking up "known misbehaving" addons. Anyway I haven't seen this problem recently, close it WORKSFORME or WONTFIX if you want.

Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.