We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

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

Updated to FireFox 11 and I keep getting "checking compatibility of add-on" when I start the browser.

  • 5 odgovora
  • 14 ima ovaj problem
  • 5 prikaza
  • Posljednji odgovor od cor-el

more options

I just updated to FireFox 11 and whenever I start the browser, I get that annoying window that checks for the compatibility of add-ons.

I have looked around for solutions and have tried the following: 1. Deleting several extension files from the profile folder. 2. Going to about:config to disable the extension:checkcompatibility (does not exist there).

None of these worked.

I just updated to FireFox 11 and whenever I start the browser, I get that annoying window that checks for the compatibility of add-ons. I have looked around for solutions and have tried the following: 1. Deleting several extension files from the profile folder. 2. Going to about:config to disable the extension:checkcompatibility (does not exist there). None of these worked.

Izabrano rješenje

Did you try to delete the file prefs.js?

Which security software (firewall, anti-virus) do you have?

Some security software has virtualization features that can cause problems by protecting and restoring files in the Firefox profile folder.

Pročitaj ovaj odgovor u kontekstu 👍 0

Svi odgovori (5)

more options

Odabrano rješenje

Did you try to delete the file prefs.js?

Which security software (firewall, anti-virus) do you have?

Some security software has virtualization features that can cause problems by protecting and restoring files in the Firefox profile folder.

more options

Prefs.js didn't fix it. But the removal of user.js did. Thank you!

more options

You're welcome.

Do you know which line(s) in the user.js file were causing the problems?

A user.js file is only present if you or another extension or program have created such a file.

more options

No, sorry I don't. Without opening it, I just deleted that file expecting a new one would generate when I restart FireFox like the Prefs.

If I get the same issue again on the next FireFox update, I will look into it and post it.