A workaround to this problem is to reduce this timeout in
/etc/systemd/system.conf down from 90s to for example 10s:
and run the following command in terminal after making changes
$ systemctl daemon-reload
This problem can have many causes, so specific answers don’t work too well. Try this for troubleshooting:
- wait for the “A stop job is running for Session c2 …” message to appear on shutdown and reboot after shutdown has completed
journalctl -p5in a terminal and press
ENDto get to the end of the systemd journal (
-p5filters out a lot of garbage)
- start a search by pressing
/and enter the search term
timed out. Killing.
- search backwards by pressing
- the line below each match tells you which application was misbehaving:
Killing process 1234 (jack_thru) with signal SIGKILL.
If it is always the same application, you want to find out what it does and why it isn’t stopped at shutdown. Otherwise it could be more complicated to solve the problem, but you might still get a hint or two.
Good luck! 🙂
I had the same problem, searching I found a post in a reddit forum of Arch Linux.
Here is the solution that works for me
# pacman -S watchdog
And then start the service at boot:
# systemctl enable watchdog.service
Start the service to don’t see the message any more
# systemctl start watchdog.service
I create a gist for this https://gist.github.com/dianjuar/98d02af4050dc2df8ae6f18695d44ca3