KDE Discover shows updates that dnf cannot find

Ask Fedora
, , , ,
1

I run a script every day that checks for updates for RMP and flatpack packages.
I have just rebooted the computer after a kernel update. KDE Discover shows me many new updates that my script cannot find.
I use dnf update in the script. An attempt with dnf check-update was also unsuccessful.
How can it be that my script does not find these updates, but Discover does?

2

Are the listed updates for flatpaks? DNF does not check for flatpak updates.

2 Likes
3

My script also checks for flatpack updates. Looking at the Discover list, these are mainly KDE related updates. It’s not the framework update which I’ve done already.
I wonder what update mechanism Discover is based on?

4

Discovery is based on packagekit.
Does your script use the --refresh option with dnf?

1 Like
5

Does your script use the --refresh option with dnf?

Thanks for the hint. I was looking at dnf --help, but I overlooked thisoption. With --refresh, dnf finds the missing packages. I have already changed my script.

Discovery is based on packagekit.

Thanks again. Looking at the packagekit page, I found this:

The actual nuts-and-bolts distro tool (dnf, apt, etc) is used by PackageKit using compiled and scripted helpers.

On Ubuntu, using my script always triggered Discovers’ new package detection. On fedora, the app apparently uses a different package cache.

Your answers have really helped me a lot. I have been a Windows Admin for many years. Now I’m also switching my desktop computers to Linux. I want my Linux skills to be just as good as my Windows skills. That’s why I try to understand the details. You can only find solutions to problems if you know how things work in the background.

1 Like
6

Added discover, dnf, packagekit, updates

7

Try

sudo dnf --refresh update -y
pkcon refresh
kill -9 discover
plasma-discover &

But I had the same thing, these sync issues are really annoying.

1 Like
8

Here’s a post where we were messing with doing automatic updates with a script using the packagekit CLI. How to configure automatic offline updates with Fedora?

2 Likes
9

Ups - my answer wasn’t send.
Thanks for your link. I have bookmarked it for later. The use of packagekit is inspiring.
My own script is much simpler. On my own devices I don’t need automatic updates because I still want control over what is installed.

With this thread I want to understand the background of the different update methods.
I happened to find confirmation of my observation when I was looking for information on dnf5. Following the page of the dnf5 proposal, currently all fedora update methods use different cashes.

Currently, dnf, microdnf, and PackageKit use their own cache, leading to significant metadata redundancy. With dnf5 and dnf5daemon, which share metadata, this redundancy will be eliminated.

This explains my observations. And it already shows a solution.

1 Like