[Bug 2120413] Re: [SRU]Fix preferred display server has not been retried on start

[Timo Aaltonen]

Hello Zhaoxuan, or anyone else affected,

Accepted gdm3 into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gdm3/46.2-1ubuntu1~24.04.2 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gdm3 (Ubuntu Noble)
       Status: In Progress => Fix Committed

** Tags added: verification-needed-noble

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2120413

Title:
  [SRU]Fix preferred display server has not been retried on start

Status in gdm:
  Fix Released
Status in gdm3 package in Ubuntu:
  Fix Released
Status in gdm3 source package in Jammy:
  In Progress
Status in gdm3 source package in Noble:
  Fix Committed
Status in gdm3 source package in Plucky:
  Fix Released
Status in gdm3 source package in Questing:
  Fix Released

Bug description:
  [ Impact ]

   * On Wayland only devices, when the Wayland display server fails to
     start occasionally, the gdm3 will only retry the unsupported Xorg
     display server instead of Wayland display server.
     The retry mechanism ineffective on these Wayland only devices,
     which in turn causes these devices to be unable to start graphics
     due to an occasional failure.

   * This patch backport from upstream and it will give 5 tries for
     the preferred display server (Wayland on our case).

  [ Test Plan ]

   This patch can be verified on ubuntu Desktop by following these steps:
   * Download attached gdm-crash-test.sh and save it into
     /usr/local/bin/gdm-crash-test.sh
     (This script will emulate a start fail of gdm)
   * Run "chmod +x /usr/local/bin/gdm-crash-test.sh"
   * Edit /usr/share/applications/org.gnome.Shell.desktop.
     Replace the line starts with "Exec=" to:

       Exec=/usr/local/bin/gdm-crash-test.sh
   * Reboot
   * - If this device does not support Xorg display server, you will
       unable to see the Ubuntu login screen.
     - If this device supports Xorg display server, in the Ubuntu login
       screen, you will noticed that Wayland option is unusable.
   * Then, install the test package on system and reboot.
   * With new package, the login screen will show normally, and the wayland
     option is usable.
   
  [ Where problems could occur ]

   * This patch adds 4 extra launch chances for the preferred display server.
     This may increase the delay in gdm selecting a fallback display server
     if the preferred display server is truly completely unavailable.

  [ Other Info ]

   * This patch has just been merged into gdm main branch, and it will be in
     the next gdm release.

   * This bug originally raised by our customer Adventech (LP: #2099664)

   * Upstream Issue: https://gitlab.gnome.org/GNOME/gdm/-/issues/973

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/2120413/+subscriptions