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)”
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.
Lots of things make no sense to some people that are me.
systemd
Lennart Poettering deserves all the hate he gets and then some…
Just set the limit to something sane like 2³² seconds!
Now you’re thinking with squares!
I’ve never see it, who sets it? I only have two processes that are like it and blth wait for 1:30
I’ve seen it for hardware/driver stuff
Yup, as happened during my most recent linux suicide, dracut just waits infinitely for a device to mount (tho it drops into a emerg shell after like 3 mins or so).
The only time I see it is to do with mounting my NAS at boot and unmounting it on a shutdown.
This is the way.
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
That too takes 15 seconds.
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.
systemctl poweroff <3
I’m still using
shutdown -h now, even though the-hflag has been pointless for, what, 20 years?edit: looks like sysvinit’s
shutdownstill defaults to single-user mode, so I guess that muscle memory will still be useful if I ever use a Devuan or antiX box.
> doesn’t want to learn about Linux > runs Gentoo
Got rid of Vista, installed Mint in 2012. Never a single regret. I am so good at Mint now, it’s hard to be humble.
mine has started acting up quite badly,
-from the start the internet has cut off randomly, likely due to driver issues or hardwareissue. Fixed only by complete restart. There seems to be no pattern, only that machine spirit gets angry if i use internet too much or sometimes just because i woke it up.
-Sometimes when i start the pc it takes really long time to boot and just stays in black screen,
-there are always kind of worrying error messages on startup and shutdown, something about rdseed being broken, something about data being lost, something about a thing hogging the processor and maybe switch to hq_unbound,
-sometimes the pc just refuses to shutdown when shutdown and everything else goes offline but fans keep running.
All of this has just slowly accumulated overtime, without me doing anything that should have caused it.
Yet funnily enough, i’m STILL very much more satisfied than with windows that didnt have that much immidiate issues.
I’ve been using mint for years without learning a single thing about terminal command stuff. It just works. Granted I’m a pretty light user. Light gaming, high seas stuff.
Sometimes this just happens with systemd, it wants to manage every thing as a session and sometimes things running in the session don’t exit like systemd expects.
Also, sometimes logging into a headless ssh session takes quite a while, because systemd is not super responsive to setting up the user session and ssh blocks waiting for that to happen.
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.
This actually got me to go track down the
systemdservice 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.
systemd-analyze ?
“Ask systemd what’s wrong with systemd” feels like “ask Grok what is bad about child sexual abuse” lol.
What about it? I admit that I don’t know a great deal about systemd and all its subcommands - it took me a while to figure out how to disable that service properly, for example - but the manual seems to suggest that systemd-analyze is for startup processes, not shutdown.
I’ll gladly take pointers on how to get it to say why a particular service hung on shutdown.
Transcript:
Top: A woman in a parked car screaming at a child in the back seat
Caption:
Why can’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.
One of the reasons i like the new atomic/immutable distros is you can just power cycle with little worry of bricking your system, even if a system update is running.
That’s what
kill -9is for.Recently I had to reboot to fix a zombie process (caused by a GPU crash, not sure if it was hardware or the driver). When shutting down systemd waited 2 minutes for all process to be killed and then another 2 minutes for the specific zombie process.
What happened when you called
kill?Absolutely nothing. kill -9, SIGCHLD to the parent which was pid 1, relogged my graphical session. After I rebooted I had the thought that I should have tried removing and reinserting the amdgpu module to avoid a reboot. I couldn’t start new mpv processes so shit was pretty fucked lol.
Dang. That’s a good one.
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.
I did have such problems. I just turned off the PSU. 😂
I think I figured out my issue, literally a few minutes ago. I’ve never really dealt with ethernet, so I just learned my bios might have some sort of “wake up on lan” setting enabled that stops me from fully shutting down.
Why would I ever want something like that, though?
Why would I ever want something like that, though?
I should look into wake on lan for my media center so I wouldn’t have to run downstairs to the living room to turn it on if I want to browse my photo/video collection.
I prefer keeping it off when it’s not in use.
Wouldn’t it be more efficient in that case to have some sort of remote* suspend+resume? Saves you the hassle of the bootup and shutdown procedure, when suspend saves most of the relevant energy.
[*] where “remote” can be “hook a tripwire from your room to the keyboard”, at least for the wakeup
I guess I’ll need to look into that option too. Probably won’t look into neither, though. I’m lazy.
Huh, used to see this regularly, but have not seen it for a few years now…
Pov: my brain at night
I would sometimes just get inpatient and force power off
Just sometimes?
I have less issues with that than i do shit getting slow at startup. I hunted down a PAM problem (that I didn’t even configure) for a couple of days of my spare time. 5 minutes startup, i could feel my hail/nails growing between power on and Graphical.
For some reason when I use sddm shutdown sometimes just doesn’t work. Using GDM makes display doesn’t work (weird hdmi quirk with bitdepth). So instead I login via TTY and start my session manually. At least then I can shutdown my system. Usually.
