** Changed in: gdm
Status: Unknown => Fix Released
** Changed in: gnome-shell
Status: Unknown => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1803581
Title:
PrepareForShutdown() signal from logind is not handled
Status in gdm:
Fix Released
Status in GNOME Shell:
New
Status in gdm3 package in Ubuntu:
Invalid
Status in gnome-shell package in Ubuntu:
Triaged
Status in unity package in Ubuntu:
Invalid
Bug description:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/787
---
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
