[Resolved] Firefox 46 big problems

[ulatekh]

I got this problem again, when Firefox upgraded to 48.0.2 -- the previously-installed Noscript 2.9.0.3 stopped working, and now I'm back to trying to install a working version of Noscript.

The console had an error message that might be relevant:

Code: Select all

1473191652088	addons.xpi	ERROR	Unable to read add-on manifest from C:\Users\[username]\AppData\Roaming\Mozilla\Firefox\Profiles\84yllrpt.default-1473188221398\extensions\staged\{73a6fe31-595d-460b-a920-fcc0f8843232}.xpi: [Exception... "Component returned failure code: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService]"  nsresult: "0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE)"  location: "JS frame :: resource://gre/modules/XPCOMUtils.jsm :: XPCU_serviceLambda :: line 230"  data: no] Stack trace: XPCU_serviceLambda()@resource://gre/modules/XPCOMUtils.jsm:230 < XPCU_defineLazyGetter/<.get()@resource://gre/modules/XPCOMUtils.jsm:198 < defineSyncGUID()@resource://gre/modules/addons/XPIProvider.jsm:1220 < loadManifestFromZipReader<()@resource://gre/modules/addons/XPIProvider.jsm:1428 < TaskImpl_run()@resource://gre/modules/Task.jsm:319 < Handler.prototype.process()@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:937 < this.PromiseWalker.walkerLoop()@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:816 < this.PromiseWalker.scheduleWalkerLoop/<()@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:750 < syncLoadManifestFromFile()@resource://gre/modules/addons/XPIProvider.jsm:1484 < this.XPIProvider.processPendingFileChanges()@resource://gre/modules/addons/XPIProvider.jsm:3319 < this.XPIProvider.checkForChanges()@resource://gre/modules/addons/XPIProvider.jsm:3615 < this.XPIProvider.startup()@resource://gre/modules/addons/XPIProvider.jsm:2685 < callProvider()@resource://gre/modules/AddonManager.jsm:227 < _startProvider()@resource://gre/modules/AddonManager.jsm:778 < AddonManagerInternal.startup()@resource://gre/modules/AddonManager.jsm:962 < this.AddonManagerPrivate.startup()@resource://gre/modules/AddonManager.jsm:2934 < amManager.prototype.observe()@resource://gre/components/addonManager.js:71
Log.jsm:753

There's no extensions/staged folder any more, nor is there anything in the extensions folder, so this error message is probably related to the attempt to install Noscript 2.9.0.14 .

[barbaz]

Yes it's related. Completely quit Firefox, then create manually the extensions/staged folder and copy in the NoScript xpi (the one with the same ID, or at least make sure it's named like that).

Does it help?

[ulatekh]

No, looks like the same problem.

Code: Select all

1473261135283	addons.xpi	ERROR	Unable to read add-on manifest from C:\Users\[username]\AppData\Roaming\Mozilla\Firefox\Profiles\84yllrpt.default-1473188221398\extensions\staged\{73a6fe31-595d-460b-a920-fcc0f8843232}.xpi: [Exception... "Component returned failure code: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService]"  nsresult: "0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE)"  location: "JS frame :: resource://gre/modules/XPCOMUtils.jsm :: XPCU_serviceLambda :: line 230"  data: no] Stack trace: XPCU_serviceLambda()@resource://gre/modules/XPCOMUtils.jsm:230 < XPCU_defineLazyGetter/<.get()@resource://gre/modules/XPCOMUtils.jsm:198 < defineSyncGUID()@resource://gre/modules/addons/XPIProvider.jsm:1220 < loadManifestFromZipReader<()@resource://gre/modules/addons/XPIProvider.jsm:1428 < TaskImpl_run()@resource://gre/modules/Task.jsm:319 < Handler.prototype.process()@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:937 < this.PromiseWalker.walkerLoop()@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:816 < this.PromiseWalker.scheduleWalkerLoop/<()@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:750 < syncLoadManifestFromFile()@resource://gre/modules/addons/XPIProvider.jsm:1484 < this.XPIProvider.processPendingFileChanges()@resource://gre/modules/addons/XPIProvider.jsm:3319 < this.XPIProvider.checkForChanges()@resource://gre/modules/addons/XPIProvider.jsm:3615 < this.XPIProvider.startup()@resource://gre/modules/addons/XPIProvider.jsm:2685 < callProvider()@resource://gre/modules/AddonManager.jsm:227 < _startProvider()@resource://gre/modules/AddonManager.jsm:778 < AddonManagerInternal.startup()@resource://gre/modules/AddonManager.jsm:962 < this.AddonManagerPrivate.startup()@resource://gre/modules/AddonManager.jsm:2934 < amManager.prototype.observe()@resource://gre/components/addonManager.js:71
Log.jsm:753

[barbaz]

Unable to read add-on manifest from C:\Users\[username]\AppData\Roaming\Mozilla\Firefox\Profiles\84yllrpt.default-1473188221398\extensions\staged\{73a6fe31-595d-460b-a920-fcc0f8843232}.xpi:

Missed that stuff earlier (the stuff I highlighted in red). That might indicate a bigger problem with your profile?

I'd suggest you create a new profile and salvage what you can.
http://kb.mozillazine.org/Transferring_ ... _-_Firefox

[ulatekh]

That is a newly-created profile.

[ulatekh]

In any case, a newly-created profile has the same problem:

Code: Select all

1473265345470	addons.xpi	ERROR	Unable to read add-on manifest from C:\Users\e833725\AppData\Roaming\Mozilla\Firefox\Profiles\wyrwye9g.Temp\extensions\staged\{73a6fe31-595d-460b-a920-fcc0f8843232}.xpi: [Exception... "Component returned failure code: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService]"  nsresult: "0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE)"  location: "JS frame :: resource://gre/modules/XPCOMUtils.jsm :: XPCU_serviceLambda :: line 230"  data: no] Stack trace: XPCU_serviceLambda()@resource://gre/modules/XPCOMUtils.jsm:230 < XPCU_defineLazyGetter/<.get()@resource://gre/modules/XPCOMUtils.jsm:198 < defineSyncGUID()@resource://gre/modules/addons/XPIProvider.jsm:1220 < loadManifestFromZipReader<()@resource://gre/modules/addons/XPIProvider.jsm:1428 < TaskImpl_run()@resource://gre/modules/Task.jsm:319 < Handler.prototype.process()@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:937 < this.PromiseWalker.walkerLoop()@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:816 < this.PromiseWalker.scheduleWalkerLoop/<()@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:750 < syncLoadManifestFromFile()@resource://gre/modules/addons/XPIProvider.jsm:1484 < this.XPIProvider.processPendingFileChanges()@resource://gre/modules/addons/XPIProvider.jsm:3319 < this.XPIProvider.checkForChanges()@resource://gre/modules/addons/XPIProvider.jsm:3615 < this.XPIProvider.startup()@resource://gre/modules/addons/XPIProvider.jsm:2685 < callProvider()@resource://gre/modules/AddonManager.jsm:227 < _startProvider()@resource://gre/modules/AddonManager.jsm:778 < AddonManagerInternal.startup()@resource://gre/modules/AddonManager.jsm:962 < this.AddonManagerPrivate.startup()@resource://gre/modules/AddonManager.jsm:2934 < amManager.prototype.observe()@resource://gre/components/addonManager.js:71
Log.jsm:753

[barbaz]

Then I would have to wonder if it might be a weird Firefox 48.0.2 issue..
Does, say, Firefox 45 ESR have the same problem?

[ulatekh]

Yes, same problem with FirefoxESR 45.3.0.

Code: Select all

1473348963598	addons.xpi	ERROR	Unable to read add-on manifest from C:\Users\[username]\AppData\Roaming\Mozilla\Firefox\Profiles\84yllrpt.default-1473188221398\extensions\staged\{73a6fe31-595d-460b-a920-fcc0f8843232}.xpi: [Exception... "Component returned failure code: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService]"  nsresult: "0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE)"  location: "JS frame :: resource://gre/modules/XPCOMUtils.jsm :: XPCU_serviceLambda :: line 230"  data: no] Stack trace: XPCU_serviceLambda()@resource://gre/modules/XPCOMUtils.jsm:230 < XPCU_defineLazyGetter/<.get()@resource://gre/modules/XPCOMUtils.jsm:198 < defineSyncGUID()@resource://gre/modules/addons/XPIProvider.jsm:1252 < loadManifestFromZipReader<()@resource://gre/modules/addons/XPIProvider.jsm:1431 < TaskImpl_run()@resource://gre/modules/Task.jsm:315 < Handler.prototype.process()@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:933 < this.PromiseWalker.walkerLoop()@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:812 < this.PromiseWalker.scheduleWalkerLoop/<()@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:746 < syncLoadManifestFromFile()@resource://gre/modules/addons/XPIProvider.jsm:1487 < this.XPIProvider.processPendingFileChanges()@resource://gre/modules/addons/XPIProvider.jsm:3277 < this.XPIProvider.checkForChanges()@resource://gre/modules/addons/XPIProvider.jsm:3565 < this.XPIProvider.startup()@resource://gre/modules/addons/XPIProvider.jsm:2655 < callProvider()@resource://gre/modules/AddonManager.jsm:227 < _startProvider()@resource://gre/modules/AddonManager.jsm:833 < AddonManagerInternal.startup()@resource://gre/modules/AddonManager.jsm:1016 < this.AddonManagerPrivate.startup()@resource://gre/modules/AddonManager.jsm:2782 < amManager.prototype.observe()@resource://gre/components/addonManager.js:58 Log.jsm:751:0

[barbaz]

What about the most recent Firefox version that you KNOW worked before?
https://ftp.mozilla.org/pub/firefox/releases/

[ulatekh]

Fixed now...like the original poster, I got Noscript to work by copying it from the profile of another computer (running Linux, even) that was already successfully running the plugin.

I got it to work in Firefox 45.3.0ESR, as well as 48.0.2.

The .xpi files are binary identical; the only difference I see is that the Unix-style permissions are 0700 for the non-installing copy, and 0644 for the installing copy. I'm not sure what implications Unix-style permissions have in MS Windows, but I don't see any other difference between the two copies of the plugin.

[barbaz]

Great, glad you're back working again and thanks for posting your findings!

The .xpi files are binary identical; the only difference I see is that the Unix-style permissions are 0700 for the non-installing copy, and 0644 for the installing copy. I'm not sure what implications Unix-style permissions have in MS Windows, but I don't see any other difference between the two copies of the plugin.

Well, Windows permissions and Linux permissions both exist but are totally different. I would think that how it translates would depend on how you copied the file.
IIRC you can see WIndows permissions on Windows by right-click the xpi > Properties?