Firefox ESR updates (91.4, Oct ESR 102.3)

[Member greyowl]

Helpful

Up

0

::

blur13 wrote:

The new FF 91.5.0esr (64-bit) hit the Debian buster repos today. I’m actually really impressed by how much faster it is at rendering websites compared with the old ESR release. Makes me wonder if its better to use the non-ESR version to get constant updates and improvements. It seems to make a real difference in terms of speed and efficiency.

I agree about it being snapper. I have also thought of switching to the non-esr version, but wonder if it would be as stable. I recall many years ago when FF came out with a new version for Windows which was a real problem.

I am still waiting for the FF 91 esr (32-bit) for Debian buster repos.

Dell Latitude D620 laptop with antiX 22 (64 bit)

[Member grey_rat]

Helpful

Up

0

::

For SSE, access to about:config possible if use “New Private Window”

[Moderator Brian Masinick]

Helpful

Up

0

::

greyowl wrote:

blur13 wrote:

The new FF 91.5.0esr (64-bit) hit the Debian buster repos today. I’m actually really impressed by how much faster it is at rendering websites compared with the old ESR release. Makes me wonder if its better to use the non-ESR version to get constant updates and improvements. It seems to make a real difference in terms of speed and efficiency.

I agree about it being snappier. I have also thought of switching to the non-esr version, but wonder if it would be as stable. I recall many years ago when FF came out with a new version for Windows which was a real problem.

I am still waiting for the FF 91 ESR (32-bit) for Debian buster repos.

For what it’s worth, I grabbed my own personal copy of Firefox-91.5-ESR and started using it from my own private space; I do the same for “Firefox-Release”, “Firefox-Beta”, and “Firefox-Nightly”.

I’ve also used the provided versions. I have fairly simple use cases because I predominantly use my Web browsers for Email and distribution forums.
When I do something else, such as viewing videos, etc. most of the time I use a video app or tool, so I’m not really stressing any of the browsers, at least not often. With those caveats, Firefox Release and Firefox ESR, in current form, certainly do their job to my satisfaction. As far as concerns about telemetry and other things, if they bother people, we’ve had discussions about what to do and have also suggested other alternatives. I am not personally addressing those matters.

--
Brian Masinick

[Member user2022]

Helpful

Up

0

::

> For Firefox 91 should work gfx.webrender.force-disabled true , but i don’t know how to do it.
> For SSE, access to about:config possible if use “New Private Window”

Hello!

My computer with Celeron-Tualatin cpu (with out sse2)
I try ff-91.5 on debian.
It not work like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002600 🙁
I put gfx.webrender.force-disabled=true
But nothing happen 🙁
Not work.
ff-78 work fine…

[Anonymous]

Helpful

Up

0

::

should work gfx.webrender.force-disabled true [..] how to do it

type into the browser addressbar: about:config
into the top entrybox (has magnifying glass icon, type: webrender
^—- note that as-you-type the page displays a list of prefkeys (or prefkey values) containing the matched string

The prefkey gfx.webrender.force-disabled does not exist by default,
but (while gfx.webrender.force-disabled is still displayed in the search entrybox)
we can create it by clicking the + button on the right side of the page.

We want this prefkey type to be BOOLEAN and, per your report, want its value to be TRUE.
Conveniently, this (type and value) are the default when creating a new prefkey… so nothing further needs done.
The change should take effect immediately. You can close the about:config browser tab (or switch to another tab) and test the result.

If the newly added prefkey does not have any effect, or does not produce the desired effect and you wish to remove it (or change its value), revisit about:config and type the prefkey name then click the trash can icon displayed at the right side of the page.

But nothing happen

I have no idea whether this prefkey has any effect in Firefox 91.
The above simply serves to instruct “how to do it” (add a non-existent prefkey).

• This reply was modified 1 year, 3 months ago by Brian Masinick. Reason: BOOLEAN
• This reply was modified 1 year, 3 months ago by Brian Masinick. Reason: BOOLEAN

[Member greyowl]

Helpful

Up

0

::

@ skidoo

Thanks for explaining the method and procedure for adding a prefkey to FF configuration.
I have been wanting to know how to do that in case it is necessary sometime in the future.

Dell Latitude D620 laptop with antiX 22 (64 bit)

[Member user2022]

Helpful

Up

0

::

Thank you!

I switched gfx.webrender.force-disabled to true but it not helped for me 🙁

Maybe it work only 91.4 and not work on 91.5 ?

[Anonymous]

Helpful

Up

0

::

user2022, Did you ALSO attend to the other items grey_rat mentioned?

.

http://www.antixforum.com/forums/topic/firefox-esr-update-to-91-4-1/page/3/#post-75033
grey_rat wrote:

For SSE, for Firefox 78 must be set to
media.cubeb.sandbox false
security.sandbox.content.level 2
webgl.disabled true

preferably:
dom.ipc.processCount 1
layers.async-pan-zoom.enabled false
browser.tabs.unloadOnLowMemory true
browser.tabs.remote.warmup.enabled false
layers.acceleration.force-enabled true
layers.max-active 1 or 2 (if a green window instead of a video)
gfx.webrender.force-disabled true

• This reply was modified 1 year, 2 months ago by Brian Masinick. Reason: From skidoo

[Member user2022]

Helpful

Up

0

::

> Did you ALSO attend to the other items grey_rat mentioned?

Yes.
Except
layers.max-active = 2
i try test tomorrow with
layers.max-active = 1

[Member grey_rat]

Helpful

Up

0

::

Webrender is the main change in Firefox, but it’s not related to the error SSE.
May be Proton or other

I have a note about Firefox settings in Linux, but it is russian language.
https://habr.com/ru/post/459880/

[Member grey_rat]

Helpful

Up

0

::

layers.max-active when black/green screen if used and working hardware acceleration OpenGL (layers.acceleration.force-enabled true)
example bug

[Member user2022]

Helpful

Up

0

::

grey_rat wrote:

russian language.

т.е. тоже 95-тый не заработал… понятно… спасибо за информацию, а статья интересная 🙂

I believe in Debian Team and hope what ff-95 will be work on pentium-3 🙂

[Member grey_rat]

Helpful

Up

1

::

fix for SSE on Firefox 91 esr
widget.non-native-theme.enabled false

• This reply was modified 9 months, 1 week ago by grey_rat.

[Moderator Brian Masinick]

Helpful

Up

0

::

FWIW:
https://www.mozilla.org/en-US/firefox/102.0esr/releasenotes/

--
Brian Masinick

[Member user2022]

Helpful

Up

0

::

bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002600
there is a patch for old processors and even build v91 and v102 for debian-11 (github.com/amurzeau/debian-autobuild/releases)

• This reply was modified 9 months ago by user2022.

[Author]

Posts