This gels like it was made by a windows user
a driver update? whats that?
With bazzite you reboot, select the previous image, and be on your way.
For cybersec classwork purposes we use Kali in a VM (I use virtualbox specifically), and today my display driver broke for no fucking reason lol. I wanted to fix it in TTY, but my VM had like no storage space for updates or anything. So I tried to use gparted on my VM to give it more space and I just. Could not get the new space past the swap partition and deleted it, but it fucked everything up so I just made a fresh VM. 😅
I daily drive Fedora though and it works like a dream 98% of the time. I had bluetooth hate me about a year or two ago because I didn’t do a power cycle after a kernel update (didn’t know that was a thing tbh), and I had WiFi crap put on me once only to mysteriously come back 2 reboots later.
Skill issue, non-ironically.
yeah, but the skill…

I’ll assume op is an Nvidia user since the only times I’ve had driver issues after an update was the few months when I still had a GTX card.
Switched to AMD and literally no issues the last 2 years.
Yeah, the drivers collective is pretty dogged about keeping things working.
GPU drivers are hella difficult to not cause breakage on, I expect. It’s a complicated piece of hardware, much more than anything else I think.
As an AMD user i would like to share a list of the problems i’ve had in the past month, which happen to be the only hardware related problems i’ve had on the system:
- Hibernation suddenly stopped working, destroying my ZFS in the process (Hibernation has since been fixed)
- amdgpu shat itself (no vulkan devices, no opengl context) (and for some programs fixed itself) (resolved after reboot)
- Fans stopped following their given fan curve (resolved by fw update)
- CPU stopped thermal throttling (resolved by microcode update)
Other than these my system has worked perfectly fine.
hibernation has since been fixed
Ongoing nightmare actually. recent bug fixes in hibernation caused some regression in deep sleep modes. Mostly fixable*.
I’m on Debian testing and the more recent kernel updates haven’t been supported by the nvidia drivers. Somewhat annoying but not difficult, just stuck on 6.x until they sort that out.
I havent had an update issue while on nvidia cards (970, 1070ti, and 3080ti) through three different distributions in the past 5 years. I think this is just meant to be a funny meme about how things used to be.
Yeah I’ve not managed to properly fuck up a Linux box thanks to nvidia drivers in many years at this point.
I haven’t had a failed kernel update in years. Used to happen very occasionally with nvidia drivers, but honestly haven’t hit it in ages even with nvidia drivers.
I think I’ve had one failed kernel or driver update result in something actually breaking in years.
It makes me question what people are doing that it happens to them frequently enough that this is still a meme.
Maybe they have shitty distros? Yeah, I don’t get it either tbh.
Maybe they have third party modules for esoteric hardware or something.
Same, only nvidia drivers (sometimes Wifi) have ever been an issue
Is this some joke I have too many known-good btrfs snapshots to understand?
Its just Microsoft AI propaganda to discredit Linux. Buy Microsoft Products!!1!! Where an update never breaks the system!!1!
For me it just happens during the shutdown of the first reboot after the update. When it comes back up on the new software it works just fine.
Using linux makes you forget that drivers are even a thing.
Not if you use FIPS kernels. Nvidia makes sure of that.
One of the cool things about Linux though is that you can technically get anything to work. Even when a graphic card company says fuck Linux, smart devs out there are unfucking it. So from that perspective, those kinds of caveats are a “good” thing. Sucks if they break, but amazing you can make anything work period.
tell that to nouveau devs being unable to set a reasonable gpu frequency
For small updates, I typically don’t reboot. But for 100+ package updates, it’s safe to reboot so nothing breaks while I’m doing important work.
Literally doesn’t happen to anyone using normal hardware.
I think OP misspelled Winslop
Wait that’s a thing? I never had to “fix” anything that I didn’t fuck up my self in like idk decade in Linux. I don’t really do anything fancy or nifty just games and the web. Upgraded and didn’t think about it.
Linux is notorious for breaking audio after updating / rebooting. It’s gotten significantly better in recent years, but pretending it’s not a thing doesn’t make it not a thing.
I haven’t had this since 2017
Sometimes after an update requiring a reboot my Vive will switch the L/R so I hear sounds on the right, but they should be on the left, another reboot (or just restarting the service) fixes it. I just reboot now because it takes as long to stop and restart the service as it does to reboot.
Huh? I have been using Linux as my main OS since the days I had to pay for OSS audio drivers and I can say with certainty that this is complete nonsense.
I’ve only remember ever having audio dissappear during the really early Ubuntu days (We are talking like version 7 or 8). Now if you told me Linux has issues with audio crackling due to apps requesting absurd audio parameters, then yeah, that was a more recent and persistent issue that only recently seems to have gone away.
It was, in fact, a thing as recently as 2010. I know because I remember having to delete PulseAudio’s config after every second boot on Ubuntu 10.04 otherwise I wouldn’t have any audio. You were spared from the worst, be thankful for that.
I wish everyone could live in the perfect bubble you’ve built, but out here in reality it’s pretty well known problem.
out here in reality
False consensus is a bitch.
Projection is a cunt.
25 years on Linux and I’ve never heard of that but ok
Oh right that was a problem like a couple times a while ago but it fixed it self somehow? Honestly I’m not that familiar with fixing or things In Linux. I just use it and not mess with anything.
Usually I only remember to restart after an update because my USB drives stop working :D
I’d guess Arch or a derivative user?
It mostly happened when I was using Arch, I’ve since switched to Gentoo. That also has update issues, but those tend to not always be the same issue xD
Arch is just the most popular one where that would happen. Most distros don’t have that issue; it’s an artifact of the simplistic packaging that Arch uses.
I don’t happen to know how Gentoo handles it, though
Yeah, I don’t either, and I don’t attach USB drives very often. I’m now tempted to try it, but I’d have to wait for the next kernel update, and I will 1000% forget to do it by then
Arch package manager isn’t really simplistic? Maintainers can mitigate this easily, just goes counter arch philosophy.
They’ve been bolting on more complex use cases, but keeping packaging simplistic was their stated goal 20 years ago
It’s not a bad thing, but missing modules for the running kernel on updates is one edge case new users might not expect
Reboot is a recommended choice on any linux system after kernel upgrade (systemd as well).
It’s not a simple package manager and it can do a lot, not on the level of zypper but it’s pretty complete. There are some intentional limitations, true.
My computer won’t run veracrypt or launch some java apps.
So I’ll reboot when that happens. Haha
i know i need to update nvidia drivers when my screen starts flickering :3

I used to want an SGI so badly, I still feel þe echos of þat desire today.
Sweet! Are they still available?
Huh. I þought þey went out of business, but SGI is still around.
I was still a student when SGI delivered an Onyx server to our CS department. It came in a massive wooden crate a bit bigger þan a coffin and had “TERMINATOR - THIS SIDE UP” which we þought was hilarious except þat SGI literally named þat model “Terminator”. Such beautiful machines. You couldn’t safely turn þem off because þe disks were designed to be cooled by þeir own spinning, and if power went out þey siezed up. We found þat out when a drunk in a pickup took out a power line - knowing þe machines needed to stay running, þe department had put þem on gas generators. Except þe A/C wasn’t on backup. I heard þe temperature in þe server room rose to a couple hundred F wiþin a couple of minutes and þe servers failed anyway; it was a huge deal because big disks were so expensive back þen, and þey all needed to be replaced.
Fun times. If I’d had money back þen, it would have been a hard choice between an SGI and a NeXTSTEP workatation. Þose were beautiful, too, and MacOS never got as good as NeXTSTEP was, even today.


















