After a couple days of regular Web browsing on two different computers running
Debian Sid, the silent add-on disabling did not happen again.
I marked this bug as fixed in version 85.0.1-1 since no one reported otherwise,
but feel free to chime in if you actually still get this issue with
On Tue, 9 Feb 2021 06:41:20 +0900 Mike Hommey wrote:
I can confirm, but while I was also able to reproduce with older
versions of Firefox, I can't reproduce it anymore... so I'm not sure...
I still reproduce the silent disabling of add-ons when reverting to firefox
84.0.2-1.
Here is how I
On Sun, Feb 07, 2021 at 04:18:50PM +0100, Antoine Le Gonidec wrote:
> With firefox 85.0.1-1, my extensions installed from Debian repositories are
> no longer disabled on launch.
>
> I made sure to restart Firefox several times to not get tricked by the
> temporary normal behaviour right after a
With firefox 85.0.1-1, my extensions installed from Debian repositories are no
longer disabled on launch.
I made sure to restart Firefox several times to not get tricked by the
temporary normal behaviour right after a firefox update. I browsed a couple Web
pages too, to check that the add-ons
I've been suffering with this problem for a while as well. I have four
extensions installed from Debian packages: HTTPS Everywhere, NoScript,
Privacy Badger, and uBlock Origin. They all keep disappearing from the
toolbar and stop functioning. I agree that this is an important bug,
since besides
On Sun, 29 Nov 2020 16:25:00 +0100 Mourad De Clerck
wrote:
> I suspect this is upstream bug #1672139:
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=1672139
That upstream bug appears to be about addon overlays not being rendered
properly: they appear to be enabled, and just not rendering
On Mon, Nov 30, 2020 at 10:09:56PM +0100, Antoine Le Gonidec wrote:
> My add-ons installed from Debian repositories are still silently disabled on
> launch, I have to switch them off then on again to get them working for the
> current session. And of course start again when I restart Firefox.
>
Le 30/11/2020 à 18:02, Mourad De Clerck a écrit :
Can you verify in "about:support" whether webrender is really disabled? I see:
* "Compositing: Basic"
* "WEBRENDER: disabled by user: User force-disabled WR"
Informations from the "WEBRENDER" tab are:
- available by default
- disabled by user:
Le 29/11/2020 à 16:25, Mourad De Clerck a écrit :
As a workaround, I disabled webrender using "gfx.webrender.force-disabled" set to
"true", and my extensions (ublock, bitwarden) seem to work properly again.
Did you check that the add-ons are still active after a couple restarts of
Firefox?
On 30/11/2020 17:45, Antoine Le Gonidec wrote:
Did you check that the add-ons are still active after a couple restarts
of Firefox?
The suggested workaround seems to have no effect here.
I just tried restarting multiple times (4-5), it still works for me.
Can you verify in "about:support"
I suspect this is upstream bug #1672139:
https://bugzilla.mozilla.org/show_bug.cgi?id=1672139
As a workaround, I disabled webrender using
"gfx.webrender.force-disabled" set to "true", and my extensions (ublock,
bitwarden) seem to work properly again.
-- M
I'm experiencing this as well. I've installed
webext-ublock-origin-firefox, and each time I restart the browser,
uBlock Origin isn't enabled (no toolbar icon, and ads not blocked) until
I go into about:addons and toggle it off and back on.
HTTPS Everywhere, installed via the upstream addon
Control: found -1 82.0-1
FTR I am still experiencing this with the latest release.
Steps to reproduce (quit after 10s each time Firefox starts):
mkdir tmp-firefox-profile
firefox -no-remote -profile tmp-firefox-profile
firefox -no-remote -profile tmp-firefox-profile
firefox -no-remote -profile
Control: retitle -1 firefox: FF80 broke webext-* add-ons on existing profiles
and new profiles after three restarts
On Wed, 2020-09-23 at 19:44 +0900, Yuya Nishihara wrote:
> If I restarted firefox 3 times, the problem came back.
I noticed that this 3 restart thing also applies to new
On Wed, 2020-09-23 at 19:44 +0900, Yuya Nishihara wrote:
> Not for me. If I restarted firefox 3 times, the problem came back.
Arghh, me too now :(
I think this issue needs to be fixed before it reaches the ESR series.
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description:
On Wed, 23 Sep 2020 15:54:06 +0800 Paul Wise wrote:
> This appears to be fixed for me in 81.0-1, can anyone else confirm?
Here it looked like it was fixed right after the update.
But very quickly after that (3 browser restarts), the add-ons are disabled once
again. Now I’m back to the previous
On Wed, 2020-09-23 at 19:44 +0900, Yuya Nishihara wrote:
> Not for me. If I restarted firefox 3 times, the problem came back.
Same here, the 3rd time starting after the upgrde, the issue is back.
Cheers,
Chris.
On Wed, 23 Sep 2020 15:54:06 +0800, Paul Wise wrote:
> On Fri, 28 Aug 2020 17:18:44 +0200 Christoph Anton Mitterer wrote:
> > It seems that with FF80 all addons are broken in existing profiles. They're
> > shown
> > in the add-ons list, but e.g. their icons aren’t in the menu.
>
> This appears
On Fri, 28 Aug 2020 17:18:44 +0200 Christoph Anton Mitterer wrote:
> It seems that with FF80 all addons are broken in existing profiles. They're
> shown
> in the add-ons list, but e.g. their icons aren’t in the menu.
This appears to be fixed for me in 81.0-1, can anyone else confirm?
--
bye,
I think the severity of this bug should be upped to at least "important".
The reasoning here is that any privacy-related add-on installed through Debian
repositories is automatically (and silently) disabled on launch, leading to
privacy leaks when opening a link in Firefox from another
I removed the 3 packages :
sudo apt purge webext-noscript webext-privacy-badger
webext-ublock-origin-firefox
I then installed the 3 extensions from the Firefox add-ons repo.
And everything works fine.
So, most probably, FF80 checks add-ons and removes/disables old ones.
I Cc this to webext
El sábado, 5 de septiembre de 2020 6:40:36 (CEST) Christoph Anton Mitterer
escribió:
> Strangely enough... the issue is back for me after another restart of
> firefox... o.O
The issue is also back in here. Unfortunately.
Regards,
--
Rául Sánchez Siles
signature.asc
Description: This is a
Strangely enough... the issue is back for me after another restart of
firefox... o.O
On Thu, 2020-09-03 at 22:43 +0200, Raúl Sánchez Siles wrote:
> Fortunately 80.0.1-1 came around and this bug has been somehow
> fixed or not exposed. This is what I can tell so far. Let me know if
> I can provide any more helpful information.
yes... that seems to fix it...
Cheers,
Chris.
Hi all:
Fortunately 80.0.1-1 came around and this bug has been somehow fixed or not
exposed.
This is what I can tell so far. Let me know if I can provide any more helpful
information.
Regards,
El jueves, 3 de septiembre de 2020 11:49:04 (CEST) Raúl Sánchez Siles escribió:
> Hi:
>
>
Hi:
El jueves, 3 de septiembre de 2020 6:54:23 (CEST) Mike Hommey escribió:
> On Thu, Sep 03, 2020 at 06:41:55AM +0200, Christoph Anton Mitterer wrote:
> > On Thu, 2020-09-03 at 10:37 +0900, Mike Hommey wrote:
[...]
>
> Try going to about:config, switch extensions.logging.enabled to true,
>
On Thu, Sep 03, 2020 at 06:41:55AM +0200, Christoph Anton Mitterer wrote:
> On Thu, 2020-09-03 at 10:37 +0900, Mike Hommey wrote:
> > With the following steps, I _don't_ reproduce:
> > - create a fresh unstable chroot and enter it
> > - install firefox 79 and webext-ublock-origin
> > - start
On Thu, 2020-09-03 at 10:37 +0900, Mike Hommey wrote:
> With the following steps, I _don't_ reproduce:
> - create a fresh unstable chroot and enter it
> - install firefox 79 and webext-ublock-origin
> - start firefox
> - stop firefox
> - upgrade firefox to 80
> - start firefox
Well... god know
On Sat, Aug 29, 2020 at 03:57:17PM +0200, Christoph Anton Mitterer wrote:
> On Sat, 2020-08-29 at 10:55 +0200, Jean-Marc wrote:
> > One remark nevertheless : if I open the page about:support and click
> > on the button "Refresh Firefox..." and then re-start Firefox, I got
> > the icon of the
On Fri, 28 Aug 2020 17:18:44 +0200 Christoph Anton Mitterer wrote:
> It seems that with FF80 all addons are broken in existing profiles.
I noticed the same issue too.
I note that the issue does *not* occur in new profiles.
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
On Sat, 2020-08-29 at 10:55 +0200, Jean-Marc wrote:
> One remark nevertheless : if I open the page about:support and click
> on the button "Refresh Firefox..." and then re-start Firefox, I got
> the icon of the add-ons I installed through Debian packages meaning
> noScript, privacy Badger and
On Fri, 28 Aug 2020 17:18:44 +0200 Christoph Anton Mitterer
wrote:
> Package: firefox
> Version: 80.0-1
> Severity: normal
>
>
> Hi.
>
> It seems that with FF80 all addons are broken in existing profiles. They're
> shown
> in the add-ons list, but e.g. their icons aren’t in the menu.
>
>
On Fri, Aug 28, 2020 at 05:18:44PM +0200, Christoph Anton Mitterer wrote:
> Package: firefox
> Version: 80.0-1
> Severity: normal
>
>
> Hi.
>
> It seems that with FF80 all addons are broken in existing profiles. They're
> shown
> in the add-ons list, but e.g. their icons aren’t in the menu.
>
Package: firefox
Version: 80.0-1
Severity: normal
Hi.
It seems that with FF80 all addons are broken in existing profiles. They're
shown
in the add-ons list, but e.g. their icons aren’t in the menu.
E.g. ublock origin, noscript also don't seem to work... so it's not just a
display
issue.
34 matches
Mail list logo
