3 ms·
For me (repository firefox on ArchLinux), the temporary fix was setting devtools.chrome.enabled = true in about:config, and running this small JavaScript snippe
by vesinisa 7y ago
For me (repository firefox on ArchLinux), the temporary fix was setting devtools.chrome.enabled = true in about:config, and running this small JavaScript snippet in Chrome DevTools (Ctrl+Shift+J):
https://wiki.archlinux.org/index.php/Firefox#Firefox_disables_all_extensions_due_to_Mozilla_not_renewing_their_certificates https://wiki.archlinux.org/index.php/Firefox#Firefox_disable...
AFAIK, this will enable all the disabled add-ons until the next check, which is in 24 hours. This will be hopefully enough time for Mozilla to release a stable channel update, instead of the "Studies hack".
At least for me, fiddling with the Studies settings had no effect; the about:studies page remained empty regardless of what I did. I've also seen multiple reports from people who got the Studies hack working that the fix actually failed to address the issue properly.
- nathanaldensr 7y agoIt appears to take several minutes for the studies to be downloaded and enabled. The process worked for me on two separate Windows 10 machines.
- deleted 7y ago[deleted]
- eikenberry 7y agoOn Linux you should also have the option of disabling the cert signature check. Go into about:config and set `xpinstall.signatures.required` to false. Just remember to set it back to true once this is fixed.