I use Pale Moon on my Win7 media box but it doesn’t support web extensions which means I can’t use FB Purity to make Faceplant bearable. If PM ever supports FB Purity I’ll be on it like a shot.
According to the FB Purity FAQ, it will work on Pale Moon if you first install Greasemonkey for Pale Moon and then get the GM Script version of FB Purity from their install page.
Yeah, but Greasemonkey is a PITA and I don’t feel like fucking with it. I mostly run FB on Chrome any more with everything else running on a FF window, started doing that a while ago when I was resisting updating FF because I’d lose too many cool extensions I like then when I bowed to the inevitable (FF just stopped working) I kept doing it this way because I’m used to it. Faceplant has a tendency to freeze up a browser significantly and having Chrome freezing because of a script in FB doesn’t impact the rest of my browsing on FF.
I went to update firefox today and everything is back to normal. Didn’t have to make any system changes. About what I expected.
As noted in the other thread, Android versions still appear to be broken. At least, Firefox still claims that the uBlock Origin addon “can’t be verified”. I can get it to work only by disabling the requirement for signature verification as I mentioned above.
It nailed me while I was out doing yardwork so I did the about:debugging temp fix which seems to be working fine–I don’t shut down my browser all that often anyway so I’ll just let it ride until I’m sure letting it update won’t break more shit.
Was sitting here & watched the “some add-ons have been disabled” pop up again. Had to set the date back (but not too far back - May '18 didn’t work, May 1[sup]st[/sup] of this year did.) & I’m back in business…for now, again. Hmmm, it’s about 24 hours exactly since it first crapped out. :mad:
The easiest fix is to install the hotfix directly using this addon. That worked for me on Linux and Android. This comes from the third comment at this Firefox blog entry, which got it from a comment at Hacker News.
I was able to manually restore my container extension-dependent tabs using this technique. Pretty easy.
As of yesterday afternoon, I was still being told that uBlock Origin for mobile wasn’t verified.
I manually changed my computer’s date to May 1, 2019, closed browser, opened it, and re-added the addon I wanted (theme). Then I changed the date back to today. So far, it’s holding. <shrug> Don’t have time to search out the other addons at the moment. FWIW.
Well, that didn’t last. Firefox disabled the theme. Poop.
How come I use Firefox and have not had any apps disabled or any other problems? Why did all you others have trouble and I did not? (I allow automatic updates, so it’s not that.)
Likewise, although I did disable automatic updates when the troubles began (I’m on 66.0.3, and the “About Mozilla Firefox” window says it’s up to date).
I checked my (three) addons when the Pit thread opened, and they all had a “new version available” button; today they all show normal.
I’m using 66.0.3 - 64-bit. Would that make a difference?
Mine is also 64-bit, for what it’s worth.
I now have an invite to up(?)grade to 66.0.4. Think I’ll set a restore point first.
My downloaded themes seem to be working fine at this point; so is Firefox Color.
Disabling updates would not have helped (unless you’ve had them disabled since something like Firefox 46 or something), since it was an expiring certificate and not something that broke as a result of a push.
My understanding is that Firefox only checks the cert once per day, so it’s possible that some people weren’t affected just by virtue of the check happening outside of the timeframe of the problem.
Thanks for this. I had been wondering how come I escaped the problems.
I got hit with it Saturday, 2 PM Chicago time. I enabled Studies like the bug fix said, and about 6 hours later the fix was installed.
For future reference: how to back up your Firefox profile Back up and restore information in Firefox profiles | Firefox Help