Closed Bug 1450436 Opened 3 years ago Closed 2 years ago

After update and restart, all my FF add-ons are deactivated.


(Toolkit :: Add-ons Manager, defect)

59 Branch
Windows 10
Not set





(Reporter: thomas.tikwinski, Unassigned, NeedInfo)



(1 file)

Attached file FF-debuginfo.json
I am running FF on auto-update. After an update, when I have restarted FF, all my web-extensions are deactivated.

The extensions are still installed, and I can re-activate them through about:plugins. Once I do this, they remain active, even if I restart FF, until the next update.

This is a bit awkward, as I am using mainly security/privacy plugins, and I'm pretty unprotected after an update until I notice the plugin icons have vanished.

I have this same behavior on a second machine (Win7, x86_64, FF59) as well, with almost the same set of plugins.

I'm attaching the debug info json file of my win 10 machine. Anything else I can provide to help, just let me know.

Component: Extension Compatibility → Add-ons Manager
Product: Firefox → Toolkit
thomas, sorry this bug was overlooked for so long.  Are you still experiencing the problem described here?
Flags: needinfo?(thomas.tikwinski)
Thanks for getting back on it. Yes, I still see the same behavior after an update of FF. Plugins are disabled and request permissions when I re-activate them.
Flags: needinfo?(thomas.tikwinski)

First of all, there's some confusion here about plugins versus extensions. Since you mention security/privacy, I assume you're talking about browser extensions but you explicitly say that you're enabling via about:plugins. Extensions cannot be managed from that page.

Can you confirm that that's a typo and you meant about:addons? If that is the case, there are a couple of things you could try to help troubleshoot this:

  1. In about:config, set the preference extensions.logging.enabled to true, then gather that logs from the browser console after starting a browser session in which extensions are unexpectedly disabled. Paste the logs into an attachment on this bug. This could be either a regular browser update or, ideally from:
  2. Try reproducing this in an otherwise clean profile (i.e., create a new profile, run an old browser version, install a minimal set [ideally 1] affected extension, perform a browser update)
Flags: needinfo?(thomas.tikwinski)

Closing due to lack of response. Please feel free to re-open if you can provide the requested information.

Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.