[Unrelated; Firefox 79.0/x64] NoScript turning off by itself

Post a reply


In an effort to prevent automatic submissions, we require that you complete the following challenge.
Smilies
:D :) ;) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :!: :?: :idea: :arrow: :| :mrgreen: :geek: :ugeek:

BBCode is ON
[img] is ON
[flash] is OFF
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: [Unrelated; Firefox 79.0/x64] NoScript turning off by itself

Re: [Unrelated; Firefox 79.0/x64] NoScript turning off by itself

by doIneedaname » Tue Oct 13, 2020 1:33 pm

This behavior, whatever was causing stray file handles starting back in early Aug (11.0.35 release?), seems to be corrected with 11.1.11. When I manually ran the update from 11.1.11 to 11.1.13, the 11.1.11 xpi file in the trash directory was deleted by the update process. It did not remain behind, undeleteable due to open file handles like prior recent versions. Remains to be validated with a few clean autoupdates in the near future, but looks good so far. No clue what the root cause was; I did leave a bugzilla with FF; hopefully one day they'll improve XPIinstall.jsm so this isn't an issue anyway.

Re: [Unrelated; Firefox 79.0/x64] NoScript turning off by itself

by doIneedaname » Fri Oct 09, 2020 1:50 am

I logged a bug with bugzilla on the installation process handling.
https://bugzilla.mozilla.org/show_bug.cgi?id=1670149

FF is allowing the locked file to become a problem and blocking the update. A more robust handling of the situation by FF would prevent this ever having been a problem for users. Why the FF extension pid continues to hang on to the old xpi when FF is trying to delete it, I have no idea. That would be nice if that changed behavior, which started early August, was corrected. But at my level, I just want it to stop being a problem.

Re: [Unrelated; Firefox 79.0/x64] NoScript turning off by itself

by therube » Thu Oct 01, 2020 3:02 pm

