Comment # 19 on bug 1184543 from Alynx Zhou

(In reply to Stefan Dirsch from comment #16)
> (In reply to Alynx Zhou from comment #14)
> > See
> > <https://gitlab.gnome.org/GNOME/libgnomekbd/-/blob/master/libgnomekbd/gkbd-
> > keyboard-display.c#L60>, it's a little bit old program and is set to only
> > run in X11 (or XWayland on Wayland), so it won't be a native Wayland client.
> 
> Hmm. Ok. So on a GNOME wayland session we rely on a keyboard configuration
> tool, which only works with X11?
> Wow! Good to know ...


Maybe it can be updated to a native Wayland client, if it does not depends on
any X11 specific APIs.

> > > Also I don't see why a Wayland
> > > session should crash just because of Xwayland is crashing. I would expect
> > > Xclients terminating but nothing more, i.e. not the whole Wayland session."
> > 
> > I think gnome-shell needs to keep a XWayland process running with it for all
> > time now. There will be a XWayland run as needed feature in upstream but not
> > in current version we are using.
> 
> Well, you could restart Xwayland if it would ever crash (losing the
> connected X clients of course), but apparently the desktop is already
> becoming unusable with Xwayland no longer running, so gnome-shell decides to
> just terminate. :-(

It will try to restart XWayland if the experimental feature is enabled, but
it's disabled by default.