1716449 - Firefox 89.0.1 breaks on Fedora 34 under Mate and Nvidia 465.31 X11

Status: RESOLVED DUPLICATE of bug 1714483

(Core :: Graphics: WebRender, defect)

Description

[Bob Schultz]

Attachment: job_7647-Untitled_1.pdf

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.116 Safari/537.36

Steps to reproduce:

Upgrade firefox to 89.0.1

Actual results:

Display image messed up, weird colors and transparencies

Expected results:

normal display.
downgrading to firefox 87 restores proper operation.
see https://bugzilla.redhat.com/show_bug.cgi?id=1970473
gfx.webrender.force-disabled set to true permits correct display with 89.0.1
firefox trouble report for broken setup attached

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::Graphics: WebRender' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Comment 2

[Darkspirit]

Thanks for the report! Does this bug still occur with https://nightly.mozilla.org ?

Comment 3

[Bob Schultz]

Yes, odd bug with firefox-91.0a1.en-US.linux-x86_64.tar.bz2
Odd behavior. Very first execution, the initial page rendered was "ghosted". Firefox was then closed. Second Firefox start, the initial page displayed appeared to be rendered correctly. However, when the "help" page-->about nightly option was selected, the message display itself was "ghosted". Firefox was closed, started for the third time. This time the initial page rendered appeared ok, and the the help-->about nightly page appeared to render correctly. Something was changing upon each firefox restart.

Comment 4

[Bob Schultz]

Just tested fedora test update 90.0-1.fc34. Still has rendering bug if gfx.webrender.force-disabled is set to false. Setting to true and restarting works ok.

Comment 5

[Darkspirit]

Please open NVIDIA X Server Settings > X Screen 0 > Antialiasing Settings and check if you have manually enabled FXAA. It could be the cause. (bug 1714483)

Comment 6

[Bob Schultz]

FXAA had been enabled. Disabling FXAA appears to clear up this bug. Has been tested several times toggling the status of FXAA between Firefox starts, with consistent results.