Mozilla/5.0 (X11; Linux x86_64; rv:12.0a1) Gecko/20111223 Firefox/12.0a1 SeaMonkey/2.9a1 ID:20111223003001 The following happen, starting at first startup with ACR 1.0.2 enabled: - All add-ons work: buttons are on toolbars and are functional, menuitems are present and functional, ChatZilla window opens, my third-party theme and Persona both display their distinctive look & feel, langpacks are listed under "User Interface Language" in the "Appearance" preferences, etc. etc. etc. - Flagfox doesn't find its libraries, however (there is a bug for that but I don't find its number back ATM) - user-disabled extensions seem to be still disabled - about:support doesn't list any "Extensions" - about:addons is completely empty except for plugins: - "Extensions" and "Appearance" tabs only say "You don't have any add-ons of this type installed" - "Languages" tab is not present - "Recent updates" tab shows only a plugin, not even the ACR upgraded an hour or two ago - "Check for updates" returns "No updates found" in a fraction of a second, while before installing ACR 1.0.2 it showed Provider for Google Calendar 0.9 (bug 711715) While reporting this bug a first time, I had a full system freeze and was forced to reboot (no change). Now let's see what happens if I restart SeaMonkey "normally".

No change. Now let's "Restart with Add-ons Disabled" and see if I can disable the ACR. FYI, here's what Flagfox says: Sorry, the Flagfox extension has encountered a problem. The following error output and a Flagfox preferences dump has been sent to Tools -> Error Console. ------------------------------------------------------------ FLAGFOX VERSION: 4.1.x (missing IPDB!) ERROR MESSAGE: Fatal Flagfox startup error! EXCEPTION THROWN: TypeError: addon is null STACK TRACE: (null)@resource://flagfox/flagfox.jsm:70 safeCall((function (addon) {try {FlagfoxVersion = addon.version;var ip4db = addon.getResourceURI(IPv4DBfilename).QueryInterface(Components.interfaces.nsIFileURL).file;var ip6db = addon.getResourceURI(IPv6DBfilename).QueryInterface(Components.interfaces.nsIFileURL).file;ipdb.init(ip4db, ip6db);checkIPDBage();ready = true;} catch (e) {handleStartupError(e);}}),null)@resource://gre/modules/AddonManager.jsm:71 ([object Object])@resource://gre/modules/AddonManager.jsm:1256 AOC_callNext()@resource://gre/modules/AddonManager.jsm:168 (null)@resource://gre/modules/AddonManager.jsm:1251 PL_getAddon("{1018e4d6-728f-4b20-ad56-37578a4de76b}",(function (aAddon) {"use strict";if (aAddon) {safeCall(aCallback, aAddon);} else {aCaller.callNext();}}))@resource://gre/modules/PluginProvider.jsm:81 callProvider([object Object],"getAddonByID",null,"{1018e4d6-728f-4b20-ad56-37578a4de76b}",(function (aAddon) {"use strict";if (aAddon) {safeCall(aCallback, aAddon);} else {aCaller.callNext();}}))@resource://gre/modules/AddonManager.jsm:99 ([object Object],[object Object])@resource://gre/modules/AddonManager.jsm:1247 AOC_callNext()@resource://gre/modules/AddonManager.jsm:174 (null)@resource://gre/modules/AddonManager.jsm:1251 (null)@resource://gre/modules/XPIProvider.jsm:3125 ([object Array])@resource://gre/modules/XPIProvider.jsm:5081 (0)@resource://gre/modules/XPIProvider.jsm:4038 BROWSER: Mozilla SeaMonkey 2.9a1 (Gecko 12.0a1 / 20111223003001) OS: Linux x86_64 (Linux x86_64-gcc3 gtk2) LOCALE: en-us content / en-us UI / en-us OS ------------------------------------------------------------ Select and copy the error report above. In order to fix this problem for you and others, please read and follow the troubleshooting and bug reporting instructions on the Flagfox support forums. Please post an abundance of information with any error reports, namely what you were doing at the time that may have triggered this. (English please)

In Safe Mode, my extensions and heavyweight themes still aren't listed, but my Personas are (they weren't before). Now I'm going to attach extensions.* from my profile.

I'm going to restart in "unsafe" mode but I don't like the idea of not being able to manage extensions (even if they work). Please advise.

The particular Add-on Manager breakage that ticks Flagfox off (comment 1) is bug 674344. I think I remember some other addon having a similar problem, as it can affect any that needs to make a AddonManager.getAddonByID() call to get any of its files.

Next experiment: remove or rename extensions.sqlite (I think the extensions.ini attached to this bug will -if necessary- tell me which extensions I must not manually disable in case they all get enabled).

