NGL, some distros will give you the anxiety that the next update will brick your OS as well
memes
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to [email protected]
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads
No advertisements or spam. This is an instance rule and the only way to live.
Sister communities
- [email protected] : Star Trek memes, chat and shitposts
- [email protected] : Lemmy Shitposts, anything and everything goes.
- [email protected] : Linux themed memes
- [email protected] : for those who love comic stories.
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/backup1
lol
Won't save you from a bricked bootloader tho haha
Sigh⦠c/linuxmemes continues to leak
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.
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
I haven't seen a blue screen in years.
Yes, Linux Preachers, I am a Windows user.
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.
Or you just decided to update all your packages like a madman whilst not running on a Debian based distro
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 -a
should 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.
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.
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
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. :)
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...
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
Unfortunately as a linux user you may get stuck-on-post syndrome but there are widely available immunizations and treatments available.
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)
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.
This is what got me to switch to Linux (arch btw). I was getting blue/green screens 1-2x a week and it almost always ruined a gaming experience.
Now I can bork my system during an update, but at least I can game smoothly. My system hasn't crashed once while in the middle of something (I have, however, fucked up my system post update and without a Time shift backup ready to go which merited a full reinstall - but it's been a good learning experience overall)
I used to dual-boot and use my Win10 for gaming.
But in the middle of Vermintide 2 I kept getting BAD BSoDs seemingly at random! None of the typical steps seemed to help. Probably something NVIDIA related I dunno.
I was gonna "refresh this system" and all Windows told me after "We're getting this ready." was: "Can't. Dunno why. Sorry."
But hey, switching over to my OpenSUSE Tumbleweed install made the game play really smooth, and no crashes! And soon, I discovered it ran all my other games just fine or even better as well!
I haven't touched that Win10 install in ages, and will probably drop it in favor of VMing it really soon.
The only real holdout is that my VR headset is WMR. That really sucks. :(