搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Firefox 48.0 update broke noscript, https everywhere and ghostery.

  • 6 回覆
  • 2 有這個問題
  • 1 次檢視
  • 最近回覆由 Paul47

more options

I just went through my latest ubuntu "software updater" procedure which pulled in the new firefox (48.0). Now, noscript could not be started, and I got a message saying I should re-install it. When I attempt to do so, it fails trying to access the file noscript.net.

Unlike noscript, ghostery and https everywhere still shows up in firefox, however when I get in the addons manager and ask it to check for updates, all three of them failed; the error message for all three was "There was an error installing ______."

I just went through my latest ubuntu "software updater" procedure which pulled in the new firefox (48.0). Now, noscript could not be started, and I got a message saying I should re-install it. When I attempt to do so, it fails trying to access the file noscript.net. Unlike noscript, ghostery and https everywhere still shows up in firefox, however when I get in the addons manager and ask it to check for updates, all three of them failed; the error message for all three was "There was an error installing ______."

被選擇的解決方法

I changed the ownership of these files and now the updates happen.

從原來的回覆中察看解決方案 👍 0

所有回覆 (6)

more options

The main issue people may encounter with Firefox 48.0 is with using older Extensions that have not been signed.

Make sure you have the latest versions of the extensions. https://addons.mozilla.org/firefox/addon/noscript/versions/ https://addons.mozilla.org/firefox/addon/ghostery/versions/ https://addons.mozilla.org/firefox/addon/https-everywhere/versions/

The support forum for NoScript at https://forums.informaction.com shows no indication that Firefox 48.0 including the official builds from Mozilla.org/firefox/all/ is breaking NoScript.

more options

James said

... The support forum for NoScript at https://forums.informaction.com shows no indication that Firefox 48.0 including the official builds from Mozilla.org/firefox/all/ is breaking NoScript.

However on Fx48 Noscript may block any rss feeds you have unless you allow the feed's parent site in NoScript.

more options

I have my extensions on automatic update so this shouldn't be an issue. I assume noscript was itself in the noscript whitelist since I have gotten their upgrades in the past.

I cannot even uninstall noscript. It simply sits there when I try.

I did notice an error message when invoking firefox from the command line. Perhaps someone can interpret it for me:

paul@len780:~$ firefox 1470720398616 addons.xpi WARN Can't iterate directory /home/paul/.mozilla/firefox/mjgcmg3t.default/extensions/staged: [Exception... "Component returned failure code: 0x80520015 (NS_ERROR_FILE_ACCESS_DENIED) [nsIFile.directoryEntries]" nsresult: "0x80520015 (NS_ERROR_FILE_ACCESS_DENIED)" location: "JS frame :: resource://gre/modules/addons/XPIProvider.jsm :: getDirectoryEntries :: line 1963" data: no] Stack trace: getDirectoryEntries()@resource://gre/modules/addons/XPIProvider.jsm:1963 < this.XPIProvider.processPendingFileChanges()@resource://gre/modules/addons/XPIProvider.jsm:3248 < this.XPIProvider.checkForChanges()@resource://gre/modules/addons/XPIProvider.jsm:3627 < this.XPIProvider.startup()@resource://gre/modules/addons/XPIProvider.jsm:2697 < 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 Component returned failure code: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService]Component returned failure code: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService]

more options

OK I went to check and noscript is at 2.9.0.4 which is not the most recent, 2.9.0.14. I don't know why these stopped updating; again it is set for them to automatically update. Anyway now I am stuck and I don't know how to proceed.

由 Paul47 於 修改

more options

For what it's worth, when I try checking for updates, these errors come out at the command line:

1470723260389 addons.xpi WARN Failed to install /tmp/tmp-2yg.xpi from https://addons.cdn.mozilla.net/user-media/addons/722/noscript_security_suite-2.9.0.14-fx+fn+sm.xpi?filehash=sha256%3A39bc71be20c318578239ea791c0341dbfcd13b33559af080cea386eeec08b337: Unix error 13 during operation stat on file /home/paul/.mozilla/firefox/mjgcmg3t.default/extensions/staged/{73a6fe31-595d-460b-a920-fcc0f8843232} (Permission denied) ((unknown module)) No traceback available 1470723263790 addons.xpi WARN Failed to install /tmp/tmp-e3d.xpi from https://addons.cdn.mozilla.net/user-media/addons/9609/ghostery-6.3.1-fx+sm+an.xpi?filehash=sha256%3A97d800d9c4b2f4e13f823b9586a6018184eb21f58ed18e1f891fb201b7724df6: Unix error 13 during operation stat on file /home/paul/.mozilla/firefox/mjgcmg3t.default/extensions/staged/firefox@ghostery.com (Permission denied) ((unknown module)) No traceback available 1470723264509 addons.xpi WARN Failed to install /tmp/tmp-luh.xpi from https://addons.cdn.mozilla.net/user-media/addons/229918/https_everywhere-5.2.1-an+fx+sm+tb.xpi?filehash=sha256%3A5a9c9cd9ca93752d9bfbbf93227c572c5756807b441742b2749b064a4b486068: Unix error 13 during operation stat on file /home/paul/.mozilla/firefox/mjgcmg3t.default/extensions/staged/https-everywhere@eff.org (Permission denied) ((unknown module)) No traceback available

When I look at the "staged" directory it lists as follows: drwx------ 2 root root 4096 Mar 18 20:41 staged

Inside the "staged" directory it has this: drwx------ 2 root root 4096 Mar 18 20:41 . drwxrwxr-x 5 paul paul 4096 Mar 18 20:41 .. -rw-r--r-- 1 root root 4803 Mar 18 20:41 {73a6fe31-595d-460b-a920-fcc0f8843232}.json -rw------- 1 root root 562656 Mar 18 20:41 {73a6fe31-595d-460b-a920-fcc0f8843232}.xpi

It's odd these are owned by root:root, is that normal? Seems like it should be paul:paul, like the rest. I wonder how they got changed.

more options

選擇的解決方法

I changed the ownership of these files and now the updates happen.