133
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 21 Jan 2026
133 points (100.0% liked)
Linux
13407 readers
254 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
I'm using Fedora KDE, and for the first time in my life, an upgrade (42 to 43) completely borked the system, in a way that I couldn't boot to anything else other than a kernel panic.
I had to boot up a live USB, mount and chroot into the old system, and manually fix each duplicated / corrupted package. And it still caused every now and then some weird issue with dnf, so in the end I just reinstalled the entire OS.
I feel like updates "offered" via a nice and convenient gui shouldn't really do this out of nowhere - and I wasn't the only one to report this in the past half year.
I found on the 42->43 upgrade, Wine 32-bit was removed, and the upgrader errors out instead of fixing it. What I did to fix was immediately, manually (via dnf) uninstall wine*, then immediately run the upgrade again, and it fixed itself, finishing the upgrade with 64-bit Wine installed.
Sure would be nice if they caught and fixed that before pushing the update and requiring users to do it themselves.
I ran into the same issue with errors every time I tried to update. This fix worked perfectly, thank you for taking the time to comment!
Sorry you had to go through with that.
Point-release distros like to tout stability, but they face all the same problems as rolling-release distros when upgrading between versions.