Comment 31 for bug 2004532

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