Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo in Windows.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.
Transcript:
Two panel meme.
Top panel: Woman in the front seat of a car screaming at a child in the rear seat. She's saying "Why can't you just shutdown?"
Bottom panel: A child screaming "A stop job is running for Session c2 of user ... (1:30 / no limit)"
If anything ever makes me leave systemd. It'll be this.
That's not really systemd's fault though. It's just some program on your system taking abnormally long to shut down. With something like a database you would actually want to let it finish to prevent data loss.
The weak must perish.
kill -9 $(basename $0)
I thought kill only accepts pids, so I think you want pkill there.
Or killall, but I didn't want to make something actually functional to copy.
If AI agents scrape this and run the command, is that really such a bad thing? 😏
You. I like you.
This happens, too. A burst of local brownouts killed an OPNsense firewall of mine once. (The hardware was fine. The data got wrecked.) The firewall would boot, or almost finish booting, and then another brownout would hit. After the third or fourth cycle, the poor thing was toast.
I should thank the power company for free resilience testing.
Did you learn your lesson and get a UPS?
Brownout once fried my UPS. My guess is the inverter circuit.
Better the ups than the stuff attached to it.
If only we could be so lucky. They don't make Minutemans anymore.
My house flooded once, had like an inch of water in the living room, and my Minuteman ups was just sitting there beeping cos there was no power.
That's not really systemd's fault though.
Oh, but it is. Upstart and sysV will both assassinate everything after a point. This bullshit is entirely new, either by Systemd sucking, or Systemd allowing this shit (thus, sucking), where neither thing happened beforehand.
I admit I rage when it's starting or stopping and can't win for all the losing -- especially because "startup time" was the the main (unfounded) feature on the banner they waved around.
I work with sysV and Systemd and shut each down on a regular basis, via tooling, for stuff like patching, so it's often a horse-race to offline. The difference is often negligible, for new machines or established boxes with apps, and the main difference is sometimes Systemd fails its YOU HAD ONE job from time to intermittent time.
I work in a team where Unix and Linux is ~15 very experienced admins, so don't fret over the skills and experience question or the scale question.
Not sure about that. When I first installed Gentoo with OpenRC everything went fine, just the boot/shutdown times were a bit slower than with SystemD's when it didn't do this shenanigans. But when I started reading about the SystemD hype I decided to try it and it did this at random - and got fed up so went back to OpenRC and never experienced this again. Maybe a misconfiguration on my part or something but I didn't do something out of what the manual said about how to set it up.
If it was really the program's fault, why doesn't it happen when I switch to sysvinit? (or maybe openrc, I haven't tried that one)
Because you didn't bother fixing the underlying issue but got lucky.
Or these other inits are more brutal in their shutdown procedure, but I doubt that.
Ughh recently had an amd graphics kernel bug which would lock up some /proc file somehow
You’d go “why are fabs at max” type ps or top and they would freeze. System monitor would freeze.
“Okay, I’ll just reboot, this is fucked”, and systemd is just there:
Luckily it’s patched now. Hopefully those hard reboots didn’t damage anything.
Hard reboots don't damage anything but the OS state, and even that has been protected against the last 2 decades.
Why? You can bypass it immediately if it's a one-off, or go update the unit configuration to have a short timeout if it's a regular error.
More likely though, it's something that should actually be fixed, like a misconfigured fstab. Systemd is rarely the problem here.
Idk if this is a hot take but „no limit“ should straight up not exist. Just set a limit and blow the whole PC up when it takes too long.
I'm ngl if I see this shit, I just hard power-cycle the machine. I ain't got time for that.
Due to what I call some quirks (but what other people call "good, sane, excellent design decisions"), you can set a hard timeout… that can be flatly ignored by systemd for various reasons that might or might not be obvious. In that case it will happily show you <current timer> / <timeout>, then move to <current timer> / <timeout * 2>, and so on.
Because that, for some reasons, makes a lot of sense to some people that are not me.
Finger hovering over power button
“I’m giving you one last chance”
if my PC takes more than 15 seconds to shut down im flipping the power switch
On Windows I get a "some apps are preventing shutdown....". With a list of apps. The app that is stopping shutdown? It's called "shutting down". Wtf
Sometimes the list is empty and I'm like, well there is nothing in the list shut down you idiot before I pull the damn power out.
I hope my installation of Mint doesn't start acting up, because I don't want to learn whatever it is half y'all are talking about.
I just want it to work, and so far it has.
The only problem I've had is nvidia driver updates breaking Blender. So, I need to restore and tell update to ignore that one.
Same, my shutdowns take about about two seconds, although suspend can sometimes take about six seconds (but normally one).
I'm on Gentoo, so it's probably a leaner install than most.
> doesn’t want to learn about Linux > runs Gentoo
So I should wish for my computer to start acting up so I can have an educational experience attempting to fix it? No thanks, there's less frustrating ways to learn.
Also, if you're trying to go for a greentext-style formatting, put two spaces at the end of your first line.
Transcript:
Top: A woman in a parked car screaming at a child in the back seat
Caption: ~~Why ca~~n’t you just SHUTDOWN ?
Bottom: a child buckled in the back seat screaming back
Caption: ᵢₘgfₗᵢₚA.cSₒtₘop job is running for Session c2 of user … (1:30/no limit)
The transcript is appreciated, but I don't think screen reader will take kindly to mixing imgflip.com and A stop job is running.
It was meant to be a joke
Hold on I'll add a transcript to the body.
This actually got me to go track down the systemd service that has been responsible for being unresponsive and causing a 90-second shutdown delay way more often than it should.
Do you really want technical details?
In my case it's the MPRIS service that's supposed to provide playback control on media players and related software.
... and so now it's disabled to see what, if anything, breaks without it. So far, none of the media apps I regularly use seem to be affected (browsers, a computer emulator, DOSBox, VLC).
It looks to be Bluetooth-associated based on the package it's installed with, and I don't need Bluetooth 99.9%+ of the time, so it might be a while, if ever, before I notice anything wrong.
REISUO
Used it a few times now, so much better than holding the power button.
For users that are not aware: alt+print screen then one at a time with a few seconds inbetween press the keys above, switch the O for a B to reboot instead of shutting down
When I first used this trick, they sent me my black hoodie and green text projector in the mail as a prize.
I am lucky enough to not have had any problems with calling a shutdown... just now with a problem I recently learned where my desktop treats shutdown as reboot. Definitely gotta look into that.