X
Tryk her for at gå til webstedets mobilversion.

Supportforum

cannot install [any] addon - for this instance though, it is UBlock Origin I require

Skrevet

Search for the addon on mozilla addons.

Locate UBlock Origin and click install. The popup is displayed to 'accept' permissions. Click accept and nothing happens. In the addons 'extensions' tab, the ublock entry row shows, but it never starts to download (and therefore never installs).

Tried to do it by saving the xpi to local and installing from there, but exactly same thing occurs.

Firefox 60.x ESR on Linux (slackware).

Is there anything else I might try please ?

Search for the addon on mozilla addons. Locate UBlock Origin and click install. The popup is displayed to 'accept' permissions. Click accept and nothing happens. In the addons 'extensions' tab, the ublock entry row shows, but it never starts to download (and therefore never installs). Tried to do it by saving the xpi to local and installing from there, but exactly same thing occurs. Firefox 60.x ESR on Linux (slackware). Is there anything else I might try please ?

Yderligere systemdetaljer

Installerede plugins

  • Shockwave Flash 31.0 r0

Program

  • User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0

Yderligere information

Luk
WestEnd
  • Top 25 Contributor
60 løsninger 5379 svar

Are those legacy addons? And disable Ublock before any addons install to verify it isn't blocking or preventing installs.

Are those legacy addons? And disable Ublock before any addons install to verify it isn't blocking or preventing installs.
FredMcD
  • Top 10 Contributor
4246 løsninger 59404 svar

It’s possible that there is a problem with the file(s) that store the extensions registry.

Type about:support in the address bar and press enter.

Under the page logo on the left side, you will see Application Basics. Under this find Profile Folder. To its right press the button Show Folder. This will open your file browser to the current Firefox profile. Now Close Firefox.

Linux: Under the page logo on the left side, you will see Application Basics. Under this find Profile Directory. To its right press the button Open Directory.

Delete all extensions* files and compatibility.ini in the Firefox profile folder to reset the extensions registry.

New files will be created when required.

After, restart Firefox.

See "Corrupt extension files":

It’s possible that there is a problem with the file(s) that store the extensions registry. Type '''about:support''' in the address bar and press enter. Under the page logo on the left side, you will see '''Application Basics. ''' Under this find '''Profile Folder. ''' To its right press the button '''Show Folder. ''' This will open your file browser to the current Firefox profile. Now '''Close Firefox. ''' '''Linux: ''' Under the page logo on the left side, you will see '''Application Basics.''' Under this find '''Profile Directory. ''' To its right press the button '''Open Directory. ''' Delete all '''extensions*''' files and '''compatibility.ini''' in the Firefox profile folder to reset the extensions registry. *https://support.mozilla.org/kb/Profiles New files will be created when required. After, restart Firefox. See "Corrupt extension files": *http://kb.mozillazine.org/Unable_to_install_themes_or_extensions *https://support.mozilla.org/kb/Unable+to+install+add-ons

Spørgsmålsstiller

Thank you both for replying.

@WestEnd, no not legacy and I am only installing Ublock Origin..no others installed; however, read the next bit.

@FredMcD, thank you for that full answer. Unfortunately this did not change the situation. The [ublock origin in this case] addon will not install, but...

I noticed a 'debug addons' option in 'about:addons'. There is a 'load temporary' button and a 'debug' checkbox etc.

On debugging the latest 'ublock origin' addon, it gave the following:

"DEPRECATION WARNING: Search service falling back to synchronous initialization. This is generally the consequence of an add-on using a deprecated search service API. You may find more details about this deprecation at: https://developer.mozilla.org/en-US/docs/XPCOM_Interface_Reference/nsIBrowserSearchService#async_warning jar:file:///usr/lib/firefox/omni.ja!/components/nsSearchService.js 2675 SRCH_SVC__ensureInitialized jar:file:///usr/lib/firefox/omni.ja!/components/nsSearchService.js 3839 SRCH_SVC_getEngineByName chrome://browser/content/browser.js 3883 addEngine chrome://browser/content/browser.js 3751 addSearch chrome://browser/content/browser.js 3712 receiveMessage..."

Which means little to me at the moment. I will go away and digest it.

Interestingly, temporary loading the addon works...but when quitting out of debugging, it seems to ditch the addon....I was hoping it would keep it :-) to act as a workaround for now. Ho hum.

Thank you both for replying. @WestEnd, no not legacy and I am only installing Ublock Origin..no others installed; however, read the next bit. @FredMcD, thank you for that full answer. Unfortunately this did not change the situation. The [ublock origin in this case] addon will not install, but... I noticed a 'debug addons' option in 'about:addons'. There is a 'load temporary' button and a 'debug' checkbox etc. On debugging the latest 'ublock origin' addon, it gave the following: "DEPRECATION WARNING: Search service falling back to synchronous initialization. This is generally the consequence of an add-on using a deprecated search service API. You may find more details about this deprecation at: https://developer.mozilla.org/en-US/docs/XPCOM_Interface_Reference/nsIBrowserSearchService#async_warning jar:file:///usr/lib/firefox/omni.ja!/components/nsSearchService.js 2675 SRCH_SVC__ensureInitialized jar:file:///usr/lib/firefox/omni.ja!/components/nsSearchService.js 3839 SRCH_SVC_getEngineByName chrome://browser/content/browser.js 3883 addEngine chrome://browser/content/browser.js 3751 addSearch chrome://browser/content/browser.js 3712 receiveMessage..." Which means little to me at the moment. I will go away and digest it. Interestingly, temporary loading the addon works...but when quitting out of debugging, it seems to ditch the addon....I was hoping it would keep it :-) to act as a workaround for now. Ho hum.
FredMcD
  • Top 10 Contributor
4246 løsninger 59404 svar

I called for more help.

I called for more help.