reupload because i mixed up sigterm and sigkill like a dumb fuck
user error doesn’t count
I couldn’t find better screenshot, but I’ve definitely seen this happening due to zombie processes after just regular use, rather than just broken mount. I feel like it’s handled way better nowadays though.
Keeping it real hell yeah
I had a systemd bug delay shutdown for 2 mins every time for a very long time on Debian. Never managed to fix it, Fedora did not have the same issue fortunately.
The first time I shutdown a Linux computer, I thought I broke something it happened so fast.
Meanwile MorphOS booting up and shutting down: https://www.youtube.com/watch?v=kIgybl6LfqU
The jingle at the start is the Mac’s own. The shutdown is so fast, you’ll miss it if you blink. No services, no demons or whatever.
(That was 2013. I’d argue it starts up even faster now.)also true for boot (not from suspended state), in my experience.
windows: wait, let me display the windows logo for 10 seconds, then show a spinny circle, then show the lock screen, then when you try to enter your password, it loads your user profile for another 5 minutes before it shows your desktop icons
linux: click the power button -> 1.5 seconds later i see the lock screen. enter password and it’s just there.
Reboot
Windows: save all your woooork. What apps you had open? How would I know?
Linux: it’s all saved in ram, don’t worry. It’ll be like you never rebooted
“By the time you hear the sudo pop, the reboot shall be
inside youdone”-Kendrick Lamar Linux
Linux gang reis ub!
…do they even have SysReq keys anymore?
Reverse meme when it’s time to install the updates.
Windows in that case is “I MUST REBOOT IMMEDIATELY PREPARE TO LOSE ALL UNSAVED DATA IN 3. 2. 1…”
Not quite. I will RESUME FROM THIS FUCKING “MODERN SLEEP” shit, even though you the user want to turn this shit right off, do it without any warning watsoever, close all your fucking windows and good luck if you have lost work or not.
When I switched to win 10, I actually gave them more money to get the pro version for access to the group policy editor so I could control updates and never have to deal with my PC telling me it’s time to restart on its own. Because I was stupid.
When it came time to switch to Win 11, I did the much more sensible thing and installed Fedora instead. I started with cinnamon and even though I ended up disliking it also, it was still way better than the windows experience.
[HKEY_CURRENT_USER\Control Panel\Desktop] "AutoEndTasks"="1"Look what they need to mimic a fraction of our power
taskkill /f /im “application.exe”
I had to update a Windows 11 work laptop after not touching it for nearly a year. I click ‘shut down’ from the start menu and nothing happens. What? Try it again. Nothing again.
I have to hold down the power button before the screen shows a “slide to shut down” screen now. How did Microslop fuck up the ‘shut down’ so badly.
I love how the design is so bad now we’re missing the days when shutting down the computer required the “Start” button.
It’s tragic the level of immediate relief I feel every time I shutdown on Linux after years on Windows.
“YOU CAN’T SHUT DOWN YET, STEAM STILL RUNNING” -Win10, literally every time.
The fuck?
I’ve had it yell at me because it couldn’t close some dialog window that explorer opened because I was trying to shut it down
A stop job is running for User Manager for UID 1000 (12s / 2 mins)
( 1min 59s / 2 mins )
…
( 2 mins / 3 mins )
???
That’s because it first send
sigterm, thensigkill. Then it gives up and let the kernel handle it…Happens on my BTRFS disk’s unmount. If the kernel is currently busy handling some heavy btrfs command (like a 4tb scrub), systemd cannot stop it with sigkill.
So when it eventually gives up, you also need to wait for the kernel to finally stop the operation and actually disconnect the disk.
(5min 7s / no limit)
Shieeet
In those cases there’s an easy solution.
Step 1: sigh
Step 2: press the power button 5 or 10 seconds while contemplating why you decided to do a quick restart instead of keeping the session and do something actually productive
I recommend starting with SysRq+E before that, there’s a chance it gets whatever the shutdown was waiting for. And if that fails… REISUB my beloved.
RSEIUB. Raising skinny elephants is utterly boring.
I think you can set the default stop job timer lower?
You can change that, but there is a maximum time when it just kills the job.
