On Aug 11, 2025, mailinglist.skid704@aleeas.com wrote: > On Monday, August 11th, 2025 at 5:27 PM, wanderer@fastmail.fm wrote: > > On 2025-08-11 at 07:23, mailinglist.skid704@aleeas.com wrote: > > [...] > > How are you initiating the shutdown or reboot? > > I am Initiating the shutdown/reboot by going in KDE plasma's > application launcher and clicking on shutdown/reboot > > [...] > > In my case, I shut down by exiting the GUI, logging out in the terminal, > > logging back in as root, and running 'shutdown -h now' or 'shutdown -r > > now'. [...] > > No It appear right after all the GUI stuff is gone but before shutdown. I believe you're seeing remnants of console messages that were sent "behind the scenes" while the system is still busy taking care of other shutdown tasks after the graphical shell is terminated. The message itself is not the cause of the delay, but rather the fact that you see the message is a symptom of some other services that haven't given the all-clear to systemd that they've successfully terminated. I *believe* systemd will wait up to 90 seconds for these processes to close cleanly, before taking more drastic measures (although, it has been quite a while since I've read up on the boot/shutdown processing). Additionally, I believe there is a way you can see the listing of applications receiving these stop signals (similar to the start list when the boot parameters do not include 'quiet splash'); though I can't recall how that is configured. -- |_|O|_| |_|_|O| Github: https://github.com/dpurgert |O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860
Attachment:
signature.asc
Description: PGP signature