They already fixed it a couple of hours after the issue.
Em seg, 6 de mai de 2019 às 11:45, Juan Francisco Cantero Hurtado < i...@juanfra.info> escreveu: > On Mon, May 06, 2019 at 11:54:04AM +0300, Dumitru Moldovan wrote: > > On Sat, May 04, 2019 at 10:13:39PM +0200, Juan Francisco Cantero Hurtado > wrote: > > > On Sat, May 04, 2019 at 07:01:55PM +0100, Anthony Campbell wrote: > > > > After upgrading Firefox today to 66.0.3 in -current, all my add-ons > > > > were inactivated. A quick search showed that this is a widespread > > > > problem, apparently due to a bug in FF. I was able to fix it > > > > temporarily by means of a suggestion on ghacks.net to change > > > > > > > > xpinstall.signatures.required > > > > > > > > in about.config to "false". > > > > > > > > Presumably it will be fixed soon upstream. > > > > > > Disabling signature checks is almost always a bad idea. > > > > > > Open this url with firefox and install the extension. > > > > > > > https://storage.googleapis.com/moz-fx-normandy-prod-addons/extensions/hotfix-update-xpi-intermediate%40mozilla.com-1.0.2-signed.xpi > > > > > > Installing random extensions from the big bad Internet is almost always > > a bad idea. :-D > > The extension is signed by Mozilla. Just in case someone doesn't know, > the xpi extensions are just zip files. If you're worried about what > you're installing, unzip the file and check the content. The changes are > in the file "experiments/skeleton/api.js". > > > > > > This issue was fixed upstream in Firefox 66.0.4. Use Landry Breuil's > > repo to keep Firefox updated in -stable or -release. More at > > https://undeadly.org/cgi?action=article&sid=20170425173917. > > > > Final result from pkg_add should be: > > > > firefox-66.0.2->66.0.4: ok > > > > -- > Juan Francisco Cantero Hurtado http://juanfra.info > >
