Ovo će web mjesto raditi na ograničen način, dok obavljamo održavanje stranice. Ako neki članak ne riješi tvoj problem i ako želiš postaviti pitanje, naša zajednica za podršku spremna je pomoći na Twitteru @FirefoxSupport i na Redditu /r/firefox.

Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

How to stop Firefox from checking for add-on compatibility every time it opens?

  • 2 odgovora
  • 4 imaju ovaj problem
  • 20 prikaza
  • Posljednji odgovor od Dummy88

more options

How to stop Firefox from checking for add-on compatibility every time it opens?

How to stop Firefox from checking for add-on compatibility every time it opens?

Izabrano rješenje

That can be a problem with the compatibility.ini file in the Firefox profile folder. Try to rename (or delete) the compatibility.ini file in the Firefox profile folder to see if that helps.

You can use this button to go to the currently used Firefox profile folder:

You can also check for problems with preferences.

Delete possible user.js and numbered prefs-##.js files and rename (or delete) the prefs.js file to reset all prefs to the default value including prefs set via user.js and prefs that are no longer supported in the current Firefox release.

Pročitaj ovaj odgovor u kontekstu 👍 1

Svi odgovori (2)

more options

Odabrano rješenje

That can be a problem with the compatibility.ini file in the Firefox profile folder. Try to rename (or delete) the compatibility.ini file in the Firefox profile folder to see if that helps.

You can use this button to go to the currently used Firefox profile folder:

You can also check for problems with preferences.

Delete possible user.js and numbered prefs-##.js files and rename (or delete) the prefs.js file to reset all prefs to the default value including prefs set via user.js and prefs that are no longer supported in the current Firefox release.

more options

Deleting all the .js files in the profile cleared all the session start problems that I was experiencing following the update to 34.0.5