I reported the GDM issue upstream, but LP does not handle Gitlab URLs yet: https://gitlab.gnome.org/GNOME/gdm/issues/443
** Description changed: When a user logged in to the GUI session and she/he request shutdown of the system a PrepareForShutdown() signal is emitted by logind: https://www.freedesktop.org/wiki/Software/systemd/inhibit/ Processes holding delay inhibitor locks can start their pre-shutdown operations and until they finish there is no feedback in a Unity session for the logged in user that shutdown is successfully requested on Xenial. On Bionic, the default Gnome 3 session does handle the signal and logs the user off to GDM, but GDM does not tell that shutdown is pending and the user may think that she/he can log in again or should to something to really start the shutdown. With Ubuntu's default configuration the confusion only lasted up to 5 seconds (default max delay for inhibitor locks), but the next upload of unattended-upgrades increases the delay up to 30 seconds which is more than noticeable (LP: #1803137). Please consider either logging the user off from Unity and stopping GDM - to switch over the the plymouth shutdown screen of at least showing a + to switch over the plymouth shutdown screen or at least showing a notification about the ongoing shutdown. ** Also affects: gdm Importance: Undecided Status: New -- 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/1803581 Title: PrepareForShutdown() signal from logind is not handled Status in gdm: New Status in gdm3 package in Ubuntu: Incomplete Status in unity package in Ubuntu: New Bug description: When a user logged in to the GUI session and she/he request shutdown of the system a PrepareForShutdown() signal is emitted by logind: https://www.freedesktop.org/wiki/Software/systemd/inhibit/ Processes holding delay inhibitor locks can start their pre-shutdown operations and until they finish there is no feedback in a Unity session for the logged in user that shutdown is successfully requested on Xenial. On Bionic, the default Gnome 3 session does handle the signal and logs the user off to GDM, but GDM does not tell that shutdown is pending and the user may think that she/he can log in again or should to something to really start the shutdown. With Ubuntu's default configuration the confusion only lasted up to 5 seconds (default max delay for inhibitor locks), but the next upload of unattended-upgrades increases the delay up to 30 seconds which is more than noticeable (LP: #1803137). Please consider either logging the user off from Unity and stopping GDM to switch over the plymouth shutdown screen or at least showing a notification about the ongoing shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1803581/+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
