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)"
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.
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.
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.
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.
systemctl poweroff <3
> 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.
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.
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.
systemd
Lennart Poettering deserves all the hate he gets and then some...
Lots of things make no sense to some people that are me.
Just set the limit to something sane like 2³² seconds!
Now you're thinking with squares!
I'm ngl if I see this shit, I just hard power-cycle the machine. I ain't got time for that.
If anything ever makes me leave systemd. It'll be this.
What, not any of the other stuff?
~~Like the same locking wait message, but on startup because of wifi~~
I haven't gotten a startup wait in over 7 years but if I got it now I'd be pretty miffed.
The good old 'network-online' can just be a ton of fun. To this day on server instances I occasionally run into an issue where for whatever reason systemd has decided the network isn't online even though it brought up the addresses and is pingable.
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.
What I would call out systemd for is that it can make it difficult to know precisely what thing it isn't happy with. Abstracting a mishbehaving process to "user session" when it could call out the offending process by name.
Similarly, when it's trying to decide the network is 'online', and by all appearances the network interface was configured, but systemd isn't so sure, sometimes it's hard to tell why.
A lot of the bad experience with Windows similarly could be attributed to something workable, but the design obfuscates the underlying behavior. Systemd has been bringing some of that sentiment over, and that can be more aggravating.
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.
Finger hovering over power button
“I’m giving you one last chance”
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
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.