xwayland display variable

Damian Ivanov damianatorrpm at gmail.com
Wed May 1 12:18:24 UTC 2019

Thanks Simon,

On Wed, May 1, 2019 at 3:00 PM Simon McVittie <smcv at collabora.com> wrote:
> On Wed, 01 May 2019 at 14:30:52 +0300, Damian Ivanov wrote:
> > export WAYLAND_DISPLAY=wayland-1
> > GDK_BACKEND=x11 gedit //starts on wayland-0
> If you are using GDK_BACKEND=x11, then gedit is not acting as a native
> Wayland app, so it will not look at WAYLAND_DISPLAY. Instead, it will be
> acting as an X11 app, which obeys the traditional X11 DISPLAY environment
> variable (and in your case it happens to connect to an Xwayland instance
> that is already associated with one of the Wayland displays, but the X11
> backend in GTK has no knowledge of Wayland, so it can't know that).
> If you want an application to appear on one of your Wayland displays,
> irrespective of whether that application is using native Wayland or
> X11 via Xwayland, then you need to put a matching pair of WAYLAND_DISPLAY
> and DISPLAY in its environment.
> Alternatively, if you let gedit use native Wayland (stop using
> GDK_BACKEND=x11) it will respect WAYLAND_DISPLAY.
>     smcv
> _______________________________________________
> wayland-devel mailing list
> wayland-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/wayland-devel

More information about the wayland-devel mailing list