** This bug is no longer a duplicate of bug 2069564
   [SRU] gnome-shell crashed with SIGTRAP in meta_wayland_compositor_new() from 
meta_context_start() from main() ["Failed to start X Wayland: Directory 
\"/tmp/.X11-unix\" is not writable"]

** Description changed:

+ [ Impact ]
+ 
+ The fix for bug 2120413 was supposed to retry the preferred display
+ server option (generally Wayland) before falling back to another option
+ (generally Xorg).
+ 
+ After the update however, gdm is seen retrying Wayland forever instead and 
never falling back to Xorg.
+ This only happens when auto-login is enabled. With auto-login disabled 
instead, GDM correctly falls back to Xorg after 5 retries of Wayland.
+ 
+ The bug is Invalid for questing and newer, because there is no Xorg
+ session to fall back to, as there's only Wayland.
+ 
+ Evidence:
+ 
+ * no auto-login:
+ 
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2129777/+attachment/5920253/+files/journal-
+ last-gdm3-version-no-autologin.txt
+ 
+ * auto-login:
+ 
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2129777/+attachment/5920254/+files/journal-
+ last-gdm3-version-autologin.txt
+ 
+ [ Test Plan ]
+ 
+ TBD
+ 
+ [ Where problems could occur ]
+ 
+ TBD
+ 
+ [ Original bug report ]
+ 
  Hello,
  
  This issue is probably linked to bug #2128840, but in my case,
  MUTTER_DEBUG_FORCE_EGL_STREAM env var is not set.
  
  In short, upgrading to gdm3 46.2-1ubuntu1~24.04.3 and rebooting, caused
  the desktop could not be reached: black screen only. Removing the
  Automatic Login entries from /etc/gdm3/custom.conf and rebooting fixed
  the issue. Downgrading to the previous version (46.2-1ubuntu1~24.04.1)
  also fixed the issue.
  
  System info will be shared in the next comment(s).
  
  Note: the issue is visible on a laptop I don't own, and I don't easily
  have access. I tried to provide as much data as I could, but "quick
  tests" might be difficult.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gdm3 46.2-1ubuntu1~24.04.3
  ProcVersionSignature: Ubuntu 6.8.0-86.87-generic 6.8.12
  Uname: Linux 6.8.0-86-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.8
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 24 19:29:50 2025
  InstallationDate: Installed on 2021-11-23 (1431 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2025-10-24T19:28:32.230086

** Also affects: gdm3 (Ubuntu Questing)
   Importance: Undecided
       Status: New

** Also affects: gdm3 (Ubuntu Noble)
   Importance: Undecided
       Status: New

** Also affects: gdm3 (Ubuntu Plucky)
   Importance: Undecided
       Status: New

** Changed in: gdm3 (Ubuntu Questing)
       Status: New => Invalid

** Changed in: gdm3 (Ubuntu)
       Status: New => Invalid

** Changed in: gdm3 (Ubuntu Noble)
       Status: New => Triaged

** Changed in: gdm3 (Ubuntu Plucky)
       Status: New => Triaged

** Tags added: udeng-8453

-- 
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/2129777

Title:
  Automatic Login with latest gdm3 is broken if Wayland doesn't work

Status in gdm3 package in Ubuntu:
  Invalid
Status in gdm3 source package in Noble:
  Triaged
Status in gdm3 source package in Plucky:
  Triaged
Status in gdm3 source package in Questing:
  Invalid

Bug description:
  [ Impact ]

  The fix for bug 2120413 was supposed to retry the preferred display
  server option (generally Wayland) before falling back to another
  option (generally Xorg).

  After the update however, gdm is seen retrying Wayland forever instead and 
never falling back to Xorg.
  This only happens when auto-login is enabled. With auto-login disabled 
instead, GDM correctly falls back to Xorg after 5 retries of Wayland.

  Evidence:

  * no auto-login:
  
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2129777/+attachment/5920253/+files/journal-
  last-gdm3-version-no-autologin.txt

  * auto-login:
  
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2129777/+attachment/5920254/+files/journal-
  last-gdm3-version-autologin.txt

  [ Test Plan ]

  TBD

  [ Where problems could occur ]

  TBD

  [ Other info ]

  The bug is Invalid for questing and newer, because there is no Xorg
  session to fall back to, as there's only Wayland.

  [ Original bug report ]

  Hello,

  This issue is probably linked to bug #2128840, but in my case,
  MUTTER_DEBUG_FORCE_EGL_STREAM env var is not set.

  In short, upgrading to gdm3 46.2-1ubuntu1~24.04.3 and rebooting,
  caused the desktop could not be reached: black screen only. Removing
  the Automatic Login entries from /etc/gdm3/custom.conf and rebooting
  fixed the issue. Downgrading to the previous version
  (46.2-1ubuntu1~24.04.1) also fixed the issue.

  System info will be shared in the next comment(s).

  Note: the issue is visible on a laptop I don't own, and I don't easily
  have access. I tried to provide as much data as I could, but "quick
  tests" might be difficult.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gdm3 46.2-1ubuntu1~24.04.3
  ProcVersionSignature: Ubuntu 6.8.0-86.87-generic 6.8.12
  Uname: Linux 6.8.0-86-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.8
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 24 19:29:50 2025
  InstallationDate: Installed on 2021-11-23 (1431 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2025-10-24T19:28:32.230086

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2129777/+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

Reply via email to