Press "Enter" to skip to content

Using Google Chrome/Chromium with native Wayland backend in Arch Linux

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:

$ google-chrome-stable --enable-features=UseOzonePlatform --ozone-platform=wayland

or

chromium --enable-features=UseOzonePlatform --ozone-platform=wayland

It’s the same for electron-based apps:

<app executable> --enable-features=UseOzonePlatform --ozone-platform=wayland

4 Comments

  1. Anonymous Anonymous

    works! thx

  2. Luis Luis

    it’s amazing.
    google chrome fast open with wayland, thank

  3. perdak perdak

    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.

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.