Hey folks. Have the same issue on my setup on a laptop with hybrid graphics. On jammy and oracular gdm3 is driven by wayland but noble tends to run gdm3 driven by xorg. However in rare cases it was driven by wayland (as intended).
I've made an investigation and realized that udev rules for gdm (/usr/lib/udev/rules.d/61-gdm.rules) are supposed to make some checks in order to choose xorg or wayland as a backend. Ubuntu uses patched rules file. In an upstream version the rules disable wayland once several conditions are met. The conditions are expected to be fulfilled by different udev events. Hence wayland only disabled when all of the required events processed and all of the conditions are persisted (as files in /var/run/udev/). In Ubuntu's version the rules supposed to enable wayland when those conditions are met (indeed rules "doesn't disable wayland" by virtually doing nothing in case as compared to other flow where wayland is disabled). The problem with the patched version is that it makes the check bound to the order of udev events (which is not guaranteed). I.e. on my setup event for nvidia_drm processed prior to other events from i915. As a result the wayland is disabled first when processing nvidia_drm event and then when all conditions are actually met nothing happens. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2062128 Title: Booting with nvidia proprietary drivers 550.67 results in gdm3 being displayed on X11 rather than Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2062128/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
