Update on Sep 22, 2021: there’s a bug affecting using Wayland Chrome/Chromium/Electron in the latest Sway/wlroots (i.e., the latest git commit). See https://github.com/swaywm/wlroots/issues/3168 and https://bugs.chromium.org/p/chromium/issues/detail?id=1246834. Before the bug is resolved, either use the released versions of Sway/wlroots, or just wait.
In the past, we may need to use XWayland when using Google Chrome or Chromium under the Wayland environment. But now (as of 01/04/2021), it’s possible to use native Wayland with Google Chrome/Chromium and even electron-based apps if they are installed through the official repository or AUR.
Just launch Google Chrome/Chromium with two additional flags:
or
It’s the same for electron-based apps:
4 Comments
works! thx
it’s amazing.
google chrome fast open with wayland, thank
Why you still have to fuck with additional parameters to run chrome in wayland ?
You probably don’t. The upstream’s roadmap was to make Ozone the default and discard these flags in the second half of 2021, which is now. I don’t know their progress because I don’t use Chrome now. No matter what, older electron-based apps still need these flags until the developers upgrade their Electron.