I attempted to reproduce in new profiles by installing ACR & Flagfox but couldn't hit any problems. Tried Linux and a WinXP VM. Builds tested: Mozilla/5.0 (X11; Linux i686; rv:12.0a1) Gecko/20111223 Firefox/12.0a1 Mozilla/5.0 (Windows NT 5.1; rv:12.0a1) Gecko/20111223 Firefox/12.0a1 Mozilla/5.0 (Windows NT 5.1; rv:12.0a1) Gecko/20111222 Firefox/12.0a1 SeaMonkey/2.9a1

(In reply to Tony Mechelynck [:tonymec] from comment #9) > Next experiment: remove or rename extensions.sqlite (I think the > extensions.ini attached to this bug will -if necessary- tell me which > extensions I must not manually disable in case they all get enabled). All extensions wake up disabled but listed and I get an about:newaddon tab for each of them, telling me that "some other program" is trying to install them. The add-ons manager is easier to use. As I enable add-ons there, the about:newaddon tabs close one by one. I have not re-enabled the ACR. (In reply to Dave Garrett from comment #10) > I attempted to reproduce in new profiles by installing ACR & Flagfox but > couldn't hit any problems. Tried Linux and a WinXP VM. Builds tested: > Mozilla/5.0 (X11; Linux i686; rv:12.0a1) Gecko/20111223 Firefox/12.0a1 > Mozilla/5.0 (Windows NT 5.1; rv:12.0a1) Gecko/20111223 Firefox/12.0a1 > Mozilla/5.0 (Windows NT 5.1; rv:12.0a1) Gecko/20111222 Firefox/12.0a1 > SeaMonkey/2.9a1 Maybe the sheer number of my add-ons (see extensions.ini, attachment 584105 [details]) contributes to the problem? I have good hope that my workaround (see comment #9 and reply above) was the right one though.

Yep, everything is back. I'm attaching the rebuilt extensions.sqlite for comparison, and I notice an extensions.sqlite-journal which I'll attach too. (I may have enabled or disabled a couple of extensions which weren't so before, but not many of them.)

oops, wrong CC

If this problem is due to the sheer number of my add-ons (enabling/disabling the ACR increased/decreased that number by one, maybe just enough to carry it over some threshold?), then it belongs in Toolkit::Add-ons Manager rather than in AMO::ACR — Dave, Blair, what do you think?

Sounds like this might be from bug 572322 again? :(

(In reply to Dave Townsend (:Mossop) from comment #16) > Sounds like this might be from bug 572322 again? :( This would only be if ACR was installed fresh, but I believe Tony was upgrading from 1.0.1 -> 1.0.2?

(In reply to Brian King (Briks) [:kinger] from comment #17) > (In reply to Dave Townsend (:Mossop) from comment #16) > > Sounds like this might be from bug 572322 again? :( > > This would only be if ACR was installed fresh, but I believe Tony was > upgrading from 1.0.1 -> 1.0.2? I had disabled 1.0.1 because of bug 709225. When 1.0.2 became available, I installed it (still disabled). I think the upgrade was proposed by "Check for updates" in the addons manager. I didn't enable it immediately but on the next restart. N.B. I use trunk nightlies on SeaMonkey, and what I call "restart" includes, about once per 24h, a manual nightly update by "rm -Rvf /usr/local/seamonkey" followed by (currently) "tar -jxvC /usr/local -f seamonkey-2.9a1.en-US.linux-x86_64.tar.bz2". IIRC I updated 1.0.1 -> 1.0.2 (disabled) with one nightly then after starting the next nightly, decided I'd check out that new ACR version, enabled it, and restarted by either (don't remember which) the addons manager "Restart Now" links or the Restartless Restart extension. Depending on what you mean by "installed fresh", I suppose this might or might not qualify.

I'm not really sure what to make of this bug, but ... (In reply to Tony Mechelynck [:tonymec] from comment #18) > I had disabled 1.0.1 because of bug 709225. When 1.0.2 became available, I > installed it (still disabled). I think the upgrade was proposed by "Check > for updates" in the addons manager. I didn't enable it immediately but on > the next restart. This will be my test scenario to try and reproduce in Seamonkey. Note that SM was never officially supported and never received any QA. Does SM have compatible by default?

Mozilla/5.0 (X11; Linux x86_64; rv:12.0a1) Gecko/20120110 Firefox/12.0a1 SeaMonkey/2.9a1 ID:20120110003001 In current trunk, extensions.strictCompatibility defaults to false. I never felt the need to toggle it. AFAIK, its default was false in SeaMonkey trunk ever since it was defined.

Thanks for filing this. Due to resource constraints we are closing bugs which we won't realistically be able to fix. If you have a patch that applies to this bug please reopen. For more info see http://micropipes.com/blog/2014/09/24/the-great-add-on-bug-triage/