A stop job is running
this post was submitted on 30 Jul 2026
428 points (98.0% liked)
linuxmemes
32538 readers
1122 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry of any kind will not be tolerated. This is an LGBTQ+-friendly community -- if that is a problem for you, you should leave.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
- Don't come looking for advice, this is not the right community.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves / tolerates / hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 3 years ago
MODERATORS
At least it tells you how long it'll take before it decides to SIGKILL whatever is holding the shutdown sequence.
Well you say that, but I've seen the countdown go past and then reset to a higher number often.
I entrust you with this horror, go figure out what to blame.
#! /usr/bin/env bash
shutdown_start=$(journalctl -b -1 -u systemd-logind --grep="System is (powering down|rebooting)" --output=cat --no-pager --output-fields=_SOURCE_REALTIME_TIMESTAMP)
shutdown_start=$((shutdown_start / 1000000))
units=$(journalctl -b -1 --since=@$shutdown_start --output=cat --no-pager --output-fields=UNIT JOB_TYPE=stop CODE_FUNC=job_emit_start_message)
for u in $units; do
stopping_start=$(journalctl -b -1 --since=@$shutdown_start -u "$u" --output=cat --no-pager --output-fields=_SOURCE_REALTIME_TIMESTAMP JOB_TYPE=stop CODE_FUNC=job_emit_start_message _SYSTEMD_UNIT=init.scope)
stopping_end=$(journalctl -b -1 --since=@$shutdown_start -u "$u" --output=cat --no-pager --output-fields=_SOURCE_REALTIME_TIMESTAMP JOB_TYPE=stop CODE_FUNC=job_emit_done_message _SYSTEMD_UNIT=init.scope)
duration_human=$(systemd-analyze timespan $((stopping_end - stopping_start))us | tail -1 | sed 's/.*: //')
printf "%s\t%10s %s\n" $((stopping_end - stopping_start)) "$duration_human" "$u"
done | sort -rn | cut -f 2
load more comments
(2 replies)
load more comments
(1 replies)
I think that depends on the setting, I had situations where one of my docker containers took ages to shutdown and it would just say 00/02 00s but when it reached that limit, it would just go up.
Individual services can override the default 90 seconds timeout. But then you can override their override if you think you are smarter, of course.
Alt-SysRq-i, u, o
I don't have time for this shit.
have i learned a new magic combo?!
(X time / 1:30) but the second time will be extended indefinitely for some fucking reason.
Yes but no, u can in config file of systemd change timeout to 5,10 second or other number of seconds which u wish before it will kill it
My always plugged in HDD with bees on it does that. 1 minute to shutdown at least because there's always some kind of extend read or dedupe that need a sync.
... I brought this upon myself so I don't have to complain.
load more comments
(2 replies)
[**ββββ] A stop job is running for Session c1 of User gdm (49s / 1min 30s)
`[**ββββ] A stop job is running for Session c1 of User gdm (4min 19s / 1min 30s)`
I've never used systemd to shut down
Sudo shutdown -h now works on the Mac
I just use poweroff.
load more comments
(1 replies)
Just poweroff is fine. Why lose extra 2.5 seconds typing two words when one word will suffice?
load more comments
(7 replies)
It's even worse, when I tell my work Windows 11 computer to shut down and I have to choose update and shutdown because it decided to do updates, sometimes it reboots a few times but then it doesn't turn off afterwards.
I'm never going to install Windows 11 on any of my devices, it's so bad.
I bought a new mini PC the other day that shipped with windows 11. Before installing Linux I thought "I'll just boot into windows to make sure the hardware is all correct".
I got as far as the windows welcome screen and thought "it's actually just going to be faster and easier to install Debian instead of going through all this windows bullshit"
I got a new Mini a month ago. Before I even powered it up, I stabbed a USB stick into it, hit escape on boot, and killed that bitch with Kinonite.
There are two things a person needs to do when starting up a fresh new computer: First, you must bathe in the purifying waters of Lake Minnetonka, and never, ever let Windows have even a single chance to live.
Or my old windows 10 machine would wake itself up in the middle of the night to run updates that the group policy wouldn't even allow it to download without my permission and then just sit there. If I hadn't fallen asleep yet, I'd notice the monitor light up the next room and get up swearing at Microsoft until I tracked down where the wakeup timer was set and disabled it. Only to find it re-enabled after some updates.
Fuck Microsoft.
It's fun when your laptop decides to do this kind of nonsense from inside your laptop bag, smothering itself in its own heat.
load more comments
(1 replies)
load more comments
(1 replies)
Five seconds? What's hogging that system? Mine is about two, at most, from the WM shutdown selection.
Everyone arguing about the amount of keypresses to type a shutdown command and time it takes to shutdown... I just power it off at the wall. One button press, shutdown is near instantaneous
load more comments
(4 replies)
Are you guys really using a command to shut down a computer?
Because you can do the same with Windows, but nobody uses it because it is just not convenient to use commands for that.
shutdown /s
"please shut down (this is sarcasm)"
Yeah, you can even throw a /f in there to force close all apps so it will kill everything and go nighty night. I used to use it with /t command if I wanted to download something while I was out but not have the PC run all day.
That's not the best way to turn your PC off but hell half the time I just murder mine by holding down the power button anyways. As long as you're not being crazy shutting her down in the middle of some data operations you'll be fine.
load more comments
(2 replies)
load more comments
(2 replies)
systemctl invariably hangs on waitimg for some job to finish. systemd-shutdown-inhibitor is hideous.
poweroff -ff
Not to be that guy but...
shutdown /s /f /t 0
No, you have to use the GUI in Windows.
load more comments
(1 replies)
Powers on
Immediately starts shut down
Refuses to close because the following programs are still running
The list is empty
Windows update set my PC back almost 3 years for some unknown reason, lost so much shit. That was my final fuck it this shit moment, I installed Mint last week. A little bit of a learning curve, but I'm enjoying it and not worried about everything getting ruined unless I do something dumb. I can live with my own stupid.
This boils down to a Linux using a file system which allows files to be deleted or replaced in the inode table while something has the old file open. So it's easier (although not simple) to replace packages while other stuff is running. Whereas Windows has to shut everything else down so nothing has the file open to replace it and also fix stragglers during the next reboot.
load more comments
(3 replies)
You know I'm okay with Windows running updates I shut down or anything else like that. It's incredibly annoying when people don't run updates and then wonder why their system gets fucked up. It's just like on Linux when people just absolutely refuse to acknowledge the fact that they need to run updates. And many times I need to run the updates manually through the command line. There are quite a few gooey applications and things like that that will allow you to run updates but many times you still have to run them manually. And then something breaks and people wonder why I broke when they didn't run any updates. So in the end really who gives a fuck if it's running updates on shutdown you hit the button says run updates you tell it to run updates and you either close the lid on your laptop and walk away or you carry it till it shuts down within a few minutes and then you shut it down. Or you just let your desktop run until it's done. It's really not that big of a deal that people here seem to make it out to be and seem to make 10 different memes a day about the shutdown process on whatever OS they want to shut down.
For most people, especially work computer/laptop users, making the update happen by default on restart or during sleep hours does a lot to keep the pc updated, because they would otherwise never do it themselves. There is a somewhat large minority of users who complain about such behaviour, but these are mostly people into computers anyways and can update their stuff anyways.
But the biggest gripe is the horrid implementation of the start menu power buttons in windows:
- update and restart: mostly works as you would expect - updates and boots the pc
- update and shutdown: updates the pc, and instead of leaving the pc in shutdown state, many times it just boots the pc again, working like update and restart
- restart/shutdown without updating: non-insignificant chance of it doing the update anyways
load more comments
(1 replies)
load more comments
(5 replies)
Systemctl? Bro just poweroff
view more: next βΊ