It’s a screenshot of a screenshot in a video? What’s that shield?
Ah I completely forgot that it was a separate extension, I only use it in smarttube 😂
It’s a screenshot of a video that I did
You did the screenshot, or the video? Or both?
screenshot
for the most part i don’t care, but really, all those fucking terminals i left open, i know they’re open, that click per window of yes close has never been helpful
I used to override that setting.
I…uh…learned some uses for it.
I bet there were interesting uses.
I won’t say i’ve never shut down a long running process, but i’ve gotten a lot better at not running them adhoc in a terminal :)
The program ‘btop’ is currently running in this session. Are you sure you want to close it?
i’ll prob just start running pkill konsole before shutdown. was thinking of pkexec /sbin/shutdown -h now on a button, but it is kind of nice having some of my apps recover on reboot.
I just don’t shutdown until I get a big backlog of updates. I have to remount my SSD with my games on it every time, then tell steam.
what? why? can you not persist your mounting scheme in the fstab? sorry if i’m being ignorant just genuinely wondering
I blew up the OS a few times doing that wrong. I’ll just hit the mount button. Good enough.
it’s real easy. if you tell me your distro and send me your lsblk output when it’s setup how you like i can send you what to put in fstab to persist it. better for system management, better for the puter. gotta reboot more often :)
My Windows is more like “I am scheduling the restart. Pray I don’t schedule it any sooner.”
Mine will do the restart and boot into Linux.
Windows Updates are always like that. Halfway through it’s got to restart, bootloader picks Linux, Windows doesn’t get to finish the other half of its update til the next time it’s chosen.
You can configure Grub to boot into whichever entry you last selected. Makes rebooting much more convenient
Is Linux higher in your boot priority?
Linux is higher in any priority.
Always has been.
When I had a dualboot, that’s how I ordered it.
you know you can make it so the last used OS gets booted right?
yay rEFInd
I like how you censored systemd
People need to learn that it’s ok to say systemd on the Internet and stop self censoring
Let’s not get carried away. Fuck and shit are ok, but I draw the line at s*****d
init.dstraight to jail
Yes, let’s keep this community family friendly. I could do without such obscenities.
system deez nuts
Windows just randomly installing updates only when I’m working on something with a customer.
one of the reasons I’m moving away. pisses me off so much at work, I don’t even want it at home
Windows after pressing shutdown and update: you wanted to use me still right???
Shutdown isn’t shutdown anymore, so it has to reboot for the updates. After the reboot, though, there’s no longer a shutdown pending.
This is just not true.
- Linux does have a graceful process.
- Windows’s process is not graceful
Yeah and in linux when you say “kill this process” that process fucking dies. No 10 minutes of windows trying to negotiating with a crashed program to close. No I’m not angry about this happening to me at work today, why do you ask?
Both Windows and Linux have ways to gracefully ask a program to close and to force close it. Not being able to select the correct one on either system is a skill issue.
I am not sure how Windows handles processes, but on Linux you have different signals.
SIGKILL
(9) generally kills the process immediately, but there are other signals likeSIGTERM
(the default signal, 1) which asks process to gracefully quit, and many others.If you want to know more, check the
signal(7)
man page or this Wikipedia page.And when chrome freezes rest of the desktop goes gray and everyrhing else freezes too including the task manager.
Fuck me that’s ugly.
I had such an issue with Teams on Mac the other day. It had a phone call stuck running in the background, so I tried to Quit the app. The Quit Teams option just turned gray, and the laptop even refused to reboot.
I am one of lucky 10 000 Thanks
same here!
Same
goddamn generation loss-ass meme.
On my work PC I disabled automatic restarts and I’ll just hibernate it for weeks at a time, keeping my work stuff open. Convenient, and I can install updates when I choose to.
Just do sysrq+s, sysrq+c (triggers panic) and flip the power switch for instant power off.
Managed to wreck my NVMe drive with an unsafe shutdown on linux the other week, gave it a few hours for the self check, booted back into the distro and has been running fine ever since.
Pretty sure windows would’ve just set the computer on fire at this point.
Linux is so strong I turn it off from the power button. Saving 5 seconds.
That’s weak. I always pull on the power cord until the plug comes out. That shuts it down in a second flat.
I was talking about a laptop with non-removable battery of course! I turn off my desktop via Zigbee remote hooked to Home Assistant which flips a Zigbee power switch that the AC power cord is hooked up to. Even faster death than going under the desk and unplugging the power cord. Even just unplugging itself takes time.
I’m a little spoiled by this. I did it on Windows and had to rebuild the boot partition.
me turning off the power supply: (i didn’t have anything open so hopefully it’s fine…)
It’s much less risky than it used to be. Journaling filesystems reduce the risk of filesystem corruption to near zero and are fairly ubiquitous now on non-removable media.
That random systemd service waiting 1.5 minutes.
You all not suspend/hibernate?
This is so fucking annoying. Whenever you try to run something not clearly meant for the desktop, there is like a 80/20 chance that you can completely forget suspend…
Yeah, I was thinking that. I wish we had a button (other than power off) to stop the service immediately.
Mine suspends immediately.
I do
yes | sudo pacman -Syu && sudo poweroff
(Update and poweroff)
Fuck that noise
sudo shutdown 0
turn off NOW bitch!I prefer shutdown now gives me a feeling of power
“&&” will only run shutdown if the update runs correctly.
I do “;” to definitely run the shutdown after the update process exits. (Don’t want to keep the system running if nothing is happening any more.)
I do “|” so it updates and shuts down at the same time
I do “;” to definitely run the shutdown after the update process exits.
If you’re able to successfully boot the machine afterwards is not your concern?
what’s fun in a successfully booting system? we are arch users for a reason!
Well, as I’m using Debian, maybe I’m a more cautious type.
I don’t know about arch but my system usually boots fine after an upgrade. (Gentoo here)
If the update is successful. If there are failures in critical steps, well…
Doesn’t it roll back to a previous state then?
No. It will boot the previous kernel, but the user experience will be at least suboptimal if some packages have already been removed during the upgrade, but the upgrade stopped at some point because a downloaded package was corrupt, leaving lots of dependent packages unconfigured. In case networking doesn’t work, it’s also inconvenient to manually download the affected package on another machine and transfer it with a usb stick onto the computer to restart the upgrade.
You don’t need sudo to run poweroff on Arch, provided there’s no other users logged into the system
And it’s a login shell.
Assuming you enter your password upon running
sudo
, isn’t there the risk ofsudo
’s privilege timing out ifpacman
takes too long to complete? I believe I tried something similar, intending to run a one-liner I could start then walk away from. However, I ended up returning to see the system not rebooted hours later.Or is
yes
somehow supposed to take care of this? Sorry, newish Debian user here who hasn’t ventured outside the distribution much.The command after
&&
runs only if the previous command returns non-error exit status (0), ifpacman
returns error the latter command won’t be executed.Additionally there’s probably a configuration option for
sudo
for it to not time out, but it doesn’t matter since you can just usesystemctl reboot
as a normal user to reboot your system (at least on Debian). If that’s too long I recommend to add this to your.bashrc
(if you use Bash):alias reb='systemctl reboot'
or something similar.Maybe this is just a
yay
thing but I think if sudo priveleges run out while downloading the files it prompts you for your password again before performing the changes. That would lead to it either trying to use theyes
output or getting stuck in the password prompt, only failing in the prior.This entire problem could be solved by just running it as the root user.
Yes, in this
commandone liner, the system should not power off when the update took too long.Or is
yes
somehow supposed to take care of this?No,
yes
is simply answering all questions asked during the update procedure (start upgrade, replace config files, restart services) with “yes”.There’s no timeout for sudo. When permitted, a process runs as root and then closes.Also, the system will still shutdown when update fails because pipes do not care if previous commands exit with a nonzero code, unlesspipefail
is set.Edit: i’m blind.