A solution to "A stop job running for user manager uid 1000" when a program doesn't close itself properly?

General system Newbie
1

I occasionally have a game fail to close itself properly, and then when I restart or turn off my desktop, I get the error from the title.

I’ve looked around and the only time I’ve seen a solution was someone mentioning you can add ‘nowatchdog’ to the kernel parameters.

I’ve looked at Arch Wiki: https://wiki.archlinux.org/title/Kernel_parameters

And I sudo nano /etc/kernel/cmdline ‘d, but it already says nowatchdog.

Is there any solution to shorten the countdown or remove it permanently if I know what is causing it and I know for sure the system being forcefully closed is safe? The only solutions I’ve seen online was for people who didn’t know what was causing it and it was possibly impactful. I just want my system to turn off immediately without waiting for badly behaved games.

2

The “nowatchdog” kernel parameter has nothing to do with this systemd stop job issue. It disables the watchdog timer, which does not resolve stuck user processes.

There is but with some caveats. You could look into /etc/systemd/system.conf and DefaultTimeoutStopSec=.

But do some research on your own to see what you may get yourself into in case you set the time too low and there are some services running on your system which need longer time to finish their job, close files and be done with write operations etc.

3

You need to kill the process (xkill). It’s possible the game is still running in the background so you kan xkill that one first. If not check for wine or gamescope. To kill it open system monitor settings and click on processes, from there find the game exe, if it’s not there then find wine or gamescope (if you use it). Kill the process with xkill.

I have tested this on my old notebook what happens if i don’t kill the service and if i kill the service.

Results: not killing it will give me the 2 minute timer after reboot or shutdown. (Uid 1000)

Killing it will just shutdown or reboot.

4

Correct me if I’m off base but Steam will do this. It’s doing housekeeping, communicating with the mothership, etc. I just let it do its thing. If you can’t wait 90 seconds or whatever the timeout, consider suspending or hibernating instead.

“Killing the killer” is not only ham-handed but you’re putting trust in various third-party processes to handle a kill command gracefully. That’s not a good standard practice for any app or service.

Just let it run and close down. Otherwise suspend or hibernate, not shut down.

5

Your killing a application that does not want to close. I have tested this, i can leave it a day or two the process does not get killed. So killing it with xkill will not do any harm at all. It works the same ways as killing processes in windows. I tested this with heroic game launcher.