Open hackingguy opened 2 years ago
I also have the same problem when trying to launch vscode (which uses chromium) natively in a wayland session. The --disable-gpu
also fixes the issue for me. I am also running on Manjaro GNOME and I have a dual-AMD laptop (ROG Zephyrus G14). @hackingguy What GPU do you have?
Description
Brave crashes when using in wayland session, it works fine without ozone flags but not able to see brave ads in that case(even custom notifications aren't working). When Ozone flag is used, brave shows following logs and doesn't launch.
Steps to Reproduce
Start brave with
--enable-features=UseOzonePlatform
and--ozone-platform=wayland
flag.Command:
brave --enable-features=UseOzonePlatform --ozone-platform=wayland
Actual result:
Brave crashes showing above logs
Expected result:
Brave should launch with wayland session
Reproduces how often:
Brave never launches when I use these flags, if I use default session, Unable to see brave ads.
Desktop Brave version:
brave version: 1.37.116 (latest) Window Manager: Wayland DE: GNOME 41.1 OS: Manjaro 21.1.2pre
Version/Channel Information:
Miscellaneous Information:
I am able to use it using
--disable-gpu
flag, but its a useless flag as I cannot use hardware accerlation without GPU, so please provide any better workaround.