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
(/u
Here is a proposed patch. It changes the action when all the conditions
are met from "do nothing" to "prefer wayland". Hence even if nvidia_drm
event was processed first and opted to "prefer xorg", further processing
of events will override the preference.
** Patch added: "61-gdm.rules.patch"
reuploaded patch
** Patch removed: "61-gdm.rules.patch"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2062128/+attachment/5831592/+files/61-gdm.rules.patch
** Patch added: "61-gdm.rules.patch"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2062128/+attachment/5831595/+files/61-
Sad to know cause in my case Wayland experience seems to be more smooth than
Xorg one.
Anyway thanks for the review and provided details.
--
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/
