Created attachment 227426 [details] v1 (3.36.6) Given -Dnative_backend=false Wayland session currently can only be nested on top of Xorg (any WM) or Sway/Wayfire/hikari/etc (requires Xwayland) or Kwin (kwin_wayland): a Mutter window appears where one can launch other apps. Unlike Xephyr or Xnest the apps within such session still have GPU acceleration. $ pkg install mutter glmark2 vkmark $ ck-launch-session dbus-run-session mutter --wayland & $ export WAYLAND_DISPLAY=$(sockstat -lu | awk '/mutter.*wayland/ { print $6; exit }') $ export DISPLAY=$(sockstat -lu | awk -F/ "/$(pgrep -f mutter-Xwayland)/"' { sub(".*/X", ":"); print; exit }') $ GDK_BACKEND=wayland gtk3-demo & $ GDK_BACKEND=x11 gtk3-demo & $ glmark2-wayland $ glmark2 $ vkmark --winsys wayland $ vkmark --winsys xcb
Ping. Did anyone test?
Created attachment 228353 [details] v1 (41.0)
Created attachment 242599 [details] v1 (42.4) Rebased on top of bug 271823 + bug 271824.
I use your patch with the latest release of mutter (45.2) on GNOME (I have also enabled wayland in various ports), and I noticed, it's always the X11 backend which is used. Even if I "export" several variables: >export XDG_SESSION_TYPE=wayland >export XDG_RUNTIME_DIR=/var/run/user/`id -u` >export WAYLAND_DISPLAY=wayland-0 > ># Set $DESKTOP_SESSION >if test "x$DESKTOP_SESSION" = "x" ; then > #DESKTOP_SESSION="gnome-xorg" > DESKTOP_SESSION="gnome-wayland" >fi The value of variable DESKTOP_SESSION is always "gnome" (like GDMSESSION). I wonder if patch from bug #271836 is required too. Otherwise everything is fine.