Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#76924 - [mesa][firefox] Broken rendering with hardware acceleration

Attached to Project: Arch Linux
Opened by Nicola Mori (snack) - Saturday, 24 December 2022, 11:34 GMT
Last edited by Toolybird (Toolybird) - Saturday, 21 January 2023, 21:52 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
Some combinations of firefox and mesa leads to broken rendering on my system (Nvidia 8800 GTS 320 MB with nouveau driver). Firefox 108 does not work with any version of mesa, while firefox 107 works with mesa 22.1.7 but is broken with newer mesa versions. Disabling hardware acceleration fixes the problem.

Additional info:
* package version(s)
firefox 108.0.1 + mesa (any version) or firefox < 108 with mesa >= 22.2
linux 5.15.82-1-lts
This task depends upon

Closed by  Toolybird (Toolybird)
Saturday, 21 January 2023, 21:52 GMT
Reason for closing:  Fixed
Additional comments about closing:  See comments
Comment by Mariusz Smołka (Freyon77) - Saturday, 24 December 2022, 20:40 GMT
Hello
If:
Firefox 108 (latest)
Mesa (latest)
Then what happens?
The browser does not start?
Does the process appear in the process list after failing to start?
If so, we have the same problem
Latest mesa and firefox along with radeon r7 350.
Since this mesa update firefox is also not working for me.
Of course there is a way around it.
-kill the process dozens of times, after which time you will be able to start firefox.
But I will not elaborate please just confirm if it is the same bug
I would still add that maybe firefox is not a good place for this bug and the culprit may be mesa.
Comment by Mariusz Smołka (Freyon77) - Saturday, 24 December 2022, 22:26 GMT
Can You try enable hardware acceleration and open Firefox with ppm and select open new tab?
Comment by Mariusz Smołka (Freyon77) - Sunday, 25 December 2022, 06:14 GMT
I searched the web on this and you can still try to kill process firefox with the highest pid and try to run.
And as for this new tab trick you have to try it after reboot, there must not be any firefox process in the background
Comment by Nicola Mori (snack) - Sunday, 25 December 2022, 08:43 GMT
The browser starts fine but the rendered window is garbage. So I think your issue is a different one.
Comment by Toolybird (Toolybird) - Monday, 26 December 2022, 00:06 GMT
When you say "hardware acceleration" do you mean the tick box within firefox settings or the configuration setup as per [1]?

[1] https://wiki.archlinux.org/title/Firefox#Hardware_video_acceleration
Comment by Nicola Mori (snack) - Monday, 26 December 2022, 09:39 GMT
For "disabling hardware acceleration" I mean Settings -> Performance -> uncheck "Use recommended performance settings" -> uncheck "Use hardware acceleration when available".
Comment by Nicola Mori (snack) - Saturday, 21 January 2023, 18:02 GMT
Today I made new tests with a fully up-to-date system and the error seems gone. So I think it has been fixed at a certain point, probably in firefox.

Loading...