Hardware acceleration broken for amdgpu/mesa in snap

Thanks for the report, Bamywasi.

If disabling hardware acceleration managed to fix your issue for Firefox, in Chromium it should work too? The command line would be "chromium --disable-gpu".

Does your KDE runs on Wayland on Xorg? If on Wayland, do you experience the same bug

- with "chromium --ozone-platform=wayland"?
- in Xorg?

Could you please attach the chromium.log file resulting from "chromium --enable-logging --v=1 &> chromium.log"?

Hi Nathan,

Sorry for missing pieces of info in my original report.

I am running KDE/Plasma on Xorg.

And yes, "chromium --disable-gpu" fixes the issue for chromium as well.

I am attaching chromium run log below.

Thank you for reporting back!

 > Sorry for missing pieces of info in my original report.

Don't worry, you even used Apport and provided many useful details.

Apparently, Apport doesn't submit enough information if snapd is its
target. Can you please run

   apport-collect -p chromium-browser 2004532

I think that will give us more information, I'm particularly interested
in dmesg at least.

The journal output after you launch Chromium could also be useful, say:

   journalctl -r | head -n 300 > journal.log

My apologies for not having asked all that at once.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

# attached below, taken with the chromium browser running
$ journalctl -r | head -n 300 >journal.log

Status changed to 'Confirmed' because the bug affects multiple users.

I can confirm this under Gnome as well. Starting a Wayland session, all works fine. Logging in under Xorg results in this graphical issue for both Firefox and Chromium.

Same GPU as the initial reporter, however I am on 22.04 and kernel 5.15.0 (stock HWE).

I also have been affected by this bug.
Firefox browser's gpu acceratation feature is unusable on x11 session.

My GPU:
0b:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] (rev c5)
OS:
Ubuntu 22.04.2 LTS

Given the error message from chromium.log,

> amdgpu: os_same_file_description couldn't determine if two DRM fds reference the same file description.
> If they do, bad things may happen!

I think this might be the kcmp's denial fault.

Can you please execute the following commands to whitelist the syscall[1], restart Chromium and see if the problem persists?

--->
#Append kcmp to the seccomp profile source
sudo sh -c 'echo kcmp >> /var/lib/snapd/seccomp/bpf/snap.chromium.chromium.src'
#Recompile it
sudo /usr/lib/snapd/snap-seccomp compile /var/lib/snapd/seccomp/bpf/snap.chromium.chromium.src /var/lib/snapd/seccomp/bpf/snap.chromium.chromium.bin
#Kill chromium and launch it again
pkill chrom
chromium
<---

If you followed the steps correctly, you shouldn't see the syscall being denied anymore when launching Chromium.

After testing you can revert the change with

--->
sudo sed -i '$d' /var/lib/snapd/seccomp/bpf/snap.chromium.chromium.src
sudo /usr/lib/snapd/snap-seccomp compile /var/lib/snapd/seccomp/bpf/snap.chromium.chromium.src /var/lib/snapd/seccomp/bpf/snap.chromium.chromium.bin
<---

[1] https://snapcraft.io/docs/debug-snaps

On the hardware acceleration front, there has also been recent fixes to AMD GPUs failing to find drivers. It's probably unrelated to the present problem, but if you want to try it anyway, it's on the beta/hwacc channel:

  snap install --channel beta/hwacc chromium

Hi Nathan,

Quick update: I have tried modifying Chromium profile file per your
instructions and indeed this silenced the error message. But it had zero
effect on the GPU bug. I also installed updated kernel which arrived
today and observed no changes either.

$ uname -a
Linux xxxxxx 5.19.0-35-generic #36-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 3
18:36:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

I am less interested in chromium, which I do not normal use, so haven't
tried installing from beta channel yet. But I doubt this would be
different since Firefox shows the same issue with the GPU acceleration
enabled.

Thanks,

Ivan

