Jammy, attempt to log into Xorg session, "Oh no! Something has gone wrong."

[Jonathan Kamens]

On Jammy, I log out of a Wayland session, click my name on the login screen, go down to the options menu and select Ubuntu on Xorg, enter my password, get "Oh no! Something has gone wrong. A probleme has occurred and the system can't recover. Please log out and try again. [Log Out]" I click the log out button and log in again, and I'm logged into a Wayland session. Why was I logged into a Wayland session when I selected Xorg the last time I tried to log in?

This issue is intermittent I had been able to log into an Xorg session just a few minutes prior.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 40.5-1ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
Uname: Linux 5.13.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 28 11:10:10 2021
DisplayManager: gdm3
InstallationDate: Installed on 2019-08-16 (834 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
RelatedPackageVersions: mutter-common 40.5-1ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2021-11-09 (19 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726

[Jonathan Kamens (jik)]

I logged out immediately after logging in again as described above, then went to log in again and checked the options menu, and it correctly had "Ubuntu on Xorg" selected as my session type, but when I finished logging in I was in a Wayland session, not an Xorg session. So for some reason my selection of Xorg as my desired session is being ignored?

[Daniel van Vugt (vanvugt)]

Sounds like bug 1952457 but we should figure out the root cause of this bug separately.

Please:

1. Uninstall these extensions: '<email address hidden>', '<email address hidden>', 'multi-volume@tigersoldier', '<email address hidden>'

2. Log in again and verify the bug still occurs.

3. If the bug does still occur then check for crashes using these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

[Jonathan Kamens (jik)]

Problem still occurs with mprisindicatorbutton, batime, and allowlockedremotedesktop completely uninstalled. Can't uninstall multi-volume because neither Extensions app nor extensions.gnome.org say it's installed.

Probably relevant crash: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1952619

[Jonathan Kamens (jik)]

(Though why _Wayland_ is crashing when I'm trying to log into an _Xorg_ session and the options menu on the login screen says that I have Xorg selected remains a mystery.)

[Daniel van Vugt (vanvugt)]

Please try:

  cd ~/.local/share/gnome-shell/
  rm -rf extensions

and then log in again.

[Daniel van Vugt (vanvugt)]

Sorry I can reproduce it now. Seems logging into Wayland first, and then Xorg, is the trick as you say.

[Daniel van Vugt (vanvugt)]

After removing all extensions I can at least log in to a Xorg session. But you get logged into the Activities Overview as expected. Clicking on the desktop then triggers the "Oh no!" (which is gnome-session-failed?).

So it seems the issue is something to do with the vanilla GNOME desktop. We only see the bug sooner when Ubuntu Dock is loaded because that starts on the desktop.

[Daniel van Vugt (vanvugt)]

Maybe related to bug 1952457.

[Daniel van Vugt (vanvugt)]

Downgrading to gnome-session 40.1.1-1ubuntu1 packages from impish appears to fix it.

https://launchpad.net/ubuntu/+source/gnome-session/40.1.1-1ubuntu1/+build/22096973

so the regression seems to have started in:

https://launchpad.net/ubuntu/+source/gnome-session/40.1.1-3ubuntu1

[Daniel van Vugt (vanvugt)]

If only something was actually crashing or logging errors, I see neither. Just 'gnome-session-failed' gets incorrectly spawned some time after login (when the overview first closes).

[Daniel van Vugt (vanvugt)]

I can't seem to reproduce this bug anymore. If anyone else can then please test:

https://launchpad.net/ubuntu/+source/gdm3/41.0-3ubuntu2/+build/22602610

[Jonathan Kamens (jik)]

No longer reproducible for me.

[Daniel van Vugt (vanvugt)]

More accurately, something in Ubuntu got fixed. Somewhere.