about:addons broken
After the latest update of Firefox, my about:addons "Extensions" tab is blank. The page throws this error into the console:
1446769817084 addons.manager WARN Exception calling callback: TypeError: aLocales[Symbol.iterator] is not a function (resource://gre/modules/Locale.jsm:57:1) JS Stack trace: findClosestLocale@Locale.jsm:57:1 < AddonInternal.prototype.selectedLocale@XPIProvider.jsm:6613:18 < AddonWrapper_singleLocaleGetter@XPIProvider.jsm:7058:9 < createItem@extensions.js:1502:3 < GM_createItem@addons4-overlay.js:30:14 < gListView_show/<@extensions.js:2697:23 < getAddonsAndInstalls_getAddonsByTypes@extensions.js:1685:7 < safeCall@AddonManager.jsm:173:5 < getAddonsByTypes_noMoreObjects@AddonManager.jsm:2412:9 < AOC_callNext@AddonManager.jsm:369:7 < getAddonsByTypes_concatAddons@AddonManager.jsm:2407:11 < SocialAddonProvider.getAddonsByTypes@SocialService.jsm:1027:7 < callProviderAsync@AddonManager.jsm:248:12 < getAddonsByTypes_nextObject@AddonManager.jsm:2402:1 < AOC_callNext@AddonManager.jsm:375:7 < getAddonsByTypes_concatAddons@AddonManager.jsm:2407:11 < AddonProvider_getAddonsByTypes@addons4.js:46:7 < callProviderAsync@AddonManager.jsm:248:12 < getAddonsByTypes_nextObject@AddonManager.jsm:2402:1 < AOC_callNext@AddonManager.jsm:375:7 < getAddonsByTypes_concatAddons@AddonManager.jsm:2407:11 < this.Experiments.PreviousExperimentProvider.prototype<.getAddonsByTypes@Experiments.jsm:2263:7 < callProviderAsync@AddonManager.jsm:248:12 < getAddonsByTypes_nextObject@AddonManager.jsm:2402:1 < AOC_callNext@AddonManager.jsm:375:7 < getAddonsByTypes_concatAddons@AddonManager.jsm:2407:11 < PL_getAddonsByTypes@PluginProvider.jsm:139:7 < callProviderAsync@AddonManager.jsm:248:12 < getAddonsByTypes_nextObject@AddonManager.jsm:2402:1 < AOC_callNext@AddonManager.jsm:375:7 < getAddonsByTypes_concatAddons@AddonManager.jsm:2407:11 < GMPProvider.getAddonsByTypes@GMPProvider.jsm:658:7 < callProviderAsync@AddonManager.jsm:248:12 < getAddonsByTypes_nextObject@AddonManager.jsm:2402:1 < AOC_callNext@AddonManager.jsm:375:7 < getAddonsByTypes_concatAddons@AddonManager.jsm:2407:11 < LightweightThemeManager_getAddonsByTypes@LightweightThemeManager.jsm:446:7 < callProviderAsync@AddonManager.jsm:248:12 < getAddonsByTypes_nextObject@AddonManager.jsm:2402:1 < AOC_callNext@AddonManager.jsm:375:7 < getAddonsByTypes_concatAddons@AddonManager.jsm:2407:11 < getAddonsByTypes_getVisibleAddons@XPIProvider.jsm:4148:7 < makeSafe/<@XPIProviderUtils.js:145:17 < asyncMap_gotValue@XPIProviderUtils.js:180:7 < asyncMap_callback@XPIProviderUtils.js:187:9 < completeAddon@XPIProviderUtils.js:134:5 < getAddon@AddonRepository.jsm:580:7 < this.AddonRepository.getCachedAddonByID<@AddonRepository.jsm:592:5
Ghostery is also throwing errors:
19:30:46.419 TypeError: SDK.tabsLib.getTabForWindow is not a function1 utils.js:172:10
but since the Extension tab is broken I can't easily disable it and see if that is the problem.
Chosen solution
It is possible that there is a problem with the file(s) that store the extensions registry.
Delete the extensions.* files (e.g. extensions.json, extensions.sqlite, extensions.ini) and compatibility.ini in the Firefox profile folder to reset the extensions registry.
New files will be created when required.
See "Corrupt extension files":
- http://kb.mozillazine.org/Unable_to_install_themes_or_extensions
- https://support.mozilla.org/kb/Unable+to+install+add-ons
If you see disabled or not compatible extensions in "Firefox menu button/Tools > Add-ons > Extensions" then click the Tools button at the left end of the Search bar to check if there is a compatibility update available.
If this hasn't helped then also delete the addons.json file.
Read this answer in context 👍 0All Replies (6)
The same error occurs when starting in Safe Mode.
I had to Refresh my Firefox but then I was able to confirm that deleting Ghostery fixed the problem.
Ignore the previous reply. Removed Ghostery but the problem returned on the next restart of the browser. Same error is present in the console when I bring up about:addons.
Sometimes Firefox is broken in weird, random ways after an update because of mixed files in the Firefox program folder. If there is no rational explanation for the problem, we recommend:
Clean Reinstall
We use this name, but it's not about removing your settings, it's about making sure the program files are clean (no inconsistent, corrupted, or alien code files). As described below, this process does not disturb your existing settings. Do NOT uninstall Firefox, that's not needed.
(A) Download a fresh installer for Firefox 42.0 from https://www.mozilla.org/firefox/all/ to a convenient location. (Scroll down to your preferred language.)
(B) Exit out of Firefox (if applicable).
(C) Rename just the current program folder, either:
(64-bit Windows folder names)
C:\Program Files (x86)\Mozilla Firefox
to
C:\Program Files (x86)\OldFirefox
(32-bit Windows folder names)
C:\Program Files\Mozilla Firefox
to
C:\Program Files\OldFirefox
(D) Run the installer you downloaded in (A). It should automatically connect to your existing settings.
Does Firefox work more normally?
Note: Some plugins may exist only in that OldFirefox folder. If something essential is missing, look in these folders:
- \OldFirefox\Plugins
- \OldFirefox\browser\plugins
Otherwise, there's no reason to keep the old folder except research/curiosity.
Chosen Solution
It is possible that there is a problem with the file(s) that store the extensions registry.
Delete the extensions.* files (e.g. extensions.json, extensions.sqlite, extensions.ini) and compatibility.ini in the Firefox profile folder to reset the extensions registry.
New files will be created when required.
See "Corrupt extension files":
- http://kb.mozillazine.org/Unable_to_install_themes_or_extensions
- https://support.mozilla.org/kb/Unable+to+install+add-ons
If you see disabled or not compatible extensions in "Firefox menu button/Tools > Add-ons > Extensions" then click the Tools button at the left end of the Search bar to check if there is a compatibility update available.
If this hasn't helped then also delete the addons.json file.
This seemed to fix it for me. Thanks.