On 2/24/23 16:11, Nathan Teodosio wrote:
> Given the error message from chromium.log,
>
>> amdgpu: os_same_file_description couldn't determine if two DRM fds reference the same file description.
>> If they do, bad things may happen!
> I think this might be the kcmp's denial fault.
>
> Can you please execute the following commands to whitelist the
> syscall[1], restart Chromium and see if the problem persists?
>
> --->
> #Append kcmp to the seccomp profile source
> sudo sh -c 'echo kcmp >> /var/lib/snapd/seccomp/bpf/snap.chromium.chromium.src'
> #Recompile it
> sudo /usr/lib/snapd/snap-seccomp compile /var/lib/snapd/seccomp/bpf/snap.chromium.chromium.src /var/lib/snapd/seccomp/bpf/snap.chromium.chromium.bin
> #Kill chromium and launch it again
> pkill chrom
> chromium
> <---
>
> If you followed the steps correctly, you shouldn't see the syscall being
> denied anymore when launching Chromium.
>
> After testing you can revert the change with
>
> --->
> sudo sed -i '$d' /var/lib/snapd/seccomp/bpf/snap.chromium.chromium.src
> sudo /usr/lib/snapd/snap-seccomp compile /var/lib/snapd/seccomp/bpf/snap.chromium.chromium.src /var/lib/snapd/seccomp/bpf/snap.chromium.chromium.bin
> <---
>
> [1]https://snapcraft.io/docs/debug-snaps
>
--
Ivan Adzhubey, Ph.D.
Research Associate
Dept of Biomedical Informatics
Harvard Medical School
10 Shattuck Street, Suite 514
Boston, MA 02115
tel: (617) 432-2144
fax: (617) 432-0693
web:http://genetics.bwh.harvard.edu/wiki/sunyaevlab/

Hi Ivan,

Unfortunate that it fixes the error message but not the bug...

Anyway many thanks for your helpfulness going out of your way to give
the test fix a go, that's much appreciated.

I have this issue on Xubuntu 22.04.2 LTS, amdgpu and X11.

Having this as well, Ubuntu 22.04.2 LTS, 5.15.0-1030-gke. Firefox and Chrome rendering garbage.

Maybe this is helpful - a difference I noticed in the output of chromium when run without and with the --disable-gpu flag is that, when run without it there is a log line

amdgpu: os_same_file_description couldn't determine if two DRM fds reference the same file description.

while when run with --disable-gpu this line is not present.

> Maybe this is helpful - a difference I noticed in the output of chromium
> when run without and with the --disable-gpu flag is that, when run
> without it there is a log line
>
> amdgpu: os_same_file_description couldn't determine if two DRM fds
> reference the same file description.
>
> while when run with --disable-gpu this line is not present.

Yes, thanks, but that is a hint I already picked up and suggested fixing
with #31, which in #33 the original reporter confirms that fixes the
denial but nonetheless the problem persists.

Any change the edge channel (in which we have now more up to date libraries) works for you?

  sudo snap refresh --edge chromium

I tried with the edge version and the rendering looks ok now, still some error messages:

~$ chromium-browser &
[1] 634220
 Gtk-Message: 13:45:31.618: Failed to load module "appmenu-gtk-module"
[634220:634220:0420/134531.890979:ERROR:chrome_browser_cloud_management_controller.cc(162)] Cloud management controller initialization aborted as CBCM is not enabled.
/usr/share/libdrm/amdgpu.ids: No such file or directory
amdgpu: os_same_file_description couldn't determine if two DRM fds reference the same file description.
If they do, bad things may happen!
[634220:634497:0420/134535.783796:ERROR:udev_watcher.cc(98)] Failed to begin udev enumeration.

Thanks for testing, that's good news.

CBCM is disabled since the build is not Chrome branded; That diagnostic
message is expected.

Could this be the same bug affecting Firefox and Spotify in Ubuntu 23.04? See https://askubuntu.com/questions/1462899/blurry-distored-unreadable-snap-apps/1464603#1464603

Here is the terminal output when trying to run Spotify:

```bash
sfn@Corsair:~$ spotify
Gtk-Message: 19:10:13.937: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it.
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
amdgpu: os_same_file_description couldn't determine if two DRM fds reference the same file description.
If they do, bad things may happen!
```

https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/2016435
Any chance my problem is related to this (Kubuntu 23.04)? My Firefox crashed constantly.

