Thanks Simon,
Ditto.
On Wed, May 1, 2019 at 3:00 PM Simon McVittie 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
Thank you for the great explanation Scott!
I needed to change:
DISPLAY=:2 to connect to wayland-1,
DISPLAY=:1 was connecting to wayland-0
and DISPLAY=:0 to nothing
On Wed, May 1, 2019 at 2:59 PM Scott Anderson
wrote:
>
> On 1/05/19 11:30 pm, Damian Ivanov wrote:
> > Hello,
> >
> > Is it
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
On 1/05/19 11:30 pm, Damian Ivanov wrote:
Hello,
Is it somewhere documented how Xwayland applications are choosing
which compositor to display on? e.g 2 compostiors (1 nested or on
another VT)
wayland-0 and wayland-1
export WAYLAND_DISPLAY=wayland-1
GDK_BACKEND=x11 gedit //starts on wayland-0
Hello,
Is it somewhere documented how Xwayland applications are choosing
which compositor to display on? e.g 2 compostiors (1 nested or on
another VT)
wayland-0 and wayland-1
export WAYLAND_DISPLAY=wayland-1
GDK_BACKEND=x11 gedit //starts on wayland-0
If it's not documented how to do it?
Thank
