Updating to 60.6.2esr solved it for me but prior to that being available (and refusing to enable studies on my live system) I instead manually downloaded one of the add-on experiments and installed it and amusingly that 'add-on' fixed the other add-ons ^^ https://storage.googleapis.com/moz-fx-normandy-prod-addons/extensions/hotfix-update-xpi-intermediate@mozilla.com-1.0.2-signed.xpi After updating firefox I restored an older copy of my profile after seeing the 'experimental' add-on still installed but disabled and have had no new or recurring issues so far...
Firefox version 52.9.0esr was the last supported release for Windows XP. Should be able to update to this version or switch to Mozilla fork browsers that are being updated.
I think the .04 update has probably fixed this. I don't know how long it will take for Ubuntu to catch up. It's odd that I never experienced the bug on macOS.
Here on my pup linux the latest update has fixed this temporary issue..Thank you mozilla for being so prompt.Normal transmission now resumes and the fog has gone.
armagadd-on 2.0! https://arstechnica.com/information...led-by-certificate-bug-hotfix-for-some-ready/ On Friday, the expiration of a Mozilla certificate used to check the signatures of add-on codes in Firefox desktop and Android Web browsers caused a nearly universal failure of Firefox plug-ins and extensions as browsers detected them as invalid and disabled them. The bug, dubbed "armagadd-on 2.0," was addressed by a hot-fix issued over the weekend, and a new version of the browser has been pushed out. This isn't the first time this sort of thing has happened with Firefox. The original "armagadd-on" happened almost exactly three years ago, on May 2, 2016, when an expired certificate caused signature verification errors for add-ons.
Tom, More information about updating the certificate into FF ESR v52.9.0. https://community.norton.com/en/comment/8136611#comment-8136611
We strive to make Firefox a great experience. Last weekend we failed, and we’re sorry May 9, 2019 https://blog.mozilla.org/blog/2019/05/09/what-we-do-when-things-go-wrong/
fake extension with no gain vs firefox. with firefox 67 (bold means set here) for older or ancient browsers irrelevant - default is off. btw thats all in the code, Code: browser.webRequest.onBeforeRequest.addListener( () => ({ cancel: true }), { urls: ['*://*/*'], types: ["ping"] }, ['blocking'] ); same as item (1) in the list above. for user.js Code: user_pref("browser.send_pings", false); user_pref("browser.send_pings.max_per_link", 0); user_pref("browser.send_pings.require_same_host", true);
Sorry for the delay in responding, Krusty. I did what you suggested here and I'm back in business. Thanks so much!!!
I just opened CCleaner and checked the installed extensions in Firefox 66.0.5 and found Baidu Search Update, even though I do not have Baidu Search Engine installed. I see this has been added by Mozilla for whatever reason. What annoys the crap out of me is I used CCleaner to disable it, yet next time you open Firefox it gets re-enabled. From reading about it, you can remove it temporarily, but next time Firefox updates it gets reinstalled. I don't want that crap in my browser. Is it hurting anything? Probably not, but we are losing control of our browser. Or should I realise, we are losing control of their browser? I would also like to disable Firefox Screenshots and Firefox Autofill, but the same applies. I don't need Firefox Monitor either.
Hi Krusty, I just checked my Firefox 66.0.5 for Baidu, I dont have it. As far as I know, that search engine has not been installed or is part of my Firefox install. Bo
Well, it is here Bo on both Win10 machines as well as my Linux machine. I have never, nor would ever use Baidu, yet here it is. More information here: https://www.ghacks.net/2019/05/07/about-baidu-search-update-in-firefox/