Logs in with Wayland although Xorg looks selected in session menu. Need to reselect

[Mario Vukelic]

After upgrade to Impish.

1. Log in with Xorg session
2. Log out
3. Check gdm session menu > Xorg is displayed as selected
4. Log in > Wayland is running
5. Log out
6. Check gdm session menu > Xorg is displayed as selected
7. Choose Xorg again anyway
8. Log in
9. Success. Xorg is running

Reproduces every time for me. Despite Xorg always showing as selected, it uses Wayland unless I click the Xorg session again

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: gdm3 41~rc-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 24 21:05:34 2021
InstallationDate: Installed on 2018-09-13 (1106 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)
SourcePackage: gdm3
UpgradeStatus: Upgraded to impish on 2021-09-24 (0 days ago)

[Daniel van Vugt (vanvugt)]

Thanks for the bug report. After reproducing the bug again please run:

  journalctl -b0 > journal.txt

and then attach the resulting text file here.

Please also follow these instructions to check for crashes: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

[Stephen Cofer (stephendcofer70)]

Also seeing this issue. No crashes shown. Boot session is three (3) logins, all three with the selector set to Xorg -- the first one logs in with Gnome Wayland session, the second with Xorg, and the third with Wayland again.

This is a fresh Impish (Ubuntu 21.10) install, not an upgrade with no custom core components, updated to latest packages.

[Daniel van Vugt (vanvugt)]

I've noticed this in lots of impish bug reports. Not sure if it indicates a bug but sure looks suspicious:

Oct 07 19:13:03 sdcpc systemd[1363]: Starting GNOME Shell on Wayland...
Oct 07 19:13:03 sdcpc systemd[1363]: Starting GNOME Shell on X11...
Oct 07 19:13:03 sdcpc systemd[1363]: app-gnome-gnome\x2dkeyring\x2dpkcs11-1484.scope: Deactivated successfully.
Oct 07 19:13:03 sdcpc systemd[1363]: <email address hidden>: Control process exited, code=exited, status=2/INVALIDARGUMENT
Oct 07 19:13:03 sdcpc systemd[1363]: <email address hidden>: Skipped due to 'exec-condition'.
Oct 07 19:13:03 sdcpc systemd[1363]: Condition check resulted in GNOME Shell on X11 being skipped.
Oct 07 19:13:03 sdcpc systemd[1363]: app-gnome-gnome\x2dkeyring\x2dsecrets-1488.scope: Deactivated successfully.
Oct 07 19:13:03 sdcpc systemd[1363]: <email address hidden>: Scheduled restart job, restart counter is at 1.
Oct 07 19:13:03 sdcpc systemd[1363]: Stopped GNOME Shell on X11.
...

[Daniel van Vugt (vanvugt)]

Since this is Mario's bug, we're still incomplete waiting on comment #2.

[Stephen Cofer (stephendcofer70)]

So you're going to abandon even worrying about it just because the original bug reporter -- who could have given up, gone to another distro or even another OS at this point -- hasn't replied?

And people wonder why I don't report bugs.

[Daniel van Vugt (vanvugt)]

This bug is not abandoned.

Since we frequently have the issue of people commenting on other peoples' bugs with information that's not relevant to the original reporter, we would still like information from the original reporter to be sure the root causes are the same for everyone.

[Stephen Cofer (stephendcofer70)]

The question is, though, have you *tried* to recreate the bug? A small period of time logging in/out and trying to select Xorg, then seeing what's running when you're logged in might give you some clue that it might just be a universal problem that can be fixed is all that's required here. Do you really need all of this bureaucracy and MBs upon MBs of logs just to find out something might not have gotten set correctly on login and you have to specifically select an option to get it to set correctly?

As a developer, the *first thing I do* when someone says there might be a bug is to *try it myself*, not ask for a mountain of new information before even acknowledging there might be something wrong. But in all modern bug report systems, this bureaucratic nonsense seems to be the norm instead of actually caring about your product enough to take a moment out of your day to actually see if it might be a problem.

[Mario Vukelic (kreuzsakra)]

Reproduced again:
1. Logged out from Xorg session
2. Logged in again with default of Xorg selected, it logs into Wayland
3. Logged out once more and clicked the selected Xorg menu entry again.
4. Logged back in - now into Xorg.
5. Created the attached journal.txt.

There are no crash reports in /var/crash and nothing relevant on the whoopsie website for my ID, the last one there is from June before upgrade and different anyway.

If I understand it right I don't have to do the apport workaround thing as this is not a stable release. Let me know if otherwise pls.

Sorry that my tardiness caused unhappiness, I was just busy and not abandoning Ubuntu after 15 years due to a minor bug in a beta :)

[Jean-Baptiste Lallement (jibel)]

I've this issue too. What else do you need than @Mario's journal?

[Launchpad Janitor (janitor)]

This bug was fixed in the package gdm3 - 41~rc-0ubuntu2

---------------
gdm3 (41~rc-0ubuntu2) impish; urgency=medium

  * debian/patches/git_select_session.patch:
    - backport an upstream fix for gdm sometime starting the wrong
      session type and not respecting the user selection (lp: #1945008)

 -- Sebastien Bacher <email address hidden> Tue, 12 Oct 2021 11:05:27 +0200