Stop Job Delaying Shutdown

Sometimes when I shutdown I get:
A stop job is running for User Manager for UID 1000 (x s / 2 min)

When I was on ubuntu, this used to work for me. However on EOS, not anymore, is #DefaultTimeoutStopSec=90s overriden somewhere else in the system?
Any help is appreciated. Thanks.

EDIT: System info (Not sure what to post)

Operating System: EndeavourOS
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.4
Kernel Version: 5.15.39-1-lts (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-4340M CPU @ 2.90GHz
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 4600

Correction: on your EnOS system
Unless you can provide info about it.

AFAIK this setting works, if configured By The Book.

hi @unknownuser ,

look at this-> link to the arch linux forum, maybe it’s the same solution for your issue.

Ok, I’ve Updated my post with some system info.
The problem is I’m using KDE and don’t know which service to modify.
$ ls /usr/lib/systemd/user/*{plasma,kde}*


please post the output from the following command:

journalctl -b -1 -e

Sorry, I encountered data corruption on my disk, had to reinstall.
Here is the output:

I’ll repost when this issue happens, it does not happen every time I shutdown/reboot.

1 Like


I to the last few shutdowns have had similar to the topic.
Here is some logs perhaps they can help.

journalctl -b -1 -e


1 Like

hi @Data ,

did you install nextcloud in your system?

@pycrk Not that Iam aware off!!!

Not every shutdown but neat enough.
closest I come to cloud is aur/davinci-resolve-beta
it has new colab/editor feature in it.


After extinguishing the system with the problem, I don’t find posting a new random journal actually useful.
Either you had a problem and post logs from the boot the problem was on, or wait for a problem to (re)appear.

Also, to all users, when you post journal logs, you have to always post the command you have used to obtain the log!!!. …please …

I really don’t know how many forum users actually read and kind-of know what to investigate in the logs, but posting logs that are not requested by someone who will actually read them is painful to the ones that may do it.
Thus, unuseful logs, will eventually make anyone that can read them, to stop doing it in the end, and spend their free time more productively.


That user was on Gnome. The solution was targeted on Gnome :person_shrugging:

This Stop Job Delaying Shutdown is really common and is usually a random per-case event. Not the same to all systems, :no_mouth:

Hi Iam on KDE and do get the regular Stop job on shutdown.

I will provide any logs … that are requested!! I lack knowledge of the
specific commands to collect the logs.
All help gratefully received.


1 Like

I would have a look at:

and start a new thread.

1 Like

I know how to tack on the end bit but what command to do at the beginning of it?

As far as the other thread I see little point this one is titled exactly how I would title it.

Back to the logs there must be a item I can put in to highlight more fully the problem.


The famous YMMV could be applicable to many superficially similar cases.

Anyways, your choice :person_shrugging:t5:

1 Like

Which one? :exploding_head:

1 Like