Hmmm… 🤔
You must log in or # 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
This is definitely a thing!!
We’re using Linux so we just assume it’s some highly technical issue right off the bat lol. This has caught me a few times. 😂
btrfs subvolume snapshot / /snapshots/backup1lolWon’t save you from a bricked bootloader tho haha
Once I manually deleted a snapshot folder because I didn’t see it listed, and thought it was “orphaned” and just taking up space. :D
“SUDO THAT SUCKER!!” 👉
OS says “Okie dokie boss.”
Suddenly none of my commands are working.
Turns out I deleted the currently mounted active snapshot . Safe to say it was reinstall time.
Don’t go manually touching system files, folks. 😂
Laughing in NixOS…
Sigh… c/linuxmemes continues to leak
Can’t search for converts in a circle jerk.
Won’t convert people with circle jerk arguments either.
Other cures include literally just restarting your PC once a month so it can install updates.
Or disabling the stupid power settings that mean a shutdown isn’t a shutdown, and turning your computer off when not in use
It’s hilarious that so many issues in Windows can be fixed with a restart but then they made it not actually restart when turned off and on again.
My understanding (unless they’ve changed it) was that a restart is a restart because software (either the OS or 3rd party software or both) may need the computer restarted to finish installing or updating stuff.
I’d heard that a shutdown wasn’t actually a shutdown, though.
That’s right, that’s what I meant to say haha but it wasn’t worded great.
I mean, I use Linux but I’ve used a lot of Windows in the past. I don’t find either of them particularly more stable than the other. I had blue screens a few years ago on my laptop and that turned out to be faulty RAM. I haven’t had a Windows-caused BSOD in years. And all this talk of Windows suddenly starting an update while I’m using it, I’ve literally never had that happen.
Not sure how you have avoided that one. It’s been a thing since windows 7
You avoid it with a better license than the cheapest home edition.
But it, like, turns itself off when I’m not using it. Why do I need to restart it?
🤦♂️
Or weekly, just to be safe
It’s windows. You’ll not have a choice in restarting at least once every couple of days.
It’s nowhere near that frequent.
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!
wait till u hear what the templeos people have to say about openbsd
But this isn’t a linux community though, it is a meme community.
The linuxmemes are on a different community.
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”…
youre fake, i used windows daily for the last year and I got one at least once a month. Maybe I was using it wrong though, idk.
That sounds like a user error issue. I use windows at home and work and I also haven’t seen a blue screen in years.
I assume that like 9/10 comments in here won’t be serious. Why are you all taking it so seriously? Yes, windows is very good and it’s rare to have a blue screen now, compared to the good old Windows XP days…
Ya got bad hardware friend, the only time I’ve seen a BSOD in the last few years was when something on my work laptop went bad and it had to be replaced. I haven’t seen a BSOD on my personal machine since my last DIMM failure.
Don’t know what you’re doing wrong. I abuse the hell out of my computer and the last time I got a blue screen was… 2021?
You suck at computers.
Sounds like your hardware is fucked more than anything
it is, got it from school and changed nothing. that’s how you know its bad.
Skill issue
Change your ram
sadly, anti consumerism nowadays makes that very difficult in many laptops.
If you happen to see blue screen on Windows, it’s most likely a hardware or driver problem. It is not Windows 9x days when a user program could take down whole OS with ease.
fake, this is a conspiracy.
and I got one at least once a month.
According to this post, that’s the monthly update Microsoft releases.
/j
Linux machines don’t crash unexpectedly, because if they do, it’s your fault for configuring it wrong and you should have expected it.
Windows machines don’t crash unexpectedly because it’s Microsoft and you should have expected it.
Hum… Hardware does still fail at random.
And that is the main cause of seeing a BSOD.
It’s really not. But it’s the main cause of a kernel panic if you don’t use nvidia hardware.
Or you just decided to update all your packages like a madman whilst not running on a Debian based distro
Bruh, if a package update breaks something, I just roll back the BTRFS snapshot.
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.
What about all those update skippers that start complaining to Microsoft when their system breaks because they don’t understand that updates are crucial for a good running system?
I get why Microsoft forces it now on the Home editions.
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.
And someone still had to configure that
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.
Sure, because Linux never has hardware crashes …
Blue screens were much more common back in the day, I guess nowadays they’re equally stable. Windows current issues are the deliberate choices Microsoft makes
I currently have a memory or CPU issues (I have not investigated), which causes my windows install to lag out for a second, but my Linux install just completely crashes the entire system
No hesitation, pure feedback
I have crashed Linux before. On a Raspberry Pi. I was fucking around with some electronics on a breadboard, hooking them up to the GPIO pins while the thing is running like a dunce, and a male jumper wire connected to Vcc got away from me and dragged across the circuit board near the SoC.
It came back up after I power cycled the board. I’ve otherwise never actually crashed Linux. I’ve crashed software running on Linux, sure, but I’ve never seen a kernel panic in 10 years of penguin flavored computing.
For a while, Linux Mint was significantly less stable than Windows 10 on my previous laptop. Worse, sometimes the system crash would freeze *everything, where it wouldn’t even let me do the CTRL ALT F1 to get a basic shell, so the only solution was a full power off/on
That is painful. It’ll work SO WELL on a bunch of systems but sometimes someone has a particular config that’ll throw monkey-wrenches all over. It always feels like the most rotten luck being on the other end of that huh? :(
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).
“Linux users are elitist jerks”
Elitist jerks are elitist jerks. Ever talked to a stuck-up Windows I.T admin? The constant scoffing is unreal.
What about people rich (or financially goofy) enough to obsess with Apple products?
I think most community people regardless of OS just wanna be helpful and enthusiastic. (I like the word “enthusiast” haha) You’ll always find elitists around topics that involve learning skills and mastery.
I dunno, I’m just happy sometimes people care here when I enthusiastically ramble to them about all their Linux-y choices they can solve problems with lol. We’re not all like that.
Jerks just stick out more. Don’t let them tint your opinion of an entire community. I managed to even enjoy ranked League of Legends for a short while because I didn’t assume everyone was out to attack my ego with theirs.
Hope you have an awesome one and let us know if we can help you with anything. :)
deleted by creator
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
Linux elitists will do anything before admitting the usefulness of GUIs, because “muh skripz”.
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
I think the whole thing might be a joke? 😀
Unfortunately as a linux user you may get stuck-on-post syndrome but there are widely available immunizations and treatments available.
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)
Linux will have an equialvent of BSoD soon. https://www.phoronix.com/news/Linux-DRM-Panic-QR-Codes
I’ve had a black screen of death on Mint. All I was trying to do was crop a video on kdenlive. It black screened on me and somehow even messed up the boot menu so that my Mint was showing up as just Ubuntu. I went straight back to Shotcut after that. I really wanted to switch from Windows to Linux, but so far, Linux, or at least Mint, really hates me. Up till recently, I was still using Mint for my music storage, but it has trouble even moving files onto my phone now. I’ve pretty much given up.
if want to diagnose black screen, can use
sudo journalctl -S "TIME"to see journal since TIME (“X min ago”, timestamp, etc.). may have message on error.can try syncthing to move file to/from phone
Journal won’t be helpful in case of kernel panics.
I’ve used Windows since the late 90s and I’ve had infinite blue screen loops before. probably a hardware issue but it’s not like this fear is irrational.
Seemingly once a year my windows machine goes into an infinite loop of bluescreens. It’s because of my wireless/bluetooth card everytime.
Windows will update the driver during one of it’s bug updates, fail, then I have to go into safe mode and install the correct driver. Then it’s business as usual.
Windows doesn’t seem to care that I told it to never update my drivers, it’ll still do it once a year.
For me, it’s not that Windows updates my drivers during a big update. It’s simply that Windows broke the driver while installing a big update.
I’ve had it happen where my Wi-Fi driver broke so it could only connect to an unprotected network. So I’d simply setup my phone as a hotspot and download the Wi-Fi driver from the manufacturer’s website and reinstall it. That’d immediately fix the issue. Though, actually, that issue hasn’t occured in years. The last time it happened, I think, was in the early years of Windows 10.
