Discussion in 'other software & services' started by Rico, Aug 28, 2017.
FYI. Update Regarding Add-ons in Firefox - Last Updated: 00:54 EDT May 5 2019
@mary7 the fix in studies 1548973 was completed see post #363
Early on when this first happened, I "deleted" HTTPSeverywhere, & attempted to re-install
How.where do you access: about studies?
In the Firefox address bar type
If the fix is installed you should see this
This study sets dom.push.alwaysConnect to true.
This is a hotfix that updates an intermediate certificate used for signing add-ons. It is one of the mechanisms used to fix bug 1548973.
This study sets app.update.lastUpdateTime.xpi-signature-verification to 1556945257.
FYI. What my about:studies showed after enabling it (they were all active upon restart). This morning they were all completed. I have disabled it.
I wasn't willing to wait for a fix, so I downloaded v66.0.4 from the Mozilla ftp server. All add-ons are back.
Disabling the signing requirement is not advised because of security and also because it may conflict with the upcoming fix. If you don't want to enable Studies, you can install them manually:
It works in Firefox (52.9 ESR) on my Vista succesfuly from years I need it due to using of Cool Previews that is already abandoned and not reachable on official addons storage so now I'm already prepared to this issue
Check if you have app.normandy.enabled in about:config set to false. If you have set it to true and restart FF. Then you can enable studies and setting will stay enabled.
I thought I saw (perhaps wrong two studies 1548973 & X, apply), my post #363 shows 1548973 completed, is another study need be completed before fix?
Check post #381 a screenshot. There are two studies that have to be completed. I didn't get the second one so far.
Just happened to me on Ubuntu. Mac is OK so far.
This was at the top of page:
Way too much excitement on a Sunday evening!
I just received the .04 update and all my extesions are working again. Thank's for the heads-up though.
same here: after the update (to .04) all my extensions are back.. ... and after few minutes of testing everything seems to work fine again.
Updating to Firefox 66.0.4 fixed the extensions problem. I didnt have to do nothing but do the update. NoScript (my only addon) and the theme I use, were enabled after restarting Firefox after the update.
Okay. . . please bear with me -- it sounds like I need more help than many of you.. I suppose it's possibly due to my 'Legacy' hardware/software setup, but not sure I'm running Firefox 52.0.2 of an XP SP3 box. (BTW, I've tried upgrading Firefox to a more current version on more than one occasion, but for some reason, it won't let me do that even though some of the newer versions indicate they are still XP compatible).
Interestingly, until yesterday, everything worked just fine -- including all of my extensions So here's the deal:
1) When I try to run about:studies, I get a big popup saying: The Address Isn't Valid (the URL isn't valid and cannot be loaded).
2) Also, I don't know if all of the fixes have been distributed, but haven't had anything corrected here yet. Also, don't know if that's because I'm not able to load about:studies (BTW. . . I can load about:config, but not about:studies)
Anyway, not sure what to do now, but I'm VERY frustrated!!! If anyone can offer any help or has suggestions, anything would be greatly appreciated.
Does this help, Tom?
Note, the about:config setting mentioned towards the bottom.
Thanks so much, Krusty. Haven't tried this yet, but sure will. What I don't totally understand is that if FF has the ability to disable everything, why don't they have the ability to re-enable it again?
I don't completely understand it, but because this related to a security certificate, I guess unless that certificate is renewed before it expires this is what happens. In the case of an EOL product I guess that means you're out of luck.
Until Firefox is updated for my Linux Mint machine I've had to change the about:config setting for my extensions to work. As soon as 66.0.4 is released I can disable that setting.
Exactly what did you change in your about:config settings. Will I need to change any of the other "xpinstall..." settings? And do the extensions just start working again -- or do you have to re-enable them?
I only searched for xpinstall.signatures.required and double-clicked the setting to change the value from TRUE to FALSE . After that the extensions worked again, but when I check my extensions they show as "[name of extension] could not be verified for use in Firefox. Proceed with caution".
Just tried it and unfortunately it didn't work for me. It still says those extensions could not be verified for use in Firefox and that they have been disabled.