Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
[SOLVED] debian 11 - a stop job is running for user manager for uid 1000
[SOLVED] debian 11 - a stop job is running for user manager for uid 1000
fresh installation of debian 11 with mate desktop and i'm getting this message on every reboot or shutdown.
i close every program when i reboot or shutdown and don't know what is happening.
i close every program when i reboot or shutdown and don't know what is happening.
Last edited by ddebbb on 2022-02-06 01:02, edited 1 time in total.
Re: debian 11 - a stop job is running for user manager for uid 1000
Workaround: logoff first, then shutdown or reboot.
Camouflage solution:
Edit /etc/systemd/system.conf and find & change these lines:
This will only wait for 10 seconds while starting or stopping jobs and then move on.
Camouflage solution:
Edit /etc/systemd/system.conf and find & change these lines:
Code: Select all
DefaultTimeoutStartSec=10s
DefaultTimeoutStopSec=10s
-
- Global Moderator
- Posts: 2960
- Joined: 2014-07-20 18:12
- Location: Europe
- Has thanked: 73 times
- Been thanked: 405 times
Re: debian 11 - a stop job is running for user manager for uid 1000
Hello ddebbb,
The message is caused by a service not responding to the shutdown command: in [1] you can find the explanation by the author of systemd. Therefore, you should analyze the system log (journal) of a previous shutdown to identify which is the offending service. For example, you could use the following commands as root user:
The journal.log will contain the journal log of the previous boot.
[1] https://github.com/systemd/systemd/issu ... -747040852
The message is caused by a service not responding to the shutdown command: in [1] you can find the explanation by the author of systemd. Therefore, you should analyze the system log (journal) of a previous shutdown to identify which is the offending service. For example, you could use the following commands as root user:
Code: Select all
journalctl --no-pager -b -1 > journal.log
[1] https://github.com/systemd/systemd/issu ... -747040852
-
- Global Moderator
- Posts: 2960
- Joined: 2014-07-20 18:12
- Location: Europe
- Has thanked: 73 times
- Been thanked: 405 times
Re: debian 11 - a stop job is running for user manager for uid 1000
Hello ddebbb,
The log you sent shows an inactivity period of about 1 minute and 30 seconds from 22:33:18 to 22:34:46 that is probably when the "stop job is running" message is shown:
The last message before the pause is:
This is not a confirmed evidence that the Plymouth is the stuck program/service, but I suggest you to uninstall it to verify if it is the culprit.
The log you sent shows an inactivity period of about 1 minute and 30 seconds from 22:33:18 to 22:34:46 that is probably when the "stop job is running" message is shown:
Code: Select all
[...]
Aug 26 22:33:18 XXXXXPC systemd[1]: Stopped Light Display Manager.
Aug 26 22:33:18 XXXXXPC systemd[1]: lightdm.service: Consumed 16min 54.831s CPU time.
Aug 26 22:33:18 XXXXXPC systemd[1]: Starting Show Plymouth Power Off Screen...
Aug 26 22:33:18 XXXXXPC systemd[1]: systemd-logind.service: Succeeded.
Aug 26 22:33:18 XXXXXPC systemd[1]: Stopped User Login Management.
Aug 26 22:33:18 XXXXXPC systemd[1]: Received SIGRTMIN+20 from PID 12553 (plymouthd).
Aug 26 22:33:18 XXXXXPC systemd[1]: Started Show Plymouth Power Off Screen.
Aug 26 22:34:46 XXXXXPC systemd[665]: Stopping D-Bus User Message Bus...
Aug 26 22:34:46 XXXXXPC systemd[665]: pulseaudio.service: Succeeded.
Aug 26 22:34:46 XXXXXPC systemd[665]: Stopped Sound Service.
Aug 26 22:34:46 XXXXXPC systemd[665]: pulseaudio.service: Consumed 2min 21.252s CPU time.
Aug 26 22:34:46 XXXXXPC systemd[665]: dbus.service: Succeeded.
Aug 26 22:34:46 XXXXXPC systemd[665]: Stopped D-Bus User Message Bus.
Aug 26 22:34:46 XXXXXPC systemd[665]: Stopped target Basic System.
Aug 26 22:34:46 XXXXXPC systemd[665]: Stopped target Paths.
Aug 26 22:34:46 XXXXXPC systemd[665]: Stopped target Sockets.
Aug 26 22:34:46 XXXXXPC systemd[665]: Stopped target Timers.
Aug 26 22:34:46 XXXXXPC systemd[665]: dbus.socket: Succeeded.
[...]
Code: Select all
Aug 26 22:33:18 XXXXXPC systemd[1]: Started Show Plymouth Power Off Screen.
Re: debian 11 - a stop job is running for user manager for uid 1000
it is still present.
a bug maybe in the kernel?
a bug maybe in the kernel?
Re: debian 11 - a stop job is running for user manager for uid 1000
No.
Did you try Bloom's workaround?
Try this for example:
Did you try Bloom's workaround?
Try this for example
Code: Select all
journalctl -r -S yesterday | grep Failed
Re: debian 11 - a stop job is running for user manager for uid 1000
yes, this works: logoff first, then shutdown or reboot.
this not: Edit /etc/systemd/system.conf and find & change these lines DefaultTimeoutStartSec=10s DefaultTimeoutStopSec=10s
this not: Edit /etc/systemd/system.conf and find & change these lines DefaultTimeoutStartSec=10s DefaultTimeoutStopSec=10s
Code: Select all
XXXXXUSER@XXXXXPC:~$ journalctl -r -S yesterday | grep Failed
Aug 30 11:51:37 XXXXXPC udisksd[516]: Failed to load the 'mdraid' libblockdev plugin
Aug 30 11:51:35 XXXXXPC bluetoothd[508]: Failed to set mode: Blocked through rfkill (0x12)
Aug 30 11:50:48 XXXXXPC systemd[691]: obex.service: Failed with result 'exit-code'.
Aug 30 11:07:00 XXXXXPC udisksd[517]: Failed to load the 'mdraid' libblockdev plugin
Aug 30 11:06:59 XXXXXPC bluetoothd[509]: Failed to set mode: Blocked through rfkill (0x12)
Aug 29 22:56:25 XXXXXPC systemd[683]: obex.service: Failed with result 'exit-code'.
Aug 29 22:26:18 XXXXXPC udisksd[487]: Failed to load the 'mdraid' libblockdev plugin
Aug 29 22:26:16 XXXXXPC bluetoothd[477]: Failed to set mode: Blocked through rfkill (0x12)
Aug 29 22:24:00 XXXXXPC systemd[698]: obex.service: Failed with result 'exit-code'.
Aug 29 20:08:59 XXXXXPC udisksd[502]: Failed to load the 'mdraid' libblockdev plugin
Aug 29 20:08:58 XXXXXPC bluetoothd[494]: Failed to set mode: Blocked through rfkill (0x12)
XXXXXUSER@XXXXXPC:~$
Code: Select all
XXXXXUSER@XXXXXPC:~$ journalctl --no-pager -b -1 --priority=err
-- Journal begins at Sun 2021-08-15 21:58:18 -04, ends at Mon 2021-08-30 12:55:21 -04. --
Aug 30 11:06:59 XXXXXPC bluetoothd[509]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Aug 30 11:06:59 XXXXXPC bluetoothd[509]: sap-server: Operation not permitted (1)
Aug 30 11:06:59 XXXXXPC bluetoothd[509]: Failed to set mode: Blocked through rfkill (0x12)
Aug 30 11:07:36 XXXXXPC lightdm[684]: gkr-pam: unable to locate daemon control file
Aug 30 11:07:36 XXXXXPC pulseaudio[640]: Error opening PCM device front:0: No such file or directory
Aug 30 11:07:36 XXXXXPC pulseaudio[640]: Error opening PCM device front:0: No such file or directory
Aug 30 11:50:52 XXXXXPC kernel: watchdog: watchdog0: watchdog did not stop!
XXXXXUSER@XXXXXPC:~$
-
- Global Moderator
- Posts: 2960
- Joined: 2014-07-20 18:12
- Location: Europe
- Has thanked: 73 times
- Been thanked: 405 times
Re: debian 11 - a stop job is running for user manager for uid 1000
Hello,
You could generate a log with a greater detail modifing systemd configuration: see [1].
[1] https://wiki.debian.org/systemd#systemd ... r_shutdown
You could generate a log with a greater detail modifing systemd configuration: see [1].
[1] https://wiki.debian.org/systemd#systemd ... r_shutdown
-
- Posts: 22
- Joined: 2021-08-19 02:18
Re: debian 11 - a stop job is running for user manager for uid 1000
Hi there!
I'm not sure if that would help, but i've been having a similar problem. My PC can't shutdown because of a service that is never stopping.
I found out it was something related to the Network Manager (to be more specific, it was with the WPA encryption service wpa_supplicant) that was stuck and preventing my PC from turning off.
Anyways, as a test to see if it might be the same issue, try to stop the network manager service (systemctl stop NetworkManager) and try to start it again (systemctl start NetworkManager). If you feel your PC or your terminal is behaving funny, it could be something related to the NM.
I know it seems that i didn't read the post was it was stated in the title that is user manager.
But i was always getting a message that it was the cups service i have here fault, but it wasn't. Maybe it might be the same problem or, at least, related to mine.
I'm not sure if that would help, but i've been having a similar problem. My PC can't shutdown because of a service that is never stopping.
I found out it was something related to the Network Manager (to be more specific, it was with the WPA encryption service wpa_supplicant) that was stuck and preventing my PC from turning off.
Anyways, as a test to see if it might be the same issue, try to stop the network manager service (systemctl stop NetworkManager) and try to start it again (systemctl start NetworkManager). If you feel your PC or your terminal is behaving funny, it could be something related to the NM.
I know it seems that i didn't read the post was it was stated in the title that is user manager.
But i was always getting a message that it was the cups service i have here fault, but it wasn't. Maybe it might be the same problem or, at least, related to mine.
-
- Posts: 3
- Joined: 2018-08-15 14:18
- Location: Tucuman, Argentina.
Re: debian 11 - a stop job is running for user manager for uid 1000
Hi everyone. I hope they are well.
I have exactly the same problem and I can't find a solution. I already tried everything I read for four hours and it did not solve the problem.
Any ideas?
Thank you.
Jorge Iruzubieta
I have exactly the same problem and I can't find a solution. I already tried everything I read for four hours and it did not solve the problem.
Any ideas?
Thank you.
Jorge Iruzubieta
-
- Posts: 3
- Joined: 2018-08-15 14:18
- Location: Tucuman, Argentina.
Re: debian 11 - a stop job is running for user manager for uid 1000
I found the problem:
Reboot the system and see what time exactly it was (1:45 am).
Then I did:
I found the following line:
sep 05 01:46:33 iruzubieta systemd[679]: app-audacious-16bd03a7f143403b8a11e5a6c671983e.scope: Failed with result 'timeout'.
I stopped Audacious before shutting down the system and then when I shut down the system I no longer had the problem.
I hope you understand why I am using google translator. I speak Spanish.
Thank you!
Reboot the system and see what time exactly it was (1:45 am).
Then I did:
Code: Select all
journalctl -r -S yesterday | grep Failed
sep 05 01:46:33 iruzubieta systemd[679]: app-audacious-16bd03a7f143403b8a11e5a6c671983e.scope: Failed with result 'timeout'.
I stopped Audacious before shutting down the system and then when I shut down the system I no longer had the problem.
I hope you understand why I am using google translator. I speak Spanish.
Thank you!
-
- Posts: 22
- Joined: 2021-08-19 02:18
Re: debian 11 - a stop job is running for user manager for uid 1000
Hey there, mate! How are you?jorgeiruzubieta wrote: ↑2021-09-05 05:17 I found the problem:
Reboot the system and see what time exactly it was (1:45 am).
Then I did:
I found the following line:Code: Select all
journalctl -r -S yesterday | grep Failed
sep 05 01:46:33 iruzubieta systemd[679]: app-audacious-16bd03a7f143403b8a11e5a6c671983e.scope: Failed with result 'timeout'.
I stopped Audacious before shutting down the system and then when I shut down the system I no longer had the problem.
I hope you understand why I am using google translator. I speak Spanish.
Thank you!
I had the same issue with the WPA Supplicant service. Once i stopped the service manually, my computer is turning off normally too.
Since i had a sh file that update and upgrade my system before shutting down, i adapted my script to stop WPA Supplicant before shutting down.
It didn't SOLVE the problem, but at least i could bypass it. hahahaha
-
- Posts: 3
- Joined: 2018-08-15 14:18
- Location: Tucuman, Argentina.
Re: debian 11 - a stop job is running for user manager for uid 1000
Hi, friend! Glad it works.
I have a script that shuts down qbittorrrent before stopping the system and from there it takes me to the shutdown, reboot, etc screen. I got it from another forum, I don't remember which one.
For some reason if I try to stop the system while qbittorrent is running, it will not stop the system. So with this script I stop it earlier.
Modify the script and add a line to it so that Audcious also stops me and it works!
The script:
I made it executable, copied it to /usr/bin and then created a shortcut for it in the Applications Menu.
Many thanks to the person who created the script originally, wherever you are, I don't remember where I got it from.
Greetings!!!
Jorge Iruzubieta
I have a script that shuts down qbittorrrent before stopping the system and from there it takes me to the shutdown, reboot, etc screen. I got it from another forum, I don't remember which one.
For some reason if I try to stop the system while qbittorrent is running, it will not stop the system. So with this script I stop it earlier.
Modify the script and add a line to it so that Audcious also stops me and it works!
The script:
Code: Select all
#! /bin/bash
pkill -o qbittorrent
pkill -o audacious
qdbus org.kde.ksmserver /KSMServer org.kde.KSMServerInterface.logout 1 2 2
Many thanks to the person who created the script originally, wherever you are, I don't remember where I got it from.
Greetings!!!
Jorge Iruzubieta
Re: debian 11 - a stop job is running for user manager for uid 1000
this problem is still present with debian 11.1
fresh install (netinst) and default settings, but this only happens to mate desktop.
fresh install (netinst) and default settings, but this only happens to mate desktop.
- craigevil
- Posts: 5391
- Joined: 2006-09-17 03:17
- Location: heaven
- Has thanked: 28 times
- Been thanked: 39 times
Re: debian 11 - a stop job is running for user manager for uid 1000
i have this, but only if i do not manually shutdown conky and protonvpn. With them both shutdown the long timeout goes away. i don't shutdown or reboot often enough for it to be a problem.
Raspberry PI 400 Distro: Raspberry Pi OS Base: Debian Sid Kernel: 5.15.69-v8+ aarch64 DE: MATE Ram 4GB
Debian - "If you can't apt install something, it isn't useful or doesn't exist"
My Giant Sources.list
Debian - "If you can't apt install something, it isn't useful or doesn't exist"
My Giant Sources.list
Re: debian 11 - a stop job is running for user manager for uid 1000
Installing systemd from backsports solved this issue.