Siduction Forum
Siduction Forum => Upgrade Warnings => Topic started by: finotti on 2019/12/05, 22:29:30
-
Title says it all. I can see that LastPass and Privacy Badger don't work.
It seems that the official Mozilla Firefox works, but it is not just Debian: https://bugzilla.redhat.com/show_bug.cgi?id=1779762 I haven't seen a bug report for Debian yet, though.
-
Based on these recommendations (https://www.kuketz-blog.de/?s=firefox) I work with the following extensions:
Skip Redirect
uBlock Origin
uMatrix
and for me (flagfox so I can see where the journey is going)
I can't detect any interference with FF. They work as usual. :)
apt policy firefox
firefox:
Installiert: 71.0-1
Installationskandidat: 71.0-1
Versionstabelle:
*** 71.0-1 500
500 http://httpredir.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status
..
apt policy firefox-l10n-de
firefox-l10n-de:
Installiert: 71.0-1
Installationskandidat: 71.0-1
Versionstabelle:
*** 71.0-1 500
500 http://httpredir.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status
-
Indeed many extensions are not affected. Among the ones I use that work just fine are https everywhere, one tab, broken link checker... I think only LastPass and Privacy Badger are giving errors. (I don't get errors from Disconnect, but I am not sure it is working either...)
-
Hi finotti,
exactly for these reasons I've been using the original Firefox directly from Mozilla and non-distribution dependent packages for years. I never had any problems with add-ons with this Firefox installation.
Another advantage is that with the original Firefox Tar-Ball from Mozilla you get the updates much faster.
-
+1 I use the Firefox tarballs extracted to my home directory and FF71 works fine for me as well. There has to be something within the Debian (and possibly other distros) FF builds that are causing the issue.
-
It's an upstream Mozilla/FF issue, so the tarballs probably exhibit the issue too, unless you use gcc10 to compile them or don't build with optimization. I'll stick to the Debian repo version of FF..
-
It's an upstream Mozilla/FF issue, so the tarballs probably exhibit the issue too, unless you use gcc10 to compile them or don't build with optimization. I'll stick to the Debian repo version of FF..
I've just tested and the Mozilla build does not have the problem... I would rather keep the Debian version, but I still don't see a bug report, so I am trying the Mozilla version.
-
I've just tested and the Mozilla build does not have the problem...
Then they probably built without optimization or used Clang7...
-
Version 71.0-2 fixes the problem.