(Some extensions [seemingly, they say, are the cause] that some handle to that extension, are locked - until a browser restart.
Bug 1624501 Cannot delete extension until Firefox is closed
There was another bug, similar, which I'm not finding? It was there that they commented that there was something specific in uBlock Origin's code that caused a similar issue [if I'm recalling correctly]. Pretty sure I filed the bug, but where?)

Re: [Unrelated; Firefox 79.0/x64] NoScript turning off by itself

by doIneedaname » Wed Sep 30, 2020 3:44 pm

All you need to do to get the update process to work once you notice it's failing is go to the trash directory we've noted and rename the file to anything else, such as ..._1.xpi, and then the update will work fine.

The problem is Firefox still has an open handle on the xpi file so Firefox is unable to delete it. Left hand right hand issue. But this started for all around early August it seems, and also for one who is still running 75. I ran 75 for a month when it was current with no issues. So I'm of the mind that the problem is with a change in NoScript. Though what that change was and why now Firefox cannot release the xpi file when it's being replaced, I have no idea.

Re: [Unrelated; Firefox 79.0/x64] NoScript turning off by itself

by yoyo » Sun Sep 27, 2020 11:56 pm

It got so bad for me that NoScript was silently dying every day. I tried switching "Allow automatic updates" to off.

I have been running with automatic updates turned off for over a week now and NoScript has not crashed.

I hope that helps someone else.

Re: [Unrelated; Firefox 79.0/x64] NoScript turning off by itself

by doIneedaname » Tue Sep 15, 2020 2:34 am

I just restarted Firefox and ran update addons and this time it updated to 11.0.43 correctly. Checking the directory structure, there was no trash directory this time. Firefox has been up and running since I updated to 80.0 some two weeks ago.

So no idea what happened with the installation of 11.0.42 that blew up. No idea why that blow up then barricaded being able to install 11.0.43. Firefox seemed to be blocking the removal of the 11.0.41 file which was now in the trash directory.

But beyond the update failure is also the question of why the blown update attempt was leaving the addon disabled instead of the prior revision reactivated. If it was as easy as click off/click on, why was the update process fail out path not doing that already.

And why has this behavior suddenly started in early August.

Re: [Unrelated; Firefox 79.0/x64] NoScript turning off by itself

by mrputter » Mon Sep 14, 2020 4:34 pm

Ok, so after I posted those last messages on Friday, I went in to my profile directory via Windows Explorer, and in the security settings, I manually added Everyone to the permissions settings, and granted them "Full control" (to the profile directory, and recursively to every item thereunder).

Have had no issues since then (3 days), after previously having NoScript crash, as I said, about twice a day.

I am hopeful that this has fixed it.

For what it's worth, before I did this, the previous permissions allowed Full Control to SYSTEM, to myself, and to Administrators. I don't know if this is correct, or if it's not, what the permissions are supposed to be. I also therefore don't know if I've potentially opened up a security hole by doing this? When I check running processes, both firefox.exe and plugin-container.exe are running as me, so as far as I can tell, they *should* have already had full control to the profile directory, but ¯\_(ツ)_/¯

Re: [Unrelated; Firefox 79.0/x64] NoScript turning off by itself

by doIneedaname » Sun Sep 13, 2020 3:55 am

In my roaming/mozilla/firefox/profiles/<profile>/extensions directory, I have a file {73a6fe31-595d-460b-a920-fcc0f8843232}.xpi, modified 9/7/2020, size 598,421 bytes. The manifest.json file inside mentions 11.0.42.

In my roaming/mozilla/firefox/profiles/<profile>extensions/trash directory, I have a file {73a6fe31-595d-460b-a920-fcc0f8843232}.xpi, modified 8/28/2020, size 594,369 bytes. The manifest.json file inside mentions 11.0.41.

If I attempt to manually delete the file in the trash directory, Explorer comes back saying it cannot because the file is open in Firefox. I don't know if this should be expected or not.

Re: [Unrelated; Firefox 79.0/x64] NoScript turning off by itself

by doIneedaname » Sun Sep 13, 2020 3:37 am

Yeah, that's definitely it. I tried "check for updates" in the FF Add-ons Manager. It said updating addon and then listed NoScript (disabled). I see the same message sequence in the extension Inspect console log. Unlike the two prior times, this time there is stuff in the Browser console log. It's like the other person's previously posted messages about failures. But it's hard to guess if these are the chicken or the egg. If it updated to 11.0.42 just fine on Sept 7, what is the problem updating to 11.0.43?

from the Browser console log this time:

Code: Select all

23:21:56.894 AbortError: Actor 'Conduits' destroyed before query 'RuntimeMessage' was resolved ConduitsParent.jsm:297
    _raceResponses resource://gre/modules/ConduitsParent.jsm:297

<uncertain if the above message is from before or after I clicked Check for Updates>

23:23:42.357 [NoScript] Cannot collect noscript activity data <unavailable> Could not establish connection. Receiving end does not exist. <empty string> 68 log.js:17:13
    error moz-extension://d5b05579-df7e-4daf-abba-d880262580d3/lib/log.js:17
    collectSeen moz-extension://d5b05579-df7e-4daf-abba-d880262580d3/bg/main.js:302
    createAndStore moz-extension://d5b05579-df7e-4daf-abba-d880262580d3/bg/LifeCycle.js:38
    createAndStore moz-extension://d5b05579-df7e-4daf-abba-d880262580d3/bg/LifeCycle.js:36
    onUpdateAvailable moz-extension://d5b05579-df7e-4daf-abba-d880262580d3/bg/LifeCycle.js:258
    <anonymous> moz-extension://d5b05579-df7e-4daf-abba-d880262580d3/bg/main.js:7

23:23:42.784 sendRemoveListener on closed conduit {73a6fe31-595d-460b-a920-fcc0f8843232}.274878111828 ConduitsChild.jsm:108
    _send resource://gre/modules/ConduitsChild.jsm:108
    _send self-hosted:1275
    removeListener resource://gre/modules/ExtensionChild.jsm:663
    removeListener resource://gre/modules/ExtensionChild.jsm:886
    onClicked chrome://browser/content/child/ext-menus.js:282
    removeListener resource://gre/modules/ExtensionCommon.jsm:2517
    revoke resource://gre/modules/ExtensionCommon.jsm:2539
    close resource://gre/modules/ExtensionCommon.jsm:2544
    unload resource://gre/modules/ExtensionCommon.jsm:909
    unload resource://gre/modules/ExtensionPageChild.jsm:261
    unload resource://gre/modules/ExtensionPageChild.jsm:298
    destroyExtensionContext resource://gre/modules/ExtensionPageChild.jsm:482
    observe resource://gre/modules/ExtensionPageChild.jsm:395

23:23:42.794 1599967422794	addons.xpi	ERROR	Failed to remove file C:\Users\<user>\AppData\Roaming\Mozilla\Firefox\Profiles\<profile>\extensions\trash\{73a6fe31-595d-460b-a920-fcc0f8843232}.xpi: [Exception... "Component returned failure code: 0x80520015 (NS_ERROR_FILE_ACCESS_DENIED) [nsIFile.remove]"  nsresult: "0x80520015 (NS_ERROR_FILE_ACCESS_DENIED)"  location: "JS frame :: resource://gre/modules/addons/XPIInstall.jsm :: recursiveRemove :: line 1009"  data: no] Stack trace: recursiveRemove()@resource://gre/modules/addons/XPIInstall.jsm:1009
recursiveRemove()@resource://gre/modules/addons/XPIInstall.jsm:1023
getTrashDir()@resource://gre/modules/addons/XPIInstall.jsm:3133
installAddon()@resource://gre/modules/addons/XPIInstall.jsm:3170
install()@resource://gre/modules/addons/XPIInstall.jsm:1754
update()@resource://gre/modules/addons/XPIProvider.jsm:2104 Log.jsm:723
    append resource://gre/modules/Log.jsm:723
    log resource://gre/modules/Log.jsm:379
    error resource://gre/modules/Log.jsm:387
    recursiveRemove resource://gre/modules/addons/XPIInstall.jsm:1013
    forEach self-hosted:216
    recursiveRemove resource://gre/modules/addons/XPIInstall.jsm:1023
    getTrashDir resource://gre/modules/addons/XPIInstall.jsm:3133
    installAddon resource://gre/modules/addons/XPIInstall.jsm:3170
    install resource://gre/modules/addons/XPIInstall.jsm:1754
    update resource://gre/modules/addons/XPIProvider.jsm:2104
    InterpretGeneratorResume self-hosted:1478
    AsyncFunctionNext self-hosted:684

23:23:42.794 1599967422794	addons.xpi	WARN	Failed to remove trash directory: [Exception... "Component returned failure code: 0x80520015 (NS_ERROR_FILE_ACCESS_DENIED) [nsIFile.remove]"  nsresult: "0x80520015 (NS_ERROR_FILE_ACCESS_DENIED)"  location: "JS frame :: resource://gre/modules/addons/XPIInstall.jsm :: recursiveRemove :: line 1009"  data: no] Stack trace: recursiveRemove()@resource://gre/modules/addons/XPIInstall.jsm:1009
recursiveRemove()@resource://gre/modules/addons/XPIInstall.jsm:1023
getTrashDir()@resource://gre/modules/addons/XPIInstall.jsm:3133
installAddon()@resource://gre/modules/addons/XPIInstall.jsm:3170
install()@resource://gre/modules/addons/XPIInstall.jsm:1754
update()@resource://gre/modules/addons/XPIProvider.jsm:2104

23:23:42.796 1599967422796	addons.xpi	ERROR	Failed to move file C:\Users\<user>\AppData\Roaming\Mozilla\Firefox\Profiles\<profile>\extensions\{73a6fe31-595d-460b-a920-fcc0f8843232}.xpi to C:\Users\<user>\AppData\Roaming\Mozilla\Firefox\Profiles\<profile>\extensions\trash: [Exception... "Component returned failure code: 0x80520015 (NS_ERROR_FILE_ACCESS_DENIED) [nsIFile.moveTo]"  nsresult: "0x80520015 (NS_ERROR_FILE_ACCESS_DENIED)"  location: "JS frame :: resource://gre/modules/addons/XPIInstall.jsm :: _installFile :: line 1111"  data: no] Stack trace: _installFile()@resource://gre/modules/addons/XPIInstall.jsm:1111
moveUnder()@resource://gre/modules/addons/XPIInstall.jsm:1140
moveOldAddon()@resource://gre/modules/addons/XPIInstall.jsm:3183
installAddon()@resource://gre/modules/addons/XPIInstall.jsm:3190
install()@resource://gre/modules/addons/XPIInstall.jsm:1754
update()@resource://gre/modules/addons/XPIProvider.jsm:2104 Log.jsm:723
    append resource://gre/modules/Log.jsm:723
    log resource://gre/modules/Log.jsm:379
    error resource://gre/modules/Log.jsm:387
    _installFile resource://gre/modules/addons/XPIInstall.jsm:1114
    moveUnder resource://gre/modules/addons/XPIInstall.jsm:1140
    moveOldAddon resource://gre/modules/addons/XPIInstall.jsm:3183
    installAddon resource://gre/modules/addons/XPIInstall.jsm:3190
    install resource://gre/modules/addons/XPIInstall.jsm:1754
    update resource://gre/modules/addons/XPIProvider.jsm:2104
    InterpretGeneratorResume self-hosted:1478
    AsyncFunctionNext self-hosted:684

23:23:42.797 1599967422797	addons.xpi	ERROR	Failed to remove file C:\Users\<user>\AppData\Roaming\Mozilla\Firefox\Profiles\<profile>\extensions\trash\{73a6fe31-595d-460b-a920-fcc0f8843232}.xpi: [Exception... "Component returned failure code: 0x80520015 (NS_ERROR_FILE_ACCESS_DENIED) [nsIFile.remove]"  nsresult: "0x80520015 (NS_ERROR_FILE_ACCESS_DENIED)"  location: "JS frame :: resource://gre/modules/addons/XPIInstall.jsm :: recursiveRemove :: line 1009"  data: no] Stack trace: recursiveRemove()@resource://gre/modules/addons/XPIInstall.jsm:1009
recursiveRemove()@resource://gre/modules/addons/XPIInstall.jsm:1023
installAddon()@resource://gre/modules/addons/XPIInstall.jsm:3235
install()@resource://gre/modules/addons/XPIInstall.jsm:1754
update()@resource://gre/modules/addons/XPIProvider.jsm:2104 Log.jsm:723
    append resource://gre/modules/Log.jsm:723
    log resource://gre/modules/Log.jsm:379
    error resource://gre/modules/Log.jsm:387
    recursiveRemove resource://gre/modules/addons/XPIInstall.jsm:1013
    forEach self-hosted:216
    recursiveRemove resource://gre/modules/addons/XPIInstall.jsm:1023
    installAddon resource://gre/modules/addons/XPIInstall.jsm:3235
    install resource://gre/modules/addons/XPIInstall.jsm:1754
    update resource://gre/modules/addons/XPIProvider.jsm:2104
    InterpretGeneratorResume self-hosted:1478
    AsyncFunctionNext self-hosted:684

23:23:42.797 1599967422797	addons.xpi	WARN	Failed to remove trash directory when installing {73a6fe31-595d-460b-a920-fcc0f8843232}: [Exception... "Component returned failure code: 0x80520015 (NS_ERROR_FILE_ACCESS_DENIED) [nsIFile.remove]"  nsresult: "0x80520015 (NS_ERROR_FILE_ACCESS_DENIED)"  location: "JS frame :: resource://gre/modules/addons/XPIInstall.jsm :: recursiveRemove :: line 1009"  data: no] Stack trace: recursiveRemove()@resource://gre/modules/addons/XPIInstall.jsm:1009
recursiveRemove()@resource://gre/modules/addons/XPIInstall.jsm:1023
installAddon()@resource://gre/modules/addons/XPIInstall.jsm:3235
install()@resource://gre/modules/addons/XPIInstall.jsm:1754
update()@resource://gre/modules/addons/XPIProvider.jsm:2104

23:23:42.797 1599967422797	addons.xpi	WARN	Failed to install C:\Users\Scott\AppData\Local\Temp\tmp-3z3.xpi from https://addons.cdn.mozilla.net/user-media/addons/722/noscript_security_suite-11.0.43-an+fx.xpi?filehash=sha256%3A79395f62e7df98813847e1ffb28ec33e8271dbf826646b022917d13126a29414 to C:\Users\Scott\AppData\Roaming\Mozilla\Firefox\Profiles\xtkp23cq.default\extensions\staged\{73a6fe31-595d-460b-a920-fcc0f8843232}.xpi: [Exception... "Component returned failure code: 0x80520015 (NS_ERROR_FILE_ACCESS_DENIED) [nsIFile.moveTo]"  nsresult: "0x80520015 (NS_ERROR_FILE_ACCESS_DENIED)"  location: "JS frame :: resource://gre/modules/addons/XPIInstall.jsm :: _installFile :: line 1111"  data: no] Stack trace: _installFile()@resource://gre/modules/addons/XPIInstall.jsm:1111
moveUnder()@resource://gre/modules/addons/XPIInstall.jsm:1140
moveOldAddon()@resource://gre/modules/addons/XPIInstall.jsm:3183
installAddon()@resource://gre/modules/addons/XPIInstall.jsm:3190
install()@resource://gre/modules/addons/XPIInstall.jsm:1754
update()@resource://gre/modules/addons/XPIProvider.jsm:2104

23:23:42.820 Webconsole context has changed

Re: [Unrelated; Firefox 79.0/x64] NoScript turning off by itself

by doIneedaname » Sun Sep 13, 2020 3:21 am

Another night, another phantom crash. This time I was not even on the computer. Last activity was around 16:45-16:48, then I left for a dinner event. Got home and opened a new window and noticed the missing S icon. Checked the inspect console log and same sequence as the day before. Oddly, it's also the same time.

It's clear to me now that the "navigated to about:blank" is the inspect window, showing the inspect console has lost connection to the extension. Because upon restart, we get the "Navigated to moz-extension://d5b05579-df7e-4daf-abba-d880262580d3/_generated_background_page.html" and then "Webconsole context has changed" messages.

Code: Select all

16:43:57.140 [NoScript] Blocking request from https://www.carscoops.com/2020/09/plasti-dipped-audi-a5-covered-in-paint-stripper-gets-new-lease-on-life-sort-of/ to https://www.facebook.com/v8.0/plugins/post.php?app_id=&chann…s%2Fposts%2F3641994429145541&locale=en_US&sdk=joey&width=525 by previous XSS prompt user choice log.js:9:13

16:45:48.322 tab is null 3 ExtensionParent.jsm:309
    getTopBrowsingContextId resource://gre/modules/ExtensionParent.jsm:309
    normalizeArgs resource://gre/modules/ExtensionParent.jsm:324
    InterpretGeneratorResume self-hosted:1478
    AsyncFunctionNext self-hosted:684

16:48:05.351 browser is undefined ExtensionParent.jsm:314
    getTopBrowsingContextId resource://gre/modules/ExtensionParent.jsm:314
    normalizeArgs resource://gre/modules/ExtensionParent.jsm:324
    AsyncFunctionNext self-hosted:684

- I leave for dinner -

19:54:56.579 [NoScript] Cannot collect noscript activity data Error: Could not establish connection. Receiving end does not exist. Could not establish connection. Receiving end does not exist. <empty string> log.js:17:13
    error moz-extension://d5b05579-df7e-4daf-abba-d880262580d3/lib/log.js:17
    collectSeen moz-extension://d5b05579-df7e-4daf-abba-d880262580d3/bg/main.js:302
    createAndStore moz-extension://d5b05579-df7e-4daf-abba-d880262580d3/bg/LifeCycle.js:38
    createAndStore moz-extension://d5b05579-df7e-4daf-abba-d880262580d3/bg/LifeCycle.js:36
    onUpdateAvailable moz-extension://d5b05579-df7e-4daf-abba-d880262580d3/bg/LifeCycle.js:258
    <anonymous> moz-extension://d5b05579-df7e-4daf-abba-d880262580d3/bg/main.js:7

<repeats many times as prior crash capture>

19:54:56.881 Navigated to about:blank

19:54:56.891 Webconsole context has changed

19:54:56.936 Error: Can't find profile directory. XULStore.jsm:66:15
    load resource://gre/modules/XULStore.jsm:66
    XULStore resource://gre/modules/XULStore.jsm:24

- I return from dinner and restart NoScript after seeing it's no longer functioning -

23:09:52.295 Navigated to moz-extension://d5b05579-df7e-4daf-abba-d880262580d3/_generated_background_page.html

23:09:52.306 Webconsole context has changed
The code stack implies something about update. Is there a way to know when NoScript is attempting auto-update? Could something out of that be crashing or hanging NoScript? My current version is 11.0.42, updated Sept 7. The issue seemed to restart on Sept 9 or so? Is this when 11.0.43 came out? Is it attempting to update and the update is crashing NoScript?

Re: [Unrelated; Firefox 79.0/x64] NoScript turning off by itself

by doIneedaname » Sat Sep 12, 2020 12:28 am

Just had it happen and had the about:debugging Noscript Inspect Console window open. Not sure if you prefer code or quote, but since I can't edit it, going quote.

Code: Select all

...
19:47:56.335 tab is null 4 ExtensionParent.jsm:309
    getTopBrowsingContextId resource://gre/modules/ExtensionParent.jsm:309
    normalizeArgs resource://gre/modules/ExtensionParent.jsm:324
    AsyncFunctionNext self-hosted:684

<FF history shows last visited time for any page as 19:49)

19:54:56.161 [NoScript] Cannot collect noscript activity data Error: Could not establish connection. Receiving end does not exist. Could not establish connection. Receiving end does not exist. <empty string> log.js:17:13
    error moz-extension://d5b05579-df7e-4daf-abba-d880262580d3/lib/log.js:17
    collectSeen moz-extension://d5b05579-df7e-4daf-abba-d880262580d3/bg/main.js:302
    createAndStore moz-extension://d5b05579-df7e-4daf-abba-d880262580d3/bg/LifeCycle.js:38
    createAndStore moz-extension://d5b05579-df7e-4daf-abba-d880262580d3/bg/LifeCycle.js:36
    onUpdateAvailable moz-extension://d5b05579-df7e-4daf-abba-d880262580d3/bg/LifeCycle.js:258
    <anonymous> moz-extension://d5b05579-df7e-4daf-abba-d880262580d3/bg/main.js:7

<repeats another ~66 times>

19:54:56.197 [NoScript] Cannot collect noscript activity data Error: Could not establish connection. Receiving end does not exist. Could not establish connection. Receiving end does not exist. <empty string> log.js:17:13
    error moz-extension://d5b05579-df7e-4daf-abba-d880262580d3/lib/log.js:17
    collectSeen moz-extension://d5b05579-df7e-4daf-abba-d880262580d3/bg/main.js:302
    createAndStore moz-extension://d5b05579-df7e-4daf-abba-d880262580d3/bg/LifeCycle.js:38
    createAndStore moz-extension://d5b05579-df7e-4daf-abba-d880262580d3/bg/LifeCycle.js:36
    onUpdateAvailable moz-extension://d5b05579-df7e-4daf-abba-d880262580d3/bg/LifeCycle.js:258
    <anonymous> moz-extension://d5b05579-df7e-4daf-abba-d880262580d3/bg/main.js:7

19:54:56.658 Webconsole context has changed

19:54:56.693 Navigated to about:blank

19:54:56.729 Error: Can't find profile directory. XULStore.jsm:66:15
    load resource://gre/modules/XULStore.jsm:66
    XULStore resource://gre/modules/XULStore.jsm:24

Re: [Unrelated; Firefox 79.0/x64] NoScript turning off by itself

by barbaz » Fri Sep 11, 2020 3:45 pm

Thanks mrputter! Based on those messages, I would suspect this is related in part to a failed auto-update of NoScript.

Why is "ACCESS_DENIED" to folders inside your profile folder?

Re: [Unrelated; Firefox 79.0/x64] NoScript turning off by itself

by barbaz » Fri Sep 11, 2020 3:43 pm

mrputter wrote:
Fri Sep 11, 2020 3:37 pm
Arrgh. This is triggering the forum's anti-spam filters. Please see a dump of the error messages here:
Let me see if I can post them:

Code: Select all

1599832830215	addons.xpi	ERROR	Failed to move file C:\Users\seann\AppData\Roaming\Mozilla\Firefox\Profiles\nx7qndcq.default-release\extensions\{73a6fe31-595d-460b-a920-fcc0f8843232}.xpi to C:\Users\XXXXXXXX\AppData\Roaming\Mozilla\Firefox\Profiles\XXXXXXXX\extensions\trash: [Exception... "Component returned failure code: 0x80520015 (NS_ERROR_FILE_ACCESS_DENIED) [nsIFile.moveTo]"  nsresult: "0x80520015 (NS_ERROR_FILE_ACCESS_DENIED)"  location: "JS frame :: resource://gre/modules/addons/XPIInstall.jsm :: _installFile :: line 1092"  data: no] Stack trace: _installFile()@resource://gre/modules/addons/XPIInstall.jsm:1092
moveUnder()@resource://gre/modules/addons/XPIInstall.jsm:1121
moveOldAddon()@resource://gre/modules/addons/XPIInstall.jsm:3152
installAddon()@resource://gre/modules/addons/XPIInstall.jsm:3159
install()@resource://gre/modules/addons/XPIInstall.jsm:1765
update()@resource://gre/modules/addons/XPIProvider.jsm:2074 Log.jsm:723
    append resource://gre/modules/Log.jsm:723
    log resource://gre/modules/Log.jsm:379
    error resource://gre/modules/Log.jsm:387
    _installFile resource://gre/modules/addons/XPIInstall.jsm:1095
    moveUnder resource://gre/modules/addons/XPIInstall.jsm:1121
    moveOldAddon resource://gre/modules/addons/XPIInstall.jsm:3152
    installAddon resource://gre/modules/addons/XPIInstall.jsm:3159
    install resource://gre/modules/addons/XPIInstall.jsm:1765
    update resource://gre/modules/addons/XPIProvider.jsm:2074
    InterpretGeneratorResume self-hosted:1156
    AsyncFunctionNext self-hosted:695


1599832830217	addons.xpi	WARN	Failed to remove trash directory when installing {73a6fe31-595d-460b-a920-fcc0f8843232}: [Exception... "Component returned failure code: 0x80520015 (NS_ERROR_FILE_ACCESS_DENIED) [nsIFile.remove]"  nsresult: "0x80520015 (NS_ERROR_FILE_ACCESS_DENIED)"  location: "JS frame :: resource://gre/modules/addons/XPIInstall.jsm :: recursiveRemove :: line 990"  data: no] Stack trace: recursiveRemove()@resource://gre/modules/addons/XPIInstall.jsm:990
recursiveRemove()@resource://gre/modules/addons/XPIInstall.jsm:1004
installAddon()@resource://gre/modules/addons/XPIInstall.jsm:3204
install()@resource://gre/modules/addons/XPIInstall.jsm:1765
update()@resource://gre/modules/addons/XPIProvider.jsm:2074


1599832830217	addons.xpi	WARN	Failed to install C:\Users\XXXXXXXX\AppData\Local\Temp\tmp-s0i.xpi from https://addons.cdn.mozilla.net/user-media/addons/722/noscript_security_suite-11.0.43-an+fx.xpi?filehash=sha256%3A79395f62e7df98813847e1ffb28ec33e8271dbf826646b022917d13126a29414 to C:\Users\XXXXXXXX\AppData\Roaming\Mozilla\Firefox\Profiles\XXXXXXXX\extensions\staged\{73a6fe31-595d-460b-a920-fcc0f8843232}.xpi: [Exception... "Component returned failure code: 0x80520015 (NS_ERROR_FILE_ACCESS_DENIED) [nsIFile.moveTo]"  nsresult: "0x80520015 (NS_ERROR_FILE_ACCESS_DENIED)"  location: "JS frame :: resource://gre/modules/addons/XPIInstall.jsm :: _installFile :: line 1092"  data: no] Stack trace: _installFile()@resource://gre/modules/addons/XPIInstall.jsm:1092
moveUnder()@resource://gre/modules/addons/XPIInstall.jsm:1121
moveOldAddon()@resource://gre/modules/addons/XPIInstall.jsm:3152
installAddon()@resource://gre/modules/addons/XPIInstall.jsm:3159
install()@resource://gre/modules/addons/XPIInstall.jsm:1765
update()@resource://gre/modules/addons/XPIProvider.jsm:2074

Re: [Unrelated; Firefox 79.0/x64] NoScript turning off by itself

by mrputter » Fri Sep 11, 2020 3:37 pm

Ok, so here's another data point; hopefully it may be helpful!

I haven't had the chance to update my browser yet (still on 75), but with any luck this may be relevant anyway.

Had to leave my computer for a few hours this morning; when I left, I verified that NoScript was still running, and left the Browser Console open, as per the request by barbaz in his last post (I also cleared away any previous messages, so the window was blank).

Came back, opened a new tab, and noticed that NoScript had died, yet again. Went to the Browser Console, and saw the following messages. I live in UTC-7 (with Daylight Saving Time in effect) so per the timestamps these occurred at exactly 8:00 AM (when I was not at the computer).

By peeking at the .xpi file being referenced, I've verified that these messages do pertain to NoScript. (There were a couple of other very similar messages relating to AdBlock -- the only other add-on that I'm running -- I haven't included them here.) So it looks to me like there's some kind of permission error happening, and NoScript is dying? AdBlock, which again is receiving similar messages, is still going.

Anyway, here we go (I've anonymized a few path names here, but I assume that's not an issue. I've also saved a copy of the xpi and can provide if it's in any way helpful)...

Arrgh. This is triggering the forum's anti-spam filters. Please see a dump of the error messages here:
http://trichotomy.ca/junk/20200911_fire ... ssages.txt

Re: [Unrelated; Firefox 79.0/x64] NoScript turning off by itself

by barbaz » Fri Sep 11, 2020 12:28 am

doIneedaname wrote:
Fri Sep 11, 2020 12:21 am
The inspect - console log doesn't seem to be flooding with those prior messages that were making leaving it open impossible. I'll leave it there and see if it can provide any enlightenment.
Please instead leave open the Browser Console (Ctrl-Shift-J) and let us know any related messages there around the time this issue recurs.

Also, in case it's relevant, what other extensions do those of you experiencing this issue have?

Top