I'm surprised that: (a) Xwayland is needed on startup. It shouldn't be started in a Wayland session until a legacy app is launched.
(b) g_error ("Failed to start X Wayland: %s", error->message); is fatal. It shouldn't be fatal because of (a), but indeed it apparently still is in the latest mutter source. This is not what I expected, but the source code confirms it. ** Summary changed: - Multiple Xsessions doesn't work + Multiple Wayland sessions doesn't work ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Summary changed: - Multiple Wayland sessions doesn't work + Multiple Wayland sessions doesn't work [Failed to start X Wayland: Wrong ownership for directory "/tmp/.X11-unix"] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972749 Title: Multiple Wayland sessions doesn't work [Failed to start X Wayland: Wrong ownership for directory "/tmp/.X11-unix"] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1972749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs