Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Google Chrome (wayland ozone) is broken #3783

Closed
ghost opened this issue Dec 2, 2020 · 2 comments
Closed

Google Chrome (wayland ozone) is broken #3783

ghost opened this issue Dec 2, 2020 · 2 comments

Comments

@ghost
Copy link

ghost commented Dec 2, 2020

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.

@rusty-snake
Copy link
Collaborator

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

@rusty-snake
Copy link
Collaborator

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 up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant