Fedora Account System
Red Hat Associate
Red Hat Customer
Gnome Software shows that everything is-up-to date and metadata being refreshed. On shutdown dialog, Gnome asks if updates should be installed offline, despite system being up-to-date. Reproducible: Always Steps to Reproduce: 1. Start Gnome Software 2. Update packages 3. shutdown by clicking through Gnome buttons Actual Results: Its asking whether updates should be installed offline Expected Results: Dont ask, system is already up to date.
Created attachment 2139966 [details] screenshot
Created attachment 2139980 [details] same screenshot but changed system language to EN Sorry, system language was German before, I switched to EN to provide you with a proper screenshot
Thanks for a bug report. It looks like the dnf5daemon-server "thinks" it still has some updates to apply. How did you do the last update, please? Maybe the dnf5daemon-server or dnf command line failed to clean-up the offline update state for some reason. If you can still reproduce, what does /usr/lib/sysimage/libdnf5/offline/offline-transaction-state.toml contain, please?
I used dnf update to update my system. Unfortunately, I can't reproduce, and I have since restarted the VM. Will keep an eye on it and post /usr/lib/sysimage/libdnf5/offline/offline-transaction-state.toml should the problem re-appear.
Thank you for the update. I tried it here with dnf5-5.4.2.0-1.fc44.x86_64, the toml file is not created with `dnf update`, it is created only with `dnf update --offline`. When I do not reboot the machine and run `dnf update`, then the gnome-software properly shows there are no package updates, but the toml file is still there, with state `download-complete`, which is an indication "the update is prepared, it can be scheduled for the next boot". That's noticed in the gnome-shell restart/power-off dialog and you get what you see. The gnome-software prepares offline updates under the hood, thus you did not necessarily need to run `dnf update --offline`, it could be the gnome-software preparing the offline update, then you "overwrote" it with the `dnf update`. I'm moving this to the dnf5 folks, the problem is that the plain `dnf update`, or any other non-offline updates invoked through the dnf command line, should invalidate the prepared offline update, or at least not claim in the offline-transaction-state.toml that the packages are downloaded (even they can be downloaded, it's just that they are not meant to be installed, because they are already installed).
Or dnf5 could to it other way around: reject any modifying operation if an offline update is scheduled.
I vaguely recall seeing some warning or such about prepared previous offline update, but maybe it shows up only with `dnf update --offline`. I'm sorry, I do not recall any better details.
Yes, stacking multiple offline updates is already prevented. Related upstream request <https://github.com/rpm-software-management/dnf5/issues/1655> actually requesting more sharing.
This is not much about sharing (downloaded packages, or cache with the command line and dnf5daemon-server), this is more about invalidating offline update state when the update was done by other means (dnf update/distro-sync/you-name-it). PackageKit is sometimes "overaggressive" with invalidating prepared offline updates, even it may make sense when a package is added or removed, even it would be nice to rather not panic in such case when applying the prepared offline update, which may contain packages which are not installed on the machine anymore.
Should be fixed upstream by https://github.com/rpm-software-management/dnf5/pull/2736
FEDORA-2026-958b875d17 (dnf5-5.4.3.0-1.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-958b875d17
FEDORA-2026-958b875d17 has been pushed to the Fedora 44 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-958b875d17` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-958b875d17 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-958b875d17 (dnf5-5.4.3.0-2.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.