Hi, I am using a KDE based F41 and I’m trying to upgrade to F42 in vain. I would need some help to fix that.
I issued the following commands without any apparent issue:
sudo dnf upgrade --refresh
sudo dnf system-upgrade download --releasever=42
sudo dnf5 system-upgrade status
An offline transaction was initiated by the following command:
dnf system-upgrade download --releasever 42
Run \`dnf5 offline reboot` to reboot and perform the offline transaction.
So I issued this command:
sudo dnf5 offline reboot
The system reboots but no update is happening. Just before the reboot I see the following message on the screen (not sure if that is relevant)
Thanks for your response.
I also tried the clean command a couple of times and it didn’t make a difference.
The upgrade through KDE Discover seems to download everything needed then when I restart nothing really happens.
Could this be a problem related to the fact that the disk is encrypted? What log files are there which I can check?
It seems to me that the installation of the downloaded packages is not done after reboot.
I did a: sudo dnf offline clean again before executing the other commands as above.
I’ve run a system upgrade on Fedora KDE 41 VM without disk encryption, and it obviously went through (though it seemed unresponsive for about 10 minutes, without progress outputs).
What happens when you run the sudo dnf offline reboot command? It just boots up into the previous F41 system?
Also, journalctl around the time of the offline reboot might give some hints.
Thank you @tqcharm for taking time to respond and offering guidance.
The system rebooted, then I saw grub menu, then the disk encryption password was requested, I entered it, the system rebooted again… and I was back on the SDDM login screen. Nothing got installed apparently.
This is what I saw while trying to go through the journalctl. Could you please recommend where to look and/or what to do next please?
That’s a bit strange. I wonder if it is an issue that dnf4 (/usr/bin/dnf-3) seems to be requested to perform the offline upgrade, and hence the No module named 'dnf' error:
I decided not to remove the packages above as they had all sorts of dependencies and I wasn’t sure about what to remove and what to keep.
However, I redefined all files /usr/bin/dnf* to point to /usr/bin/dnf5 and tried the upgrade again but without clean and this time upon reboot I saw briefly a screen where updates were getting installed, but then the system rebooted and eventually no upgrade happened.
Here’s what I found in the journalctl:
Apr 17 07:59:58 fedora pk-offline-update[1604]: assigned role
Apr 17 07:59:58 fedora dnf-3[1601]: Unknown argument "upgrade" for command "system-upgrade". Add "--help" for more information about the arguments.
Apr 17 07:59:58 fedora systemd[1]: dnf-system-upgrade.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 17 07:59:58 fedora systemd[1]: dnf-system-upgrade.service: Failed with result 'exit-code'.
Apr 17 07:59:58 fedora systemd[1]: Failed to start dnf-system-upgrade.service - System Upgrade using DNF.
Apr 17 07:59:58 fedora systemd[1]: dnf-system-upgrade.service: Triggering OnFailure= dependencies.
Apr 17 07:59:58 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf-system-upgrade comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? a>
Apr 17 07:59:58 fedora dnf5[1602]: Trigger file does not exist. Exiting.
Apr 17 07:59:58 fedora systemd[1]: Starting NetworkManager.service - Network Manager...
Apr 17 07:59:58 fedora systemd[1]: Starting dnf-system-upgrade-cleanup.service - System Upgrade using DNF failed...
Apr 17 07:59:58 fedora systemd[1]: Starting packagekit.service - PackageKit Daemon...
Apr 17 07:59:58 fedora systemd[1]: dnf5-offline-transaction.service: Deactivated successfully.
Apr 17 07:59:58 fedora systemd[1]: Finished dnf5-offline-transaction.service - Offline upgrades/transactions using DNF 5.
Apr 17 07:59:58 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf5-offline-transaction comm="systemd" exe="/usr/lib/systemd/systemd" hostna>
Apr 17 07:59:58 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf5-offline-transaction comm="systemd" exe="/usr/lib/systemd/systemd" hostnam>
Apr 17 07:59:58 fedora PackageKit[1634]: daemon start
Apr 17 07:59:58 fedora systemd[1]: Created slice user.slice - User and Session Slice.
I’m going to try one last time to do the whole clean thing and see what happens and update this message afterwards.
I know this is a lot of work, but I wonder if this issue would replicate on your hardware if you do an F41 fresh install and then upgrade, then system-upgrade to F42. If it’d still replicate, then it would be certainly an issue worth reporting.
I wanted to thank you for your help.
As I believe I have reached a dead-end on that very issue, I’m considering doing a fresh install of F42.
I already had issues with KDE Discover after my F41 fresh install. Basically every time I attempted to update through that software everything seemed to work fine then after a reboot, I would get a message that the updates failed. I didn’t bother investigating as updates were working just fine using DNF.
Probably an existing issue then, which became a blocker with the F42 upgrade.
Hope you’ll enjoy F42 after the fresh install.
PS: If you’re with KDE, you could also give Kinoite a try. Being an atomic desktop, it’s less configurable, but system-upgrades rarely come with issues.
Thanks @tqcharm ,
I made a fresh F42 install and restored my settings and backed-up files with no major issues encountered.
I am updating this because I think I know what might have caused the issue.
At some point on my F41 I downgraded python and I manually changed the simlinks /usr/bin/python and /usr/bin/python3 to point to the downgraded version of python instead of the original one which came with F41.
