[GH-ISSUE #3783] google-chrome: hardware acceleration is broken (intel/wayland ozone) (seccomp) #2384

Closed
opened 2026-05-05 09:03:50 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @ghost on GitHub (Dec 2, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3783

Fedora 33 on Haswell CPU & iGPU

Compiled form master today (last done over a month ago) and google chrome is broken, videos aren't played correctly and desync from audio.

noprofile fixes the problem.

The command used:

firejail --disable-mnt --netns=custom --dns=1.1.1.1 --private=~/jailed/google_chrome google-chrome-stable --disable-webgl --enable-features=UseOzonePlatform --ozone-platform=wayland

Prior to the recompilation today it worked fine.

Originally created by @ghost on GitHub (Dec 2, 2020). Original GitHub issue: https://github.com/netblue30/firejail/issues/3783 Fedora 33 on Haswell CPU & iGPU Compiled form master today (last done over a month ago) and google chrome is broken, videos aren't played correctly and desync from audio. noprofile fixes the problem. The command used: `firejail --disable-mnt --netns=custom --dns=1.1.1.1 --private=~/jailed/google_chrome google-chrome-stable --disable-webgl --enable-features=UseOzonePlatform --ozone-platform=wayland ` Prior to the recompilation today it worked fine.
gitea-mirror 2026-05-05 09:03:50 -06:00
  • closed this issue
  • added the
    graphics
    label
Author
Owner

@rusty-snake commented on GitHub (Dec 2, 2020):

Likely a regression from 594300374d. However, the only effective change for google-chrome.profile was private-cache 😕 .

<!-- gh-comment-id:737151634 --> @rusty-snake commented on GitHub (Dec 2, 2020): Likely a regression from 594300374dc15bd704bcb1f2a98b17faef80aa79. However, the only effective change for google-chrome.profile was private-cache :confused: .
Author
Owner

@rusty-snake commented on GitHub (Jan 4, 2021):

I played a bit with ozone in brave, chromium-browser-privacy and vivaldi. AV worked fine in brave. However, I needed to allow the kcmp syscall (I set seccomp-error-action kill). Works firejail '--seccomp=!chroot,!kcmp' …?

For the record: Fedora 32; Mesa 20.2.3; Intel GPU; secomp.drop kcmp is only violated when using ozone, but not with the default X11 backend.

<!-- gh-comment-id:753980748 --> @rusty-snake commented on GitHub (Jan 4, 2021): I played a bit with ozone in brave, chromium-browser-privacy and vivaldi. AV worked fine in brave. However, I needed to allow the kcmp syscall (I set `seccomp-error-action kill`). Works `firejail '--seccomp=!chroot,!kcmp' …`? For the record: Fedora 32; Mesa 20.2.3; Intel GPU; `secomp.drop kcmp` is only violated when using ozone, but not with the default X11 backend.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#2384
No description provided.