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: https://www.reddit.com/r/gnome/comments/oknd9c/failed_to_start_application_launched_by/ ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.gnome.org/GNOME/gdm/-/issues #733 https://gitlab.gnome.org/GNOME/gdm/-/issues/733 ** Summary changed: - gdm requires a second login to start xorg session instead of wayland + systemd refuses to start secondary Xorg logins [[email protected]: Skipped due to 'exec-condition'.] ** Changed in: gnome-session (Ubuntu) Status: New => Confirmed ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2006059 Title: systemd refuses to start secondary Xorg logins [[email protected]: Skipped due to 'exec-condition'.] Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I have three accounts and I need all three to run on xorg instead of wayland. For some reason, when switching accounts, 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. A solution that is supposed to work consists in customizing /etc/gdm3/custom.conf (see https://docs.fedoraproject.org/en- US/quick-docs/configuring-xorg-as-default-gnome-session/). This solution does not work. I have also experimented with the following options: DefaultSession=gnome-xorg.desktop and PreferredDisplayServer=xorg Neither appears to set xorg as the default... I have found the following bug reported upstream against gdm: https://gitlab.gnome.org/GNOME/gdm/-/issues/733. It looks like this was fixed a year ago but my system is still affected. Note that I am using the gnome-session package. I doubt whether it makes any difference but I am adding it for the sake of completeness. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9 Uname: Linux 6.0.0-1010-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Sun Feb 5 19:44:53 2023 InstallationDate: Installed on 2022-03-27 (315 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2023-01-30T07:57:48.574915 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2006059/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
