On my new Lenovo with a brand install of Fedora, DNF was reporting 10KiB/s disk writes when installing packages. That was a long long upgrade but fortunately all that got fixed by the upgrade.
What is stable? I just run nix flake update then brew a coffee to accompany me for the next 12 hours
Windows: You got a kernel panic from an update just once this week? I went through two BSODs today!
Mac: It’d happen more often if I actually had software! You get everything!
Arch: While getting updates can cause crashes sometimes, new stuff is fun.
Debian: You guys are getting updates?
What? I never had an update break my system on Arch, even with nvidia proprietary drivers.
2-3 years ago, an update to GRUB completely fucked the bootloader on Arch systems. I remember it well because it was the only time I was thankful for choosing Manjaro (which receives updates on a delayed schedule).
(edit) Found it! https://archlinux.org/news/grub-bootloader-upgrade-and-configuration-incompatibilities/ A breaking change in the GRUB configuration caused systems to become unbootable. Manual intervention was required to regenerate the config files (I think it was supposed to be handled by a pacman hook but can’t be sure).
Upgrading on arch involves looking at the arch news. And IIRC, there was also a warning for some time when upgrading grub. So, assuming people who use arch, btw, use it properly, I don’t see the issue.
I’ve had two instances in the past year on Purple Arch (Endeavor) where a kernel update “broke” my system. In both cases, the system still booted fine though, so not all definitions of "broken"may apply.
The first time there was a bug with the kernel drivers for my wireless card which caused a component of Network Manager to lag out the entire UI to the point it was basically unresponsive trying to find a connection, but never did.
The second time, it was a bug with the Vulkan drivers that caused all my games to crash within 60 seconds of starting up. Games are the main thing I use my PC for, so my system was effectively “broken”, even though everything else was fine.
I am of course not discrediting your fortune - I merely wanted to share
Yea, that is not your system broken, but just an package update that was faulty, and probably fixed with an update a few hours later, isn’t it?
And you were able to role back such packages with yay/pacman, I suppose?
Yeah, kernel rollback fixed things no problem
Debian: You guys are getting updates and crashes?
Oh we get updates, after all the other distros have spilled their blood all over them for us first. Why do you think they call it bleeding edge?
Backports don’t count
😮why?
Next update: the same thing breaks again. After searching forums, you notice a pattern going back to 2002.
In my experience the only times I’ve had a stable experience was
-
when I actually only installed packages I needed i.e using a window manager instead of a DE (and no bloat packages which I’ll eventually lose track of)
-
using an atomic distro, my favourite so far has to be bluefin which is part of the Ublue project based on Fedora Silverblue. NixOS is also great but it gives me the urge to pointlessly tinker instead of getting actual stuff done.
In the past I’ve seen flatpaks and containers as bloated and messy solutions which tainted my computer but now that I’ve tried it, It’s actually very convenient.
I’ve always installed a crap ton of packages for gaming which turns into this inevitable mess, but with containers I just use
bazzzite-archand be done with it. It wraps all my gaming packages in one neat container.-
Me hoping 6.13 fixes the AMD iGPU issue introduced with 6.12.
Go back to 6.11
I updated the the other day and now my system boots to a grub prompt; I have to type
exitand then it starts normally.I’d figure out how to fix it, but I reboot so infrequently that I keep forgetting about it.
I feel like running
grub-mkconfig -o /boot/grub/grub.cfgwould probably fix that.Disclaimer: I mostly have no idea what I’m talking about.
Yup! That’s definitely the solution
Disclaimer: me neither
When my arch testing prod server reboots cleanly after a kernel update
It’s a meme because it’s made up and never happens /s
It definitely happens if you upgrade to the next version of your distro while it’s still in beta.
You hit a bunch of bugs, and they actually do get fixed around final release time.
Once you’re on a stable branch, updates rarely include major changes.
I had this when going from Ubuntu 20 to 22 last week. Luckily the universe made sense again when going from 22 to 24, breaking halfway the installation and putting my laptop in a fucked up state between 22 and 24. Caused me a whole afternoon of headaches
Lol, I run Alpine Linux on edge and nothing ever breaks on reboot.
What is there even in alpine, that can break? /s
Only what I install and little else?
Famous last words :p
Is this some sort of Arch joke I’m too stable and usable to understand?
I’m in the 4th box where there’s nothing to do so you try something new and botch up systemd or netplan or something enough to warrant a fresh install and start again
For what it’s worth last time I broke an update fixing it ended up fixing a bunch of other issues I was having.
