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.

I've never see it, who sets it? I only have two processes that are like it and blth wait for 1:30

Just set the limit to something sane like 2³² seconds!

This is the way.

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.

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.

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, not any of the other stuff?

Like the same locking wait message, but on startup because of wifi

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.

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.

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.

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.

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.

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.

systemd-analyze ?

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

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.

The transcript is appreciated, but I don't think screen reader will take kindly to mixing imgflip.com and A stop job is running.