I’m trying to update through Discover. When I reboot, the offline update loading bar loads in, but none of the text does and then it just reboots. After logging back in I get a notification saying “Failed Offline Update. Failed to download files”
I think the Fedora 44 update didn’t work properly, because I remember having to check the “About this System” in the settings to see if it was actually Fedora 44. But I did that last weekend and don’t remember why I thought it didn’t work.
The system works fine other than this, I just can’t update it.
Lots of us prefer to upgrade using the command line because then it gives out status output so if something goes wrong you have an idea what happened and can ask here for help.
I’d recommend trying to upgrade by following this procedure and see what happens:
Never do the dnf system-upgrade download step when there are errors with the dnf upgrade --refresh step. Fix those errors before proceeding.
Errors in the upgrade must be repaired or the system-upgrade will always fail.
I am reviewing the dnf upgrade data.
did you by chance manually remove the /lib/modules/7.0.4-200.fc44.x86_64/ directory tree. There are many errors reported about files in that tree missing.
There were errors related to the hid-xpadneo module failing to build
>>> Sign command: /lib/modules/7.0.8-100.fc43.x86_64/build/scripts/sign-file
>>> Signing key: /var/lib/dkms/mok.key
>>> Public certificate (MOK): /var/lib/dkms/mok.pub
>>>
>>> Autoinstall of module hid-xpadneo/v0.9-214-g8d20a23 for kernel 7.0.8-100.fc43.x86_64 (x86_64)
>>> Building module(s)...(bad exit status: 2)
>>> Failed command:
>>> make -j16 KERNELRELEASE=7.0.8-100.fc43.x86_64 -C '/lib/modules/7.0.8-100.fc43.x86_64/build' M='/var/lib/dkms/hid-xpadneo/v0.9-214-g8d20a23/build/src' VERSION='v0.9-214-g8d20a23' modules
>>>
>>> Error! Bad return status for module build on kernel: 7.0.8-100.fc43.x86_64 (x86_64)
>>> Consult /var/lib/dkms/hid-xpadneo/v0.9-214-g8d20a23/build/make.log for more information.
>>>
>>> Autoinstall on 7.0.8-100.fc43.x86_64 failed for module(s) hid-xpadneo(10).
>>>
>>> Error! One or more modules failed to install during autoinstall.
>>> Refer to previous errors for more information.
>>> dracut-install: ERROR: could not locate dependency libsystemd-shared-258.7-1.fc43.so requested by '/var/tmp/dracut.dERQm3y/initramfs/usr/lib64/systemd/libsystemd-core-258.7-1.fc43.so'
>>> xargs: /usr/lib/dracut/dracut-install: exited with status 255; aborting
>>> dracut[F]: Resolving executable dependencies failed
>>> /usr/lib/kernel/install.d/50-dracut.install failed with exit status 1.
These problems seem to be warnings and did not actually stop the upgrade. I would repeat the command to do the upgrade with this command sudo dnf upgrade --refresh --allowerasing The allowerasing option should enable the system to remove the obsoleted packages and eliminate those to noted problems.
Problem 1: installed package libavutil-free-8.0.1-6.fc44.x86_64 obsoletes libpostproc-free < 8.0 provided by libpostproc-free-7.1.4-1.fc43.x86_64 from updates
- cannot install the best update candidate for package libpostproc-free-7.1.2-1.fc42.x86_64
- cannot install the best update candidate for package libavutil-free-7.1.2-1.fc42.x86_64
Problem 2: installed package libavutil-free-8.0.1-6.fc44.x86_64 obsoletes libpostproc-free < 8.0 provided by libpostproc-free-7.1.4-1.fc43.x86_64 from updates
- cannot install the best update candidate for package libpostproc-free-7.1.2-4.fc43.x86_64
- cannot install the best update candidate for package libavutil-free-7.1.2-4.fc43.x86_64
Review of the second (system-upgrade) data reveals a known issue with wine related to the upgrade from f42 to either f43 or f44..
The simplest fix is to remove wine, perform the version upgrade, then reinstall wine.
I assume from that error list that you are attempting to upgrade from f42 to f43, but you failed to tell us the details.
It is strange that you had installed packages from f44 that show in #3 above, but seem to be attempting to upgrade to f43. The package versions in several locations are inconsistent for fedora version numbers.
One additional suggestion before doing anything else, since it seems this may be an attempt to upgrade from f43 to f44.
Please run sudo dnf distro-sync --refresh --releasever=43 --allowerasing
That should get every thing that may be an error there fixed before attempting to move forward.
Updating and loading repositories:
Fedora 43 - x86_64 - Updates 100% | 15.6 KiB/s | 27.8 KiB | 00m02s
RPM Fusion for Fedora 43 - Nonfree - Updates 100% | 3.9 KiB/s | 5.9 KiB | 00m02s
RPM Fusion for Fedora 43 - Nonfree 100% | 4.3 KiB/s | 6.1 KiB | 00m01s
RPM Fusion for Fedora 43 - Free - Updates 100% | 2.6 KiB/s | 3.4 KiB | 00m01s
RPM Fusion for Fedora 43 - Free 100% | 2.8 KiB/s | 3.4 KiB | 00m01s
ProtonVPN Fedora Stable repository 100% | 5.5 KiB/s | 3.0 KiB | 00m01s
LibreWolf Software Repository 100% | 7.0 KiB/s | 3.8 KiB | 00m01s
Fedora 43 openh264 (From Cisco) - x86_64 100% | 871.0 B/s | 986.0 B | 00m01s
Fedora 43 - x86_64 100% | 34.0 KiB/s | 29.5 KiB | 00m01s
Repositories loaded.
Failed to resolve the transaction:
Problem: The operation would result in removing the following protected packages: grub2-efi-ia32, grub2-efi-x64, grub2-tools-minimal, plasma-desktop, selinux-policy-targeted, setup, shim-ia32, shim-x64, sudo, systemd, systemd-udev
You can try to add to command line:
--skip-broken to skip uninstallable packages
Adding --skip-broken didn’t change anything. I also removed libpostproc-free . Now running sudo dnf upgrade --refresh works without errors (says Nothing to do), and sudo dnf system-upgrade download --releasever=44 has the same output as before.
I am already on 44, I upgraded from 43 last weekend but I don’t think the update worked. I have not manually removed /lib/modules/7.0.4-200.fc44.x86_64/. I can try manually removing wine.
Yes I missed the final option in that command.
It now would read sudo dnf distro-sync --refresh --releasever=44 --allowerasing --setopt=protected_packages=
Newbie here. Akseli on KDE said to say here that this method worked for me. I had the same Failed Offline Update, too. I copied the solution, specified the 43 is 44, then the terminal did the rest, and it worked. Now I don’t see any more of that dialog. Except now I will have to figure out how to fix the “space” that crash dialog shows up after restart. smh