I also observed the same issue with my KDE Neon (with Pop!_OS's kernel + mesarc from this PPA: https://launchpad.net/~ernstp/+archive/ubuntu/mesarc). The crash only happens if I turn on my parallel-installed Firefox Nightly, and it's very random.

Would this one be related to this problem as well, with Hogwarts Legacy?
https://gitlab.freedesktop.org/mesa/mesa/-/issues/8324

Thanks for the additional data points, that is much appreciated.

I've upgraded to Ubuntu 23.04 (Lunar Lobster), and I'm affected as well, with Mozilla Firefox (from snap), and with Chromium (from snap too).

- chromium --ozone-platform=wayland is a workaround for Chromium
- MOZ_ENABLE_WAYLAND=1 firefox is a workaround for Firefox.

Could this be affecting Telegram too? Look at the line

```
abr 25 09:24:24 Corsair telegram-desktop_telegram-desktop.desktop[2613107]: /usr/share/libdrm/amdgpu.ids: Permission denied
```

here: https://github.com/telegramdesktop/tdesktop/issues/26225

Yann, your screenshots are not accessible to me. For firefox, could you share `about:support` with and without `MOZ_ENABLE_WAYLAND` ?

We have had several reports as well that got duped to https://bugzilla.mozilla.org/show_bug.cgi?id=1828196

This problem should now be solved for Chromium (>=114.0.5735.198). Please confirm or deny it if you are a Chromium user previously affected by this bug.

Hi Nathan,

I can confirm hardware acceleration is now working in Chromium browser
version 114.0.5735.198 (Official Build) snap (64-bit).

Hardware acceleration still DOES NOT work in Firefox version 115.0
(64-bit) Mozilla Firefox snap for Ubuntu canonical-002-1.0.

Using Xorg on Kubuntu 23.04.

Best,

Ivan

On 7/4/23 08:54, Nathan Teodosio wrote:
> This problem should now be solved for Chromium (>=114.0.5735.198).
> Please confirm or deny it if you are a Chromium user previously affected
> by this bug.
>
> ** Description changed:
>
> Possible, proposed solutions
> ----------------------------
>
> Option 1: Please install from these channels and report back with
> success or failure.
>
>   snap refresh --channel candidate/core22 firefox
> -   snap refresh --edge chromium
>
> Option 2:
>
> - chromium --ozone-platform=wayland
> - MOZ_ENABLE_WAYLAND=1 firefox
> +   chromium --ozone-platform=wayland
> +   MOZ_ENABLE_WAYLAND=1 firefox
>
> If nothing works, it is possible around the issue by disabling hardware
> acceleration.
>
> Original bug report
> -------------------
>
> Snap packages which use hardware accelerated graphics are broken after
> the last routine system upgrade via apt. My system is using AMD Radeon
> RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers.
> Two snap packages which are now unusable are Mozilla Firefox and
> Chromium browsers. Both display animated speckled color garbage inside
> their windows, overlayed with the correct image. Disabling hardware
> acceleration in the settings for the snap version of Firefox fixed it.
> Also, Firefox version installed from the original Mozilla tarball into
> /opt/ works just fine with the acceleration enabled on the same system,
> as well as glmark2 benchmark. Looks like the issue is only affecting
> snap packages.
>
> $ snap list firefox chromium
> Name Version Rev Tracking Publisher Notes
> chromium 109.0.5414.119 2295 latest/stable canonical✓ -
> firefox 109.0.1-1 2311 latest/stable mozilla✓ -
>
> $ dpkg -l snapd|grep ^ii
> ii snapd 2.58+22.10 amd64 Daemon and tooling that enable snap packages
>
> $ dpkg -l mesa\* | grep ^ii
> ii mesa-utils 8.5.0-1 amd64 Miscellaneous Mesa utilities -- symlinks
> ii mesa-utils-bin:amd64 8.5.0-1 amd64 Miscellaneous Mesa utilities -- native applications
> ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64 Mesa VA-API video acceleration drivers
> ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64 Mesa VDPAU video acceleration drivers
> ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64 Mesa Vulkan graphics drivers
>
> $ lsb_release -a
> No LSB modules are available.
> Distributor ID: Ubuntu
> Description: Ubuntu 22.10
> Release: 22.10
> Codename: kinetic
>
> $ uname -a
> Linux xxxxxx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
>
> Pr...

Good! Marking it as fixed then, thank you again for reporting back.

Just to confirm: Option 1 works for firefox (in Wayland): `snap refresh --channel candidate/core22 firefox`

"snap refresh --channel candidate/core22 firefox" worked for me.
and I have enabled VAAPI on this firefox successfully.

attached log
$ LIBVA_DRIVER_NAME=radeonsi MOZ_DISABLE_RDD_SANDBOX=1 MOZ_WEBRENDER=1 MOZ_ENABLE_WAYLAND=1 MOZ_LOG="PlatformDecoderModule:5" firefox >& firefox.log

[reference]
https://ubuntuhandbook.org/index.php/2021/08/enable-hardware-video-acceleration-va-api-for-firefox-in-ubuntu-20-04-18-04-higher/
https://www.linux-magazine.com/Issues/2021/243/Firefox-VA-API-Integration

Spotify snap is also broken (see the attached image). I looked into journalctl and found this (look at the line that mentions amdgpu):

abr 21 19:47:47 Corsair audit[43725]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.spotify.spotify pid=43725 comm="spotify" exe="/snap/spotify/64/usr/share/s>
abr 21 19:47:47 Corsair spotify_spotify.desktop[43725]: libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
abr 21 19:47:47 Corsair audit[43725]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.spotify.spotify pid=43725 comm="spotify" exe="/snap/spotify/64/usr/share/s>
abr 21 19:47:47 Corsair spotify_spotify.desktop[43725]: amdgpu: os_same_file_description couldn't determine if two DRM fds reference the same file description.
abr 21 19:47:47 Corsair spotify_spotify.desktop[43725]: If they do, bad things may happen!
abr 21 19:47:47 Corsair audit[43725]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.spotify.spotify pid=43725 comm="spotify" exe="/snap/spotify/64/usr/share/s>
abr 21 19:47:47 Corsair audit[43725]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.spotify.spotify pid=43725 comm="spotify" exe="/snap/spotify/64/usr/share/s>

Santiago, Spotify is proprietary, there is nothing for us to do. You
have to request them to update their base from core20 to core22.
According to 'snap info spotify', their contact link is
https://community.spotify.com/t5/Desktop-Linux/bd-p/desktop_linux.

Marking Firefox as fix released as well since now Firefox is on core22 and that was confirmed in earlier comments to solve the problem. Please reset if observed otherwise.

Ubuntu 22.04.3 LTS
I have AMD integrated graphics. AMD Ryzen 5 7600 6-Core Processor.
I'm using the mesa packages from ppa //ppa.launchpadcontent.net/oibaf/graphics-drivers/ubuntu/
firefox and chromium is completely gibberish rendering. completely unusable.
I tried the different snaps from here. All same jibberish.
If i download firefox from mozilla it works fine.
I haven't found a chromium that works (tried flatpak and different snap channels)
google chrome works fine.
Same in wayland and x.org.

To all MATE-Desktop users: there is not Wayland support.

The only way to execute Firefox and Chromium snaps is by disabling gpu support:

$ firefox --safe-mode
$ chromium --disable-gpu

Or install the packages outside snap. Firefox appimage works.

Is you want to make this permanent on Firefox you can go to about:config and change:

browser.preferences.defaultPerformanceSettings.enabled -> false
layers.acceleration.disabled -> true

And Firefox will start without gpu acceleration (until MATE supports Wayland, I hope).

I thought the whole point of Snap cores is that its supposed to be more resistant to issues like this?

It looks like this regressed in Chromium (probably when Chromium switched to core22) judging by LP:2054887. The fix for the lack of /usr/share/libdrm/amdgpu.ids is currently released on beta and will be soon in other channels too.

This issue affected me as well on Ubuntu 22.04.4, running on a AMD Ryzen 9 7950X3D integrated graphics CPU. Took a late Feb update and it broke. I tried the various snap yaml modifications + snap try with no success. Workaround seems to be to run Firefox does work outside of snap:

https://support.mozilla.org/en-US/kb/install-firefox-linux#w_install-firefox-from-mozilla-builds

I guess only a 32-bit version is being distributed (?), install the 32-bit library dependencies to get this to work: sudo apt install libgtk-3-0.i386 libasound2:i386

Is there any known workaround for the spotify breakage? It has been broken for quite a while now...

For Chromium users:

Can you verify if either of

  snap remove chromium
  snap install --beta chromium

or

  snap remove chromium
  snap install --channel internal-libdrm chromium

fixes the issue?

Note: A refresh will *not* work for the first case, it really needs to be removed and installed back (looks like there is a bug in Snapd).