Closed Bug 1549071 Opened 6 years ago Closed 6 years ago

66.0.3 update disables addons and will not allow reinstall

Categories

(Toolkit :: Add-ons Manager, defect)

66 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1548973

People

(Reporter: jhibbard, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0

Steps to reproduce:

  1. Updated to 66.0.3 from whatever was current before 66.0.3
  2. Got message that "some" addons" were disabled
  3. Checked addons to find ALL addons had been disabled
  4. Attempted to reinstall any addon
  5. Got message (below) saying that 66.0.3 was blocking install of addon in question: "Firefox has prevented this site from asking you to install software on your computer"
    6.Uninstalled 66.0.3
  6. Installed 66.0.3
    8 Goto to 4 above

Notes:
In order to see blocking message, Right click "Add to Firefox" and choose "Open in new Tab (or Window).
Also, message disapears if you goto another tab (or Window).
Also entered this as 1548973 since the original listing was 15 years old.
There appears to be some relationship between addons that were installed previous to the update from 66.0.3 from whatever vs was current before the release of 66.0.3. If I attempt to install some addon that was NOT installed before the update to 66.0.3, the addon installs without issue (regardless of fresh install of 66.0.3 or update to the same).

Actual results:

Message stating that 66.0.3 was blocking install of addon.

Expected results:

Duh?

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
Component: Untriaged → Add-ons Manager
Product: Firefox → Toolkit

What is "Normandy fix" and what does it entail?
Was this "expiration" a clever and sinister trick to get more tracking added to the user's systems?

Overall, this travesty demonstrates how irresponsible the "open source" projects, including Mozilla, have become, where they completely disrespect their user base and hold us with contempt. BOO!

You need to log in before you can comment on or make changes to this bug.