From 2e06bed0e30ac76d03e85f13744253a97624edc2 Mon Sep 17 00:00:00 2001 From: Simon Ser Date: Sun, 18 Aug 2019 22:19:19 +0300 Subject: [PATCH] Updated Running programs natively under Wayland (markdown) --- Running-programs-natively-under-Wayland.md | 10 ++-------- 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/Running-programs-natively-under-Wayland.md b/Running-programs-natively-under-Wayland.md index 345c2f8..c36ef7d 100644 --- a/Running-programs-natively-under-Wayland.md +++ b/Running-programs-natively-under-Wayland.md @@ -4,15 +4,9 @@ You can disable Xwayland (X clients under Wayland) support by specifying `xwayla ## GTK3 -Wayland should be selected by default. If not, this can be overridden on a per-app basis by setting: +Wayland will be selected by default. Do **not** set `GDK_BACKEND=wayland`, it will break apps (e.g. Chromium and Electron). -```shell -# Do not set this globally -GDK_BACKEND=wayland -CLUTTER_BACKEND=wayland -``` - -Setting ```GDK_BACKEND=wayland``` however can still lead to startup crashes with some applications, e.g. chromium (as of Feb. 2019) and electron. **For this reason `GDK_BACKEND` should not be set globally.** +Experimental Wayland support in Firefox can be enabled with `MOZ_ENABLE_WAYLAND=1`. ## Qt5