I’m on Fedora Workstation 43 and trying to upgrade to 44 , but it keeps failing.
Same thing actually happened when I upgraded from 42 → 43 , so this is like a repeating issue for me.
What happens
dnf system-upgrade download --releasever=44 works fine
I run dnf5 offline reboot
system starts upgrading, installs a LOT of packages
near the end I see stuff like:
Non-critical error in %posttrans scriptlet
then:
Transaction failed: Rpm transaction failed.
system reboots → I’m still on Fedora 43
So basically → upgrade runs → fails → rolls back → nothing changes
What I already tried (from guides + help)
disabled all COPR repos
removed some conflicting packages (like wcurl )
cleaned cache
retried upgrade multiple times
checked logs (but I don’t fully understand them)
noticed a LOT of .i686 packages (probably from Wine)
planning to remove Wine completely since I don’t use it
It is not very likely it really rolled back the update. The kernel version itself doesn’t really say which Fedora version you are running, as the Fedora 43 and Fedora 44 kernel are basically the same version. It looks like there were some isses with the kernel update, so the question is: did the regular updates update the kernel properly?
You can run some checks:
Run cat /etc/os-release to see which version that indicates
Run dnf check if there are any pending issues with the installed system
Run dnf repolist to show which version of the repositories are used
As for wine and the .i686 packages, it would be good idea to remove them if you won’t use wine anyway.
Some packages includes pieces of script code which are run during certain stages of the installation. Post transaction scriptlets are run after all the packages are basically installed. The post transaction scriptlet for kernel-core runs the configuration changes to make the new kernel bootable.
That is missing the “updates” repository, so perhaps the system was not fully up-to-date before running the upgrade to version 44. Also I can’t explain how after running the updates to 44 it would still refer to version 43, so there must be something else going on, and I have no clue what that could be.
In addition to @vgaetera 's comment here the link to the quick-doc which gives you a bit more explanations, to get the guidance you asked for
Could it be that you installed a pre-release once (beta version) and updated to the stable version?
As you see above, the second link is distro-sync which does the following:
Using distro-sync to resolve dependency issues
The system upgrade tool uses dnf distro-sync by default. If your system is partly upgraded or you see some package dependency issues, try running another distro-sync manually to see if this fixes the problem. This will attempt to make your installed packages the same version in your currently enabled repositories, even if it must downgrade some packages:
sudo dnf distro-sync
Beside of checking the log files as proposed from others, have also a look if you have enough space where the kernel gets stored (/boot).
lsblk -f #if sizes get close to 95% (FSUSE%) this can interrupt your upgrade too.
And also the /boot partition got an upgrade in size the last few versions. From 1GB to 2GB. If yours still is1GB or smaller, take in consideration to resize the partition before finishing your upgrade. But please not forget to update your impotent data in case something goes wrong.
