All upstream references do seem to point to
https://gitlab.gnome.org/GNOME/gdm/-/issues/733 but the "fix" for that
is already in gdm3 version 41.3 and later. Yet the bug still happens.
Some people are focussed on the cgroup errors that come before it, but I'm not
sure if they're really related:
** Description changed:
I have three accounts and I need all three to run on xorg instead of
wayland.
- For some reason, two of them consistently start wayland even when I
- select plain gnome from the gdm menu. To get xorg, I need to log out and
- log in a second time.
+ For some reason,
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdm3 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
There are not any gdm crash reports in /var/crash. Neither do I find
anything gdm related at https://errors.ubuntu.com/.
In my journalctl log, I do find this:
feb 07 02:29:00 Dapple systemd[53605]: Stopped GNOME Shell on X11.
feb 07 02:29:00 Dapple systemd[53605]: Starting GNOME Shell on X11...
Please check for crashes (which gdm3 is designed to catch and that then
causes the session type to change):
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
In theory you should never see Wayland because you have:
WaylandEnable=false
Although I recall when 22.04 was released, some unpredictability was
observed in the choice of session on Nvidia hybrid (dual GPU) systems.
** Tags added: nvidia
--
You received this bug notification because you
