Snap/Radeon: window corruption - unreadable window contents
Categories
(Core :: Graphics, defect)
Tracking
()
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
Reporter | ||
Comment 1•1 year ago
|
||
Further searching reveals that it's https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2004532
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Comment 2•1 year ago
|
||
Martin, do you know if the official snap build is using wayland?
Updated•1 year ago
|
Comment 3•1 year ago
|
||
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).
Comment 4•1 year ago
|
||
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!
Comment 5•1 year ago
|
||
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).
Comment 6•1 year ago
|
||
Mark, can you:
-
do what Darkspirit suggests, i.e. attach about:support page here.
-
Try Mozilla binaries: https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Testing_Mozilla_binaries
-
run firefox on terminal as:
LIBGL_ALWAYS_SOFTWARE=1 firefox
and check the corruption? (that forces SW rendering).
Thanks.
Reporter | ||
Comment 7•1 year ago
|
||
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...
Reporter | ||
Comment 8•1 year ago
|
||
This is the about:support text for the corrupted screen state.
Reporter | ||
Comment 9•1 year ago
|
||
This is about:support text with the MOZ_ENABLE_WAYLAND=1 environment variable set, as mentioned in Comment 7. This fixes the window corruption
Reporter | ||
Comment 10•1 year ago
|
||
This is the about:support text with LIBGL_ALWAYS_SOFTWARE=1 set, as requested in Comment 6. This also fixes the issue.
Reporter | ||
Comment 11•1 year ago
|
||
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.
Comment 12•1 year ago
|
||
(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.
Updated•1 year ago
|
Reporter | ||
Comment 13•1 year ago
|
||
That field says:
Compositing: WebRender
(for all of the three ways of starting Firefox).
Comment 14•1 year ago
|
||
So only Firefox/Snap/X11 is affected, right? That's interesting.
Comment 15•1 year ago
|
||
Who should we talk to in terms of a snap maintainer?
Comment 16•1 year ago
|
||
I think Olivier Tilloy is the right person here.
Comment 17•1 year ago
|
||
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.
Comment 20•1 year ago
|
||
(In reply to Kelsey Gilbert [:jgilbert] from comment #15)
Who should we talk to in terms of a snap maintainer?
what is the question ?
Comment 21•1 year ago
|
||
(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.
Reporter | ||
Comment 22•1 year ago
|
||
(In reply to :gerard-majax from comment #21)
This mentions
core22
fixes, and above all theabout:support
links to versions < 117. With 117 it is built withcore22
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.
Reporter | ||
Comment 24•1 year ago
|
||
Yes, indeed. RESOLVING this as FIXED.
Updated•1 year ago
|
Description
•