Public bug reported: Summary Shutdown/reboot hung after installing updates, and I had to hold down the physical power button to turn the laptop off. This is a system shutdown hang, not just a Slack application crash. The final journal messages do not establish that the machine actually restarted.
System - Ubuntu 26.04.1 LTS (resolute), amd64 - MSI Stealth GS66 12UGS / MS-16V5 - Encrypted root with device-mapper crypt and LVM - Kernel: 7.0.0-38-generic; Ubuntu version signature 7.0.0-38.38-generic 7.0.14 - dracut and dracut-core: 110-11ubuntu0.1 - systemd, udev and systemd-cryptsetup: 259.9-0ubuntu0.1 - Intel Alder Lake-P Iris Xe (i915) and NVIDIA RTX 3070 Ti Laptop GPU; nvidia-driver-595-open 595.99.02-0ubuntu0.26.04.1 - molly-guard is not installed; no reboot/poweroff command diversions were reported by dpkg-divert. Steps / observed incident 1. Install the normal available updates. 2. Request a reboot from the running desktop. 3. The system begins shutting down but does not complete the restart. 4. Recover by holding down the power button, then boot again. Expected The system completes shutdown and restarts without requiring a forced power-off. Actual / impact The machine remains stuck during shutdown and requires a physical forced power-off. Exact recurrence rate and the final on-screen message have not been captured. This report documents one investigated incident; no forced-shutdown reproduction was attempted during diagnosis. Update timeline On 2026-10-26 at approximately 08:48:53-08:49:17 (UTC-07:00), systemd/udev/systemd-cryptsetup were upgraded from 259.5-0ubuntu3.4 to 259.9-0ubuntu0.1, along with Mutter 50.1-0ubuntu2.4 to 50.1-0ubuntu2.5 and other desktop packages. The dracut trigger completed at 08:49:15 and regenerated the boot image. The running kernel did not change in this transaction: 7.0.0-38.38 had been installed on October 5. Temporal association is not proof that these updates caused the hang. A subsequent dpkg --audit produced no output. Shutdown journal evidence (2026-10-26, UTC-07:00; hostname omitted) 13:39:47 systemd-logind: The system will reboot now! 13:39:48 systemd-logind: System is rebooting. 13:39:50 systemd: Stopped dracut-shutdown.service - Restore /run/initramfs on shutdown. 13:40:05 systemd-cryptsetup: Device dm_crypt-0 is still in use. 13:40:05 systemd-cryptsetup: Failed to deactivate 'dm_crypt-0': Device or resource busy 13:40:05 systemd: systemd-cryptsetup@dm_crypt-0.service: Control process exited, code=exited, status=1/FAILURE 13:40:12 systemd: Reached target shutdown.target - System Shutdown. 13:40:12 systemd: Finished systemd-reboot.service - System Reboot. 13:40:12 systemd: Reached target reboot.target - System Reboot. 13:40:12 systemd: Shutting down. 13:40:12 systemd-shutdown: Syncing filesystems and block devices. 13:40:12 systemd-shutdown: Sending SIGTERM to remaining processes... 13:40:12 systemd-journald: Received SIGTERM from PID 1 (systemd-shutdow). 13:40:12 systemd-journald: Journal stopped The journal ends there. Reaching reboot.target and stopping journald do not prove the later dracut/kernel/firmware shutdown completed. No panic or fatal lockup signature was captured in the retained shutdown journal. No kernel crash dump was present in /var/crash; the next boot's systemd- pstore service was skipped because persistent storage was empty. Caveats / other shutdown events - The same dm_crypt-0 busy-deactivation error appears in the October 19 and October 21 shutdown logs, so it is not a new error or sufficient proof of this hang's cause. - GNOME Shell and the user session hit stop timeouts but shutdown progressed beyond them. - NVIDIA persistence/power daemons stopped successfully; that does not prove the NVIDIA kernel driver completed later device teardown. - Slack generated a SIGTRAP crash report during desktop teardown. There is no established causal link between that application crash and the system-level shutdown hang. - Reading the active boot image and privileged late-shutdown artifacts was not possible without administrator authentication. There is no late-shutdown console capture or rdsosreport for this incident. Related report https://bugs.launchpad.net/bugs/2147476 describes a dracut shutdown/reboot failure with encrypted storage and forced power-off. It is a related lead, not a confirmed duplicate. In particular, molly-guard-related comments in that report do not match this machine. Initial component selection Filed against dracut for initial triage because the system uses its late-shutdown environment and the related report has similar symptoms. The actual failing component is not established; please reassign to systemd or linux if later diagnostics support that. A separate bug covers the boot-time disk-unlock prompt refreshing and clearing password input. Separate report from this investigation (no shared cause established): https://bugs.launchpad.net/bugs/2172254 ** Affects: dracut (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 resolute ** Description changed: Summary Shutdown/reboot hung after installing updates, and I had to hold down the physical power button to turn the laptop off. This is a system shutdown hang, not just a Slack application crash. The final journal messages do not establish that the machine actually restarted. System - Ubuntu 26.04.1 LTS (resolute), amd64 - MSI Stealth GS66 12UGS / MS-16V5 - Encrypted root with device-mapper crypt and LVM - Kernel: 7.0.0-38-generic; Ubuntu version signature 7.0.0-38.38-generic 7.0.14 - dracut and dracut-core: 110-11ubuntu0.1 - systemd, udev and systemd-cryptsetup: 259.9-0ubuntu0.1 - Intel Alder Lake-P Iris Xe (i915) and NVIDIA RTX 3070 Ti Laptop GPU; nvidia-driver-595-open 595.99.02-0ubuntu0.26.04.1 - molly-guard is not installed; no reboot/poweroff command diversions were reported by dpkg-divert. Steps / observed incident 1. Install the normal available updates. 2. Request a reboot from the running desktop. 3. The system begins shutting down but does not complete the restart. 4. Recover by holding down the power button, then boot again. Expected The system completes shutdown and restarts without requiring a forced power-off. Actual / impact The machine remains stuck during shutdown and requires a physical forced power-off. Exact recurrence rate and the final on-screen message have not been captured. This report documents one investigated incident; no forced-shutdown reproduction was attempted during diagnosis. Update timeline On 2026-10-26 at approximately 08:48:53-08:49:17 (UTC-07:00), systemd/udev/systemd-cryptsetup were upgraded from 259.5-0ubuntu3.4 to 259.9-0ubuntu0.1, along with Mutter 50.1-0ubuntu2.4 to 50.1-0ubuntu2.5 and other desktop packages. The dracut trigger completed at 08:49:15 and regenerated the boot image. The running kernel did not change in this transaction: 7.0.0-38.38 had been installed on October 5. Temporal association is not proof that these updates caused the hang. A subsequent dpkg --audit produced no output. Shutdown journal evidence (2026-10-26, UTC-07:00; hostname omitted) 13:39:47 systemd-logind: The system will reboot now! 13:39:48 systemd-logind: System is rebooting. 13:39:50 systemd: Stopped dracut-shutdown.service - Restore /run/initramfs on shutdown. 13:40:05 systemd-cryptsetup: Device dm_crypt-0 is still in use. 13:40:05 systemd-cryptsetup: Failed to deactivate 'dm_crypt-0': Device or resource busy 13:40:05 systemd: systemd-cryptsetup@dm_crypt-0.service: Control process exited, code=exited, status=1/FAILURE 13:40:12 systemd: Reached target shutdown.target - System Shutdown. 13:40:12 systemd: Finished systemd-reboot.service - System Reboot. 13:40:12 systemd: Reached target reboot.target - System Reboot. 13:40:12 systemd: Shutting down. 13:40:12 systemd-shutdown: Syncing filesystems and block devices. 13:40:12 systemd-shutdown: Sending SIGTERM to remaining processes... 13:40:12 systemd-journald: Received SIGTERM from PID 1 (systemd-shutdow). 13:40:12 systemd-journald: Journal stopped The journal ends there. Reaching reboot.target and stopping journald do not prove the later dracut/kernel/firmware shutdown completed. No panic or fatal lockup signature was captured in the retained shutdown journal. No kernel crash dump was present in /var/crash; the next boot's systemd- pstore service was skipped because persistent storage was empty. Caveats / other shutdown events - The same dm_crypt-0 busy-deactivation error appears in the October 19 and October 21 shutdown logs, so it is not a new error or sufficient proof of this hang's cause. - GNOME Shell and the user session hit stop timeouts but shutdown progressed beyond them. - NVIDIA persistence/power daemons stopped successfully; that does not prove the NVIDIA kernel driver completed later device teardown. - Slack generated a SIGTRAP crash report during desktop teardown. There is no established causal link between that application crash and the system-level shutdown hang. - Reading the active boot image and privileged late-shutdown artifacts was not possible without administrator authentication. There is no late-shutdown console capture or rdsosreport for this incident. Related report https://bugs.launchpad.net/bugs/2147476 describes a dracut shutdown/reboot failure with encrypted storage and forced power-off. It is a related lead, not a confirmed duplicate. In particular, molly-guard-related comments in that report do not match this machine. Initial component selection Filed against dracut for initial triage because the system uses its late-shutdown environment and the related report has similar symptoms. The actual failing component is not established; please reassign to systemd or linux if later diagnostics support that. A separate bug covers the boot-time disk-unlock prompt refreshing and clearing password input. + + Separate report from this investigation (no shared cause established): + https://bugs.launchpad.net/bugs/2172254 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2172253 Title: Shutdown/reboot hangs after updates and requires forced power-off on MSI GS66 with encrypted root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2172253/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
