I hope you all are having a good day. There is an issue that I have been facing for quite some while now, which I would like to report.
In my system, often times,
sudo dnf upgrade --refresh fails to list the available updates. It returns me the message that “Nothing to do.” However, GNOME Software Centre shows me that quite a few updates are available.
I don’t like upgrading from the software centre as it demands me to reboot my system and do note that this issue has cropped up recently (a month or two).
Why is this happening? What can I do to fix it?
Thank you all.
Gnome-software and dnf are not always in sync. Gnome software does not use the same metadata as dnf, so if you’ve run dnf and your system is already up to date, Gnome software’s information may be out of date. To update the metadata that Gnome-software uses, try:
$ pkcon refresh
(This is the packagekit command line interface)
@FranciscoD Thanks for the reply. It would be understandable if GNOME software centre would be out of date. However, surprisingly, it is the dnf that is out of date often and Gnome software centre displays the available updates. Do you know why this could happen?
[Note: I have run the command mentioned by you and I shall wait to see if it brings any positive impact]
Yes, it simply depends on which—gnome software or dnf—updated its metadata most recently. I only use dnf, and my connection allows me to refresh my metadata cache each time I run it. I ignore gnome-software’s notifications completely. I even use
flatpak update in a terminal to update those
The idea is to remain consistent. Use whichever, but don’t mix them.
Hey, I waited for sometime to notice any inconsistency in the system, and unfortunately, I did find them. This is the issue that I have been talking about. Have a look:
Any idea how to solve it? I have a feeling something is wrong in my system.
No, as I said, there is no reason for the two to be “consistent”. Whichever has it’s metadata updated most recently will be correct. If you click the “refresh” button in the gnome-software window at this time, it will also refresh its metadata and not show you any OS updates.
The second pane in gnome-software is for your Flatpaks. DNF does not deal with Flatpaks at all, so it will not show any information about these. To update your Flatpaks from the terminal, use
If you click on “OS Updates” a list of packages to update should appear.
Then you can look the proposed new version numbers, and compare them to the actually installed ones (via
I have a similar problem, but with version 32.
Decided by changing the entry for the baseurl variable:
Home - MirrorManager find good for me;
- $ sudo vim /etc/yum.repos.d/fedora-updates.repo;
- comment string #metalink=https://…
and add new string, something like it:
Now, imagine every community member would point to that server…there is a reason for having a worldwide network of mirrored servers.
If you want to check for updates more frequently, just refresh your metadata manually:
sudo dnf update --refresh, or do a
sudo dnf clean all && sudo dnf update to see if another mirror has updated packages for you. Normally an update can wait for a day, no?
Moreover, I think your ‘solution’ does not fix inconsistency between PackageKit and dnf metadata.
You are right, this is not a good solution. It’s important to understand why it doesn’t work with metalink.
Unfortunately sudo dnf update --refresh, or do a sudo dnf clean all && sudo dnf update did not help.
If you are hitting a particular mirror and the mirror isn’t up to date, please file an issue with the infrastructure team here. They will be able to see why the mirror isnt syncing: