Discover also handles Flatpak updates and firmware updates, which dnf doesn’t. You’ll need to run additional commands to replicate the whole Discover process from the command line.
This fixed this issue, and my weird issue where the “Connected devices” pane would open when I ran Discover. Thanks!!
from the very little i know, dnf is a tool to update and install or remove packages meant for redhat derivative distros
if discover uses dnf, how does that work in kubuntu, that is ubuntu, same for kde neon?
interesting comment
It uses whatever Ubuntu uses.
Example: Disccover on Suse Tumbleweed KDE uses “zypper” instead of “dnf”.
great to know, i did like how discover runs on opensuse, displaying each element separatedly when doing updates but in general works sort of weird, yast is still required there
Apparently discover (a kde software management tool) works with different backends on different OSes. (dnf, zypper, yast, etc.)
This does make it problematic for it to be 100% reliable on different platforms.
Usually by using PackageKit as a server, and PackageKit can use different backends depending on which system it is built for.
It looks like Gnome Software has switched to use dnf5daemon-server instead of PackageKit on Fedora 44. That helps maintaining a consistent history.
Since updates work through the terminal but Discover is stuck on “Fetching updates…”, it’s most likely an issue with Discover or PackageKit not the repositories themselves.
You can try:
-
Restarting PackageKit:
sudo systemctl restart packagekit -
Clearing Discover’s cache and then logging out and back in.
-
Running `plasma-discover from a terminal to see if it reports any errors when it hangs.
-
Running
sudo dnf upgrade --refreshto ensure the package metadata is up to date.
If DNF works normally but Discover continues to hang, it’s likely a Discover/PackageKit bug rather than a problem with your Fedora installation. 
I would suggest that folks provide additional data on the upstream bugs.
A related topic
This is often a Discover/PackageKit issue rather than a problem with the repositories themselves. A good first step is to check whether updates work from the command line.
If you’re using Fedora KDE with DNF5, run:
sudo dnf upgrade --refresh
If that completes successfully, then your package repositories are fine and the problem is likely with Discover or PackageKit.
You can also try restarting the PackageKit service:
sudo systemctl restart packagekit
If Discover is still stuck at “Fetching updates”, clear its cache and restart it:
rm -rf ~/.cache/discover
Then log out and back in (or reboot) and try again.
It’s also worth checking whether another package manager is holding the package database:
ps aux | grep -E 'dnf|packagekit'
If another update process is running, wait for it to finish before opening Discover.
Finally, if command-line updates work but Discover continues to hang, it may simply be a Discover/PackageKit bug. There have been occasional regressions where Discover gets stuck while DNF itself functions normally. In that case, updating from the terminal until a fix is released is a reasonable workaround.
If you’re still having trouble, please post the output of:
sudo dnf upgrade --refresh
sudo dnf check
systemctl status packagekit
That should help determine whether the issue is with the package manager, PackageKit, or Discover itself.
This is a duplicate post on another topic and is clearly AI generated.
- Please do not post duplicate content of different topics
- Please comply with fedora policies
Please read the policy for use of AI and comply before moderator action becomes required.
if is a ai account, how can it read the policies and comply? things are not ideal right now for people online, ai is just a annoyance
I don’t know that it is an AI account. I do believe that the post was entirely AI generated.
tbh i had here replies that do look like are made by a ai for sure, or the person has the level of a ai when communicating, wont say names
well, no idea why you have the sudo situation, i fixed it a long time ago, perhaps you didnt removed snap stuff as the previos replies explained how to remove
just in case you can reinstall fedora 44 in case you upgraded from fedora 43 that seems to have been the source of the problem for most of us, it will not add back snap unless you ask for it, snap is better to be left to ubuntu derivative distros tbh
about kernel, no problems here, perhaps you could do a thread for that specific problem with your hardware
What you are saying is a bit confusiing.
You claim to be having issues with discover and plasma-discover-snap, both of which are on Fedora KDE, yet you say you installed Fedora Workstation which uses Gnome.
If you actually installed Workstation then you would not have either discover or the snap package.
You also posted on a topic that has had a solution marked more than 30 posts back and should be allowed to rest. If you have your own problems please open a new topic where the discussion would be focused on your issues and not hidden as a ME TOO in this wandering long topic.
@noname19
I wonder if it would be appropriate to close this topic since you already noted a solution and 25% of the total posts are just wandering on after it was marked solved, some of which are ME TOOs. As the OP I think your choice would apply.
i dont know how a post can be closed, and tbh no idea who to ask to close it
Please do.