Hmmm… 🤔
You must log in or register to comment.
NGL, some distros will give you the anxiety that the next update will brick your OS as well
Well I updated my computer and my audio stopped working; to the logs! Lol I love Linux, but find myself asking “what now?” much more frequently with it…
With windows it is more like “wtf is this new ad on my start menu?” Or “how can I opt out of all these features no one ever asked for?”
One time an update broke audio, and I spent like 15 minutes digging around in pipewire logs and weird config parameters before I realized that I was literally just muted lol. Pulseaudio has irrevocably conditioned me to assume that whenever there is no audio, it must be some obscure bizzare weird issue instead of something simple
btrfs subvolume snapshot / /snapshots/backup1lolWon’t save you from a bricked bootloader tho haha
Laughing in NixOS…
Sigh… c/linuxmemes continues to leak
Can’t search for converts in a circle jerk.
Linux Syndrome:
When nobody asked but somehow the solution is Linux.
If you browse linux communities long enough, you eventually start seeing openbsd users who condescendingly speak about linux the same way some linux users speak about windows lol. It’s turtles all the way down!
I haven’t seen a blue screen in years.
Yes, Linux Preachers, I am a Windows user.
I’ve seen one recently, when I kicked my computer by an accident.
“by an accident”…
I saw that happen once in a big presentation.
There was a team of students presenting their work to ~200 people. Right in the middle, a pop-up says updates are finished and the computer needs to restart. It has a helpful 60-second countdown, but “cancel” is grayed out, so all they can do is watch.
I was only in the audience and I still have nightmares.
shutdown.exe -ashould take care of situations like that. It’s not an excuse for taking away your options on the UI though.Does that require admin access? It wasn’t their machine, it was one the school provided for the auditorium.
By default a normal user can abort the shutdown. They could also configure group policy to prevent shutdown permissions which also prevents aborting a shutdown.
The GPO is
Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment > Shut down the system.
Greyed out options like that almost always mean the person has been hitting cancel or delay for several warnings already.
This wasn’t their machine, it was one the school provided for the auditorium.
I don’t want to be that guy, because I still hate Windows, but… most people who have these problems just didn’t set up updates properly. Well, that, or they never restart their computer.
Windows user here. I don’t have a fear of BSODs.
On the other hand, I have “Linux users are elitist jerks” syndrome, which stops me from switching to Linux, due to a fear of Linux users might be elitist jerks. This can be only cured by massive improvements to the Linux community, and a debugger that has an actual GUI for Linux (no, I don’t care about whatever cute little script you’ve written for GDB for a semi-automated testsuite for command line utility that converts one obscure format into another).
deleted by creator
Linux elitists will do anything before admitting the usefulness of GUIs, because “muh skripz”.
I’m a Linux user, and you’re being an elitist jerk. Knock it off.
I dislike Microsoft, that doesn’t make me a elitist
I’m a Linux user, and I have “X11 decides to lock up the entire system irrecoverably for no reason” syndrome. Should probably look into wayland…
X does fall over sometimes. Since I’ve been on Fedora KDE running Wayland, I’ve had a couple “you’re now in recovery mode” moments as well.
Since when did the Blue Screen concept change from being an actual error screen to simply the Windows update screen?
I’m guessing shortly after Windows began implementing aforementioned update screen?
This is the first I’ve heard it referred to as the Blue Screen.
For reference: https://wikipedia.org/wiki/Blue_screen_of_death
Linux will have an equialvent of BSoD soon. https://www.phoronix.com/news/Linux-DRM-Panic-QR-Codes
99 percent of the time I’ve had to deal with a bsod in Windows, it was a bad driver (Intel controllerless Wi-Fi, for one) or a software issue (Malwarebytes Premium or Kaspersky + insert networking app here). Sometimes it’s a hardware problem (stupid ASUS laptops with builtin RAM), and rarely, a bad disk clone (gotta do that bcdboot)
Fresh memes just for this post
I cannot remember the last time I had a blue screen
My kernel panics in fear of Blue Screen syndrome.
