PrepareForShutdown() signal from logind is not handled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNOME Shell |
New
|
Unknown
|
|||
gdm |
Fix Released
|
Unknown
|
|||
gdm3 (Ubuntu) |
Invalid
|
Low
|
Unassigned | ||
gnome-shell (Ubuntu) |
Triaged
|
Low
|
Unassigned | ||
unity (Ubuntu) |
Invalid
|
Low
|
Unassigned |
Bug Description
https:/
---
When a user logged in to the GUI session and she/he request shutdown of the system a PrepareForShutd
https:/
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.
Changed in gdm3 (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Low |
Changed in gnome-shell (Ubuntu): | |
importance: | Undecided → Low |
status: | New → Triaged |
Changed in gdm3 (Ubuntu): | |
status: | Triaged → Invalid |
Changed in unity (Ubuntu): | |
importance: | Undecided → Low |
status: | New → Invalid |
Changed in gdm: | |
importance: | Undecided → Unknown |
status: | New → Unknown |
Changed in gdm: | |
status: | Unknown → Fix Released |
Changed in gnome-shell: | |
status: | Unknown → New |
Please report this bug to the GDM developers here:
https:/ /gitlab. gnome.org/ GNOME/gdm/ issues
and then tell us the new bug ID.