Closed Bug 1847175 Opened 11 months ago Closed 9 months ago

Snap/Radeon: window corruption - unreadable window contents

Categories

(Core :: Graphics, defect)

Firefox 116
Unspecified
Linux
defect

Tracking

()

RESOLVED FIXED

People

(Reporter: mamozrk, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(4 files)

Firefox window display is corrupted (see attachment).
Even the Select User Profile window is affected (I was going to try a new user profile, but stopped when I saw that).
All my other programs are displaying correctly (including Chromium, which is how I can submit this report)
Ubuntu 22.04 LTS, using the official Firefox snap, all up-to-date
Graphics card is an AMD RX5500XT, I'm using the open source drivers

Component: General → Graphics
Product: Firefox → Core
Blocks: gfx-triage
Blocks: snap
See Also: → 1828196, 1814919, 1828757
Summary: window corruption - unreadable window contents (Linux AMD) → Snap/Radeon: window corruption - unreadable window contents

Martin, do you know if the official snap build is using wayland?

Flags: needinfo?(stransky)
Severity: -- → S2

NI - I will look at this as well, I would like to confirm if we ship Wayland by default, and whether the snap is using Wayland by default (it should be).

Flags: needinfo?(ahale)

No, Wayland isn't shipped yet (bug 1836342): https://github.com/canonical/firefox-snap/blob/stable/firefox.launcher#L55
"See Also[s]": Such a bug has been reported for X11 (not Xwayland, not Wayland).
There has also been bug 1822908 (Radeon) which has been closed as duplicate of bug 1821944 (Nvidia).

(In reply to Mark Tyndall from comment #0)
Please open about:support (type it in the address bar and press enter), click on "Copy text to clipboard" (2nd button at the top left) and paste it here. Thanks!

As Darkspirit says, AFAIK snap doesn't use Wayland yet.

But we use the same gfx codepath for Wayland and X11 now (EGL/dmabuf) so I don't thin it's can be fixed or caused by Wayland.
This one really looks like a typical AMD driver bug (AMD is know to be more or less buggy).

Flags: needinfo?(stransky)

Mark, can you:

  1. do what Darkspirit suggests, i.e. attach about:support page here.

  2. Try Mozilla binaries: https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Testing_Mozilla_binaries

  3. run firefox on terminal as:

LIBGL_ALWAYS_SOFTWARE=1 firefox

and check the corruption? (that forces SW rendering).

Thanks.

Hi Martin, Darkspirit,
I'm temporarily in a different country to the affected computer; I'll be back in front of it in a couple of weeks.

However, in the mean while, I'll note that I'd applied the workaround from the bug report in comment #1

   MOZ_ENABLE_WAYLAND=1 firefox

and this solved the corruption problem I was having.

Do you want the about:support info without any environment variables (does it matter)? It might be quite tricky when I can't see the window contents...

Flags: needinfo?(mamozrk)

This is the about:support text for the corrupted screen state.

Flags: needinfo?(mamozrk)
Flags: needinfo?(ahale)

This is about:support text with the MOZ_ENABLE_WAYLAND=1 environment variable set, as mentioned in Comment 7. This fixes the window corruption

This is the about:support text with LIBGL_ALWAYS_SOFTWARE=1 set, as requested in Comment 6. This also fixes the issue.

Finally, trying the Mozilla binaries (Comment 6, item 2) also fixes the issue.

Running Firefox with any of

MOZ_ENABLE_WAYLAND=0 ./firefox -ProfileManager -no-remote
MOZ_ENABLE_WAYLAND=1 ./firefox -ProfileManager -no-remote
./firefox -ProfileManager -no-remote

fixes the window corruption.

(In reply to Mark Tyndall from comment #11)

Finally, trying the Mozilla binaries (Comment 6, item 2) also fixes the issue.

Running Firefox with any of

MOZ_ENABLE_WAYLAND=0 ./firefox -ProfileManager -no-remote
MOZ_ENABLE_WAYLAND=1 ./firefox -ProfileManager -no-remote
./firefox -ProfileManager -no-remote

fixes the window corruption.

Thanks for testing.

Can you check which Compositing is used by Mozilla binaries? At about:support please look at Compositing field. Is there 'Compositing: WebRender' or 'Compositing: WebRender (Software)'?

Thanks.

Flags: needinfo?(mamozrk)

That field says:
Compositing: WebRender
(for all of the three ways of starting Firefox).

Flags: needinfo?(mamozrk)

So only Firefox/Snap/X11 is affected, right? That's interesting.

See Also: → 1850318

Who should we talk to in terms of a snap maintainer?

Flags: needinfo?(stransky)

I think Olivier Tilloy is the right person here.

Flags: needinfo?(stransky) → needinfo?(olivier)

Redirect a needinfo that is pending on an inactive user to the triage owner.
:bhood, since the bug has high severity and recent activity, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(olivier) → needinfo?(bhood)

Martin, know of anybody else?

Flags: needinfo?(bhood) → needinfo?(stransky)

Maybe Alexandre?

Flags: needinfo?(stransky) → needinfo?(lissyx+mozillians)

(In reply to Kelsey Gilbert [:jgilbert] from comment #15)

Who should we talk to in terms of a snap maintainer?

what is the question ?

Flags: needinfo?(lissyx+mozillians) → needinfo?(jgilbert)

(In reply to Mark Tyndall from comment #1)

Further searching reveals that it's https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2004532

This mentions core22 fixes, and above all the about:support links to versions < 117. With 117 it is built with core22 so the issue should get fixed by upgrading now.

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

This mentions core22 fixes, and above all the about:support links to versions < 117. With 117 it is built with core22 so the issue should get fixed by upgrading now.

I've tested again with version 117, and I have uncorrupted windows without needing to add environment variables or command-line flags.
Many thanks to everyone who helped.

Mark, should we now consider this resolved?

Flags: needinfo?(mamozrk)

Yes, indeed. RESOLVING this as FIXED.

Status: NEW → RESOLVED
Closed: 9 months ago
Flags: needinfo?(mamozrk)
Resolution: --- → FIXED
No longer blocks: snap
Flags: needinfo?(jgilbert)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: