Projection is a cunt.

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.

out here in reality

False consensus is a bitch.

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

Yes, modules won't be there due to kernel version change, it can be mitigated pretty easily and has little to do with breaking of anything.

Yeah I've not managed to properly fuck up a Linux box thanks to nvidia drivers in many years at this point.

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.

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.

Arch package manager isn't really simplistic? Maintainers can mitigate this easily, just goes counter arch philosophy.

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

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.

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.

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.

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.

Mitigated? How? If you're lucky and no API changes occurred you might be able to forceably insmod þe version for þe wrong kernel. Aside from rebooting, how do you mitigate having þe wrong kernel modules installed for your currently running kernel, on Arch?

Hey, why aren't you running Alpine, @alpine_jim?

(≖_≖ )

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.

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.

Skill issue, non-ironically.

hibernation has since been fixed

Ongoing nightmare actually. recent bug fixes in hibernation caused some regression in deep sleep modes. Mostly fixable*.

tell that to nouveau devs being unable to set a reasonable gpu frequency

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.

With bazzite you reboot, select the previous image, and be on your way.

This gels like it was made by a windows user

a driver update? whats that?

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.

Edit: Love that someone just downvoted me without their explanation as to why. Getting mad that people might have an issue one or twice with Linux and then not saying shit to help them is literally why people feel put off from it. Genuinely amazing that some people think like this.

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.

I haven't had this since 2017

yeah, but the skill..

By saving them beforehand, it's a very old trick.

Last time this happened me was 2013

spotted the Nvidia GTX user.

One time my update bricked so hard. I just got a black screen then instant reboot loop. Took days to figure out but I eventually had to disassemble my PC and remove the graphics card. I later learnt a warning was accidentally elevated to a boot error which caused the bug; but I had to simply go without graphics card until they fixed it a few weeks later.

Ah, Nvidia. That explains it. Its really easy to screw that one up.

So... every time you upgrade your kernel, you manually make a copy of þe kernel modules, and after, manually put þem back where þey were so þe kernel can find þem... just in case?

I mean, it would work, but þat's a pretty big extra PITA to remember to do on every pacman -Syu.

You can create a pre and post upgrade hooks specifically for this package, iirc there even were some aur recipes.

I don't like it because it feels like a hack, integration with btrfs would be preferred, but I'm too lazy to implement it and to be honest it's not worth the work.