Computer takes forever to shut down (unless I restart before shutting down).

SedDeSangre

I assume it's because some program isn't closing. Really annoying to have to restart every time I want to shut down.

ender

I have the same problem, on one of my laptop.

Brucehankins

I started noticing the same thing yesterday. I had swapped a new drive into my machine to install an OS on before this though.

prateekmedia

Happens sometimes to me also in my fresh installation of budgie, I have to force shutdown it.

brent

this was common for me a while and ufw (firewall) was the culprit. Evidence: dmesg and plymouth shutdown screen.
ufw interrupted the shutdown because it hadn't resolved ingoing/outgoing requests. That's at least my interpretation. Something resolved itself eventually b/c it don't happen anymore.
If you have no ufw then disregard my 2 cents.

elfprince

brent Interesting observation. I run ufw always. I too experienced occasional slow shutdown time (using Budgie). I always wait it out so the processes have time to shutdown nicely, and not with a 'kick in the butt'. Lately I've tried running Solus with Openbox and just shutting down from terminal via sudo poweroff. It is pretty instant. No lightdm. 😀

brent

elfprince I have really come to trust ufw a lot on its simple default setting. Yes, something wants to call in, and something wants to call out, and I used to "just wait it out" exactly. (openbox is on my experiment list--hope you like it).
sudo poweroff I've never tried--the lightdm bypass is interesting. thanks for that info. I wonder if it would over-ride ufw?
Because in these instances killall sometimes didn't work but I admit I wasn't always sure what I was tring to kill...🙂

elfprince

brent I checked man poweroff, and I believe that this command sends the kill signal to all processes, in a nice way, including ufw. ie not 'kick in the butt'.

brent

elfprince appreciate checking the man page. I should more! I liked poweroff is gentle that way. The kick in the butt method is never foolproof🙂 and I used to be so impatient I did an occasional hard shutdown (push button, cross fingers). When you buy another computer, you try to watch that stuff..

elfprince

brent I only push buttons when all else fails, ie when computer is locked up by a process or smtg. 😀

sangheeta

I also noticed that Solus was stuck on a black screen saying "watchdog....." . By pressing Ctrl+Shift+Del, other indications appeared but I don't remember, it was other stuck processes.

Then I realized that it happened just after I had done some operations. Now I leave Solus alone for a few minutes before turning off my laptop and since then I don't have this problem anymore. But if I try to turn it off right after an update, or a copy of a file on a usb stick etc, chances are that my screen will stuck again on shut down.

elfprince

sangheeta Interesting. I never had any watchdogs or cats on my screen. Just a flashing cursor until the power is off.

brent

Brucehankins sangheeta elfprince
also used to have that watchdog delay as well. all my research about it seemed really vague but watchdog is a kernel function triggered by something, I don't remember. never got the impression it was bad news just some weird hiccup.

Brucehankins

elfprince mine sticks on the HP splash screen (HP motherboard) sometimes for 10-15 minutes. Then I'll see a quick message about watchdog and it shuts down. I'll try through the terminal next time. I did notice sudo reboot is almost instantaneous.

just

What is watchdog - a bit of background (very simplified, can't remember the exact mechanism).

When shutting down, systemd by default sets a watchdog timeout of 10 minutes, then closes the watchdog before executing systemd-shutdown. If systemd did not stop the watchdog, Linux warns a user. This has the effect that if shutdown is not completed within 10 minutes, the hardware watchdog will trigger the specified action. Which is usually shutdown.

How to disable 10 minutes watchdog timer.

edit /etc/systemd/system.conf

uncomment 2 lines:

#RuntimeWatchdogSec=0
#ShutdownWatchdogSec=10min

leave RuntimeWatchdogSec at 0
set ShutdownWatchdogSec to 0

like this:

RuntimeWatchdogSec=0
ShutdownWatchdogSec=0

reboot
done

Brucehankins

just this worked perfectly for me!