1814919 - Firefox Snap/X11-only (Xwayland is fine)/Ubuntu 22.04 LTS/Radeon: entire window is glitchy

Status: RESOLVED WORKSFORME

(Firefox Build System :: Third Party Packaging, defect, P3)

Description

[CMR]

Attachment: Screenshot from 2023-02-03 11-24-47.png

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/109.0

Steps to reproduce:

Launch Firefox while using xorg display server desktop

Actual results:

the firefox window fails to draw correctly, with many horizontal lines missing from the image. further interactions with the program makes the corruption worse (see attached screenshot).

Expected results:

Normal operation.
Notes: using Ubuntu LTS 22.04.1 with AMD graphics (Radeon rx 5500 xt).
Some combination of updates this week are not playing well together.
Workaround: issue does not happen with the Wayland desktop.

Comment 1

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

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

Comment 2

[Darkspirit]

Thanks for the report! Please open about:support, click on "Copy text to clipboard" and paste it here.

Does this bug also occur if you start a Mozilla-built Firefox on x11?
$ pip3 install mozregression
$ ~/.local/bin/mozregression --launch 109.0.1

Comment 3

[CMR]

Attachment: about : suport text

the support text requested by Darkspirit. This was collected while logged into the Wayland desktop, but hopefully still useful.

Comment 4

[CMR]

(In reply to Darkspirit from comment #2)

Thanks for the report! Please open about:support, click on "Copy text to clipboard" and paste it here.

Does this bug also occur if you start a Mozilla-built Firefox on x11?
$ pip3 install mozregression
$ ~/.local/bin/mozregression --launch 109.0.1

that worked, its just missing my user profile data. Guess that means something went wrong with the snap package?

Comment 5

[Darkspirit]

Does this problem still exist with Snap Firefox 111 on X11?
Start Snap Firefox 111 with the following command to check if you get any error messages in the terminal: $ snap run firefox
Please also attach its about:support. Thanks!

---

A previous Firefox-launch has hit a driver problem:

gfx.blacklist.layers.opengl.failureid: FEATURE_FAILURE_SOFTWARE_GL

Comment 6

[CMR]

(In reply to Darkspirit from comment #5)

Does this problem still exist with Snap Firefox 111 on X11?
Start Snap Firefox 111 with the following command to check if you get any error messages in the terminal: $ snap run firefox
Please also attach its about:support. Thanks!

---

A previous Firefox-launch has hit a driver problem:

gfx.blacklist.layers.opengl.failureid: FEATURE_FAILURE_SOFTWARE_GL

Hi sorry I just noticed this question. The problem has persisted with newer versions (now at 112.0.2). when launched from the terminal I get the following output, though to be fair I get basically the same of under Wayland as well

Gtk-Message: 22:17:34.848: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
amdgpu: os_same_file_description couldn't determine if two DRM fds reference the same file description.
If they do, bad things may happen!
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
[ERROR glean_core] Error setting metrics feature config: Json(Error("EOF while parsing a value", line: 1, column: 0))
ALSA lib conf.c:4120:(snd_config_update_r) Cannot access file /usr/share/alsa/alsa.conf
ALSA lib seq.c:935:(snd_seq_open_noupdate) Unknown SEQ default

Comment 7

[:gerard-majax]

I know there were several Mesa bugs related to AMD GPUs fixed in the past months, can you confirm it is fixed with recent versions ?

Comment 8

[:gerard-majax]

Also please note Firefox and its Snap package version will soon default to Wayland, so given the comment here indicates Wayland is fine, we will probably WONTFIX it at that time ?

Comment 9

[CMR]

(In reply to :gerard-majax from comment #7)

I know there were several Mesa bugs related to AMD GPUs fixed in the past months, can you confirm it is fixed with recent versions ?

There was a point where the problem expanded to effect Wayland as well, at least on the non-beta builds, and I opened a second ticket at that time (see 1842654). currently the issue seems to be resolved and I'm back on the stable release (119.0-2).

Comment 10

[:gerard-majax]

No report for a long time, not much activity, wayland is default for a long time now and newer version of Mesa are shipping