gnome-shell fails to start without XWayland, using the --no-x11 switch.
Arch Linux
gnome-shell 3.30.0+37+g969eecb8-1
xorg-server-xwayland 1.20.1-1
linux 4.18.11.arch1-1
Intel Core2 Quad CPU Q6600
ATI Radeon HD 5570 - REDWOOD (DRM 2.50.0 / 4.18.11-arch1-1-ARCH, LLVM 7.0.0) - three screens
glibc 2.28-4
Running "gnome-shell --wayland --display-server --no-x11", gnome-shell fails to start. Collecting the error messages with "tee" gives:
dri_create_context: requested glthread but driver is missing backgroundCallable V2 extension dri_create_context: requested glthread but driver is missing backgroundCallable V2 extension Window manager warning: Failed to set environment variable WAYLAND_DISPLAY for gnome-session: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.SessionManager" does not exist (gnome-shell:15048): GLib-GObject-CRITICAL **: 09:55:54.459: g_object_get_data: assertion 'G_IS_OBJECT (object)' failed (gnome-shell:15048): Gdk-CRITICAL **: 09:55:54.459: gdk_screen_get_display: assertion 'GDK_IS_SCREEN (screen)' failed (gnome-shell:15048): Gdk-CRITICAL **: 09:55:54.459: gdk_display_get_name: assertion 'GDK_IS_DISPLAY (display)' failed (gnome-shell:15048): Gdk-CRITICAL **: 09:55:54.459: gdk_screen_get_number: assertion 'GDK_IS_SCREEN (screen)' failed (gnome-shell:15048): Gtk-CRITICAL **: 09:55:54.460: gtk_settings_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed (gnome-shell:15048): GLib-GObject-CRITICAL **: 09:55:54.460: g_object_set_data_full: assertion 'G_IS_OBJECT (object)' failed
Running "gdb gnome-shell" and "run --wayland --display-server --no-x11" will lock-out the mouse and keyboard inputs with gnome-shell still running. A remote login is required to kill gnome-shell, and no back-trace remains.
Is running gnome-shell without XWayland possible?