X
Tap here to go to the mobile version of the site.

Support Forum

You broke half of my addons on v56 and v54, studies fix is active, disabling singing did nothing. How to fix your failures?

Posted

Details: in title.

I sit on a super old version so you don't break my addons and you still manage to break them....

Details: in title. I sit on a super old version so you don't break my addons and you still manage to break them....

Chosen solution

UPDATE: Firefox 66.0.4 and 60.6.2esr are now available with the new certificate needed to solve this problem. See: Update Firefox to the latest release.

Hi UsernameX, I don't know why the study hasn't come through. Maybe there was a change to how they work in a later version of Firefox, and it's not backwards compatible?

The study downloads a hotfix extension, and the hotfix extension installs a new certificate. So your options are:

(A) Wait for further official, supported solution(s) -- we don't know whether these will apply for non-current releases

(B) Download the hotfix extension directly and see whether it works (not officially supported)

(C) Install the certificate directly and then manually trigger re-verification (not officially supported)

For B and C:

B: Hotfix extension URL

I know this looks totally strange, but this is the one I have:

https://storage.googleapis.com/moz-fx-normandy-prod-addons/extensions/hotfix-update-xpi-intermediate%40mozilla.com-1.0.2-signed.xpi

("Normandy" is the system for managing studies.)

C: Manual certificate installation

I've posted detailed steps for Firefox 52 ESR users. The screens are a bit different, but you would use the same technique in newer versions of Firefox. See: https://support.mozilla.org/en-US/questions/1258165#answer-1218833

Read this answer in context 1

Additional System Details

Installed Plug-ins

  • Shockwave Flash 32.0 r0

Application

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

More Information

jscher2000
  • Top 10 Contributor
8789 solutions 71880 answers

A critical certificate used in verifying add-on signatures expired, so you need a hotfix to install, enable, or update most add-ons. More info in this article:

Add-ons disabled or fail to install on Firefox

A critical certificate used in verifying add-on signatures expired, so you need a hotfix to install, enable, or update most add-ons. More info in this article: [[Add-ons disabled or fail to install on Firefox]]

Question owner

I read that. I wrote in the title that the studies system is on and singing bugfix is active. I did notice now that besides the active study the other (*timestamp*) one is required yet hours passed and nothing changed. Also, there's no app.normandy.run_interval_seconds in my about config. I imagine the "general" fix won't help users refusing to get rid of most of their addons (by disabling old addons). So what can I do? Wait more?

I read that. I wrote in the title that the studies system is on and singing bugfix is active. I did notice now that besides the active study the other (*timestamp*) one is required yet hours passed and nothing changed. Also, there's no app.normandy.run_interval_seconds in my about config. I imagine the "general" fix won't help users refusing to get rid of most of their addons (by disabling old addons). So what can I do? Wait more?
jscher2000
  • Top 10 Contributor
8789 solutions 71880 answers

Chosen Solution

UPDATE: Firefox 66.0.4 and 60.6.2esr are now available with the new certificate needed to solve this problem. See: Update Firefox to the latest release.

Hi UsernameX, I don't know why the study hasn't come through. Maybe there was a change to how they work in a later version of Firefox, and it's not backwards compatible?

The study downloads a hotfix extension, and the hotfix extension installs a new certificate. So your options are:

(A) Wait for further official, supported solution(s) -- we don't know whether these will apply for non-current releases

(B) Download the hotfix extension directly and see whether it works (not officially supported)

(C) Install the certificate directly and then manually trigger re-verification (not officially supported)

For B and C:

B: Hotfix extension URL

I know this looks totally strange, but this is the one I have:

https://storage.googleapis.com/moz-fx-normandy-prod-addons/extensions/hotfix-update-xpi-intermediate%40mozilla.com-1.0.2-signed.xpi

("Normandy" is the system for managing studies.)

C: Manual certificate installation

I've posted detailed steps for Firefox 52 ESR users. The screens are a bit different, but you would use the same technique in newer versions of Firefox. See: https://support.mozilla.org/en-US/questions/1258165#answer-1218833

'''UPDATE: Firefox 66.0.4 and 60.6.2esr are now available with the new certificate needed to solve this problem. See: [[Update Firefox to the latest release]].''' Hi UsernameX, I don't know why the study hasn't come through. Maybe there was a change to how they work in a later version of Firefox, and it's not backwards compatible? The study downloads a hotfix extension, and the hotfix extension installs a new certificate. So your options are: (A) Wait for further official, supported solution(s) -- we don't know whether these will apply for non-current releases (B) Download the hotfix extension directly and see whether it works (not officially supported) (C) Install the certificate directly and then manually trigger re-verification (not officially supported) For B and C: ''B: Hotfix extension URL'' I know this looks totally strange, but this is the one I have: https://storage.googleapis.com/moz-fx-normandy-prod-addons/extensions/hotfix-update-xpi-intermediate%40mozilla.com-1.0.2-signed.xpi ("Normandy" is the system for managing studies.) ''C: Manual certificate installation'' I've posted detailed steps for Firefox 52 ESR users. The screens are a bit different, but you would use the same technique in newer versions of Firefox. See: https://support.mozilla.org/en-US/questions/1258165#answer-1218833

Modified by jscher2000

Question owner

I went with option C. It solved my problem both on v54 and v56 for most of the addons including all addons I actually cared about and actively used.

Thank you for your support jscher2000.

I went with option C. It solved my problem both on v54 and v56 for most of the addons including all addons I actually cared about and actively used. Thank you for your support jscher2000.