GITHUB PAGES IS ONLY FOR SEARCH ENGINES! CLICK HERE TO FIND OUT WHY! IF YOU ARE ON CATWITHCODE.MOE ALREADY, YOU MAY BLOCK JS AND THATS WHY YOU SEE THIS. GOOD FOR YOU :).

How to fix a very long Shoutdown Time on OpenSuse/Linux

If your OpenSuse/Linux System takes very long to shutdown there is a thing you could try that fixed it for me in almost all cases.

If your OpenSuse/Linux dose not show what it dose on Boot/Shooutdown, aka. "Quiet boot" you need to temporarily disable it. That's very easy; Reboot your PC, in GRUB press 'E' and try to navigate the cursor to the following and remove it (this can be a little finicky):

splash=silent quiet

This is temporary! Nothing permanent! It will be back to normal after one reboot! Press F10. Now you can see what happens on boot/shoutdown. Boot your Linux, log in, wait a little and then reboot again. Now you see what your System dose, when it hangs on shutdown. If your screen is black just press CTRL+ALT+F1 to F12 to find a screen where it shows the current state. If it says something like the following you found your issue. If it is not that then this guide is over here. Sorry:

A stop job is running for System Logging Service ...

Its the system logging service that has issues closing. To fix it you need to find out what logging Software you use. Boot your PC again and search in your package manager what logging service you have installed. There two common ones: "rsyslog" and "SYSLOG-ng". If you have one of them you need to switch to the other. In OpenSuse you can open yeast and just uninstall the installed software (it will automatically ask you to install the other one). If that's not the case, mark the one to install and the other to uninstall. Pretty much the same an all other distros. After that you need to enable the service. If you have systemD type the following into your terminal (if you have something different you probably know how to do it, if not find out how to do it. If you don't know what you have just look if the systemD is installed in the package manager:

sudo systemctl enable syslog-ng

OR

sudo systemctl enable rsyslog

Depending on what you needed to install.

Now reboot. It should be fixed. At least for me it was. If you are a very low level developer or thinker with a lot very specific and kernel depending stuff this switch could make some things different from now on. Like stuff where you need a kernel log or something. If it causes issues just revert the changes.

That's pretty much it. For me this literally always was and fixed that issue. Hope I could help you. Bye! :)


Sources: