Thanks Thomas
I ran his command as suggested and was surprised that the package was installed.
Removed it and done a reboot…now discover/update is working as intended.
100% the issue. For others, note that I never installed “snap”. I double checked discover/settings and snap was never ticked. If you now look at Discover/Settings, scroll down to the very bottom and it says: “Missing Backends” . Discover - Snap backend
With a button to install it.
I will add that info to the bug report now.
Info added to bug report bug No: 521865
I wonder how this is getting installed! For comparison, it doesn’t exist on my F44 system (not updated to Plasma 6.7 yet).
It would be interesting to know from dnf history list contains-pkgs=plasma-discover-snap how this originally got installed.
So mine was installed as part of the Fedora 44 KDE upgrade. So it was installed as part of Fedora’s change from FD43 to FD44.
Part of 5189 packages that were installed/upgraded.
i was following these replies and decided to check if indeed i had the snap package, i had it and i removed it, just in case i ran again the command to update distro via the konsole and rebooted
discover now finishes the fetching updates and tells me up to date
in my particular case, iirc i used snap to install brave, or gimp, cant remember, something i was testing, so iirc i installed snap stuff, wasnt a error from fedora or something, i uninstalled it because i found flatpak to be less problematic to add to he system
checking the discover settings, i think i added the flatpak testing option, i dont remeber
i was going to remove it but when i try to it tells me it will remove the following
To remove this repository, the following applications must be uninstalled:
- Breeze GTK theme
- Document Scanner
- Fedora Platform
- Mesa - runtime/org.fedoraproject.Platform.CL.default/x86_64/f44, runtime/org.fedoraproject.Platform.GL.default/x86_64/f44
i added document scanner iirc, but sounds a bit rough if it wants to remove also fedora platform
from the sections of the repo it should have access to, i understand that for me, as a daily user i dont really need source, or debug or testing sections, but i have one that is called rpm fusion for fedora 44 free test updates debug
not sure if i should remove that one
to make fedora work the way i need it, i had to add the rpm for the video codecs but i dont remember if it was this section or what,i think it wasnt
at the end of the list i found a section called missing backends with just one entry called discover snap backend, wasnt this the problematic package?
Yes, that’s the one we removed, which is why it now shows up in the bottom as missing.
thank you for confirming
a bit confusing that some got it as a problem as mentioned, and it became a problem all of a sudden for me, because i made a couple of updates without any form of issue
very nice to see that the people came together sharing so much information here, pretty much all the situation was very well explained
nice to see a forum post helping others like it helped me
I also issued this command, and now discover works. However sometimes (e.g. today) it does not find any package to be updated, while “sudo dnf upgrade” finds 12 updates. Does this depend on some settings?
Not really.
The issue is apparently in the timing of updates of the metadata from the repos.
With dnf you can accept the latest automatic updates to the metadata and perform upgrades, or you can use the --refresh option and ensure your metadata is fully synced with the repos at the time of performing an update.
With Discover the timing of metadata updates is not the same as with dnf and it is more difficult to manually tell Discover to update the metadata.
This discrepancy in timing often leads to the mismatch you are describing.
Since I always want my system to be fully in sync with the repo I use dnf and avoid the gui tools for updating.
I’ve had the same problem on Fedora/KDE all the way back to v32. I gave up on Discover and only use the command line… same one still in the buffer six years later, so updates are just “up arrow, enter”. 
Interesting to learn why the issue exists, tho.
GUI tools show you what the programmer thinks are important and the app works the way the programmer thinks is best. Many details that happen behind the curtain are hidden.
Command line tools show you what is actually happening and do not hide the details.
True. And it’s fine to hide the details so long as the GUI works as expected, or when it doesn’t, at least tells you what went wrong.
this is where both Discover and gnome software are falling down. They do not always tell the user the issue even exists, and often fail with just a hang.
That 100 times. If you want to bring Linux truly to the masses then GUI’s have to be a priority and function accordingly. The average Computer User requires their PC/Laptop to function as a tool to achieve the desired outcome.
That doesn’t mean that we more humble Users are not very grateful for the help we get from the proffessionals here when (not if) things go wrong…we are. 
Discover would be “mission critical” for a cubicle farm where a local mirror managed by the IT group provides updates and the inmates are expected focus on assigned tasks (which may require installing task-specific software with updates scheduled around project deadlines). Any problems are handled by the IT group.
More, Discover is mission-critical for new users whose previous experience is that you point at the update manager, and it Just Works. Discover’s interface is polished enough to reinforce that expectation.
Unfortunately there are cases where the performance doesn’t meet the expectations.
i remember distros 20 years ago trying to implement this, it is two steps forward and sometimes 3 steps back, discover is a opportunity to integrate everything under one app, i do get that is nice to have options, but i personally dont love konsole as much as others do and for sure will forget these commands in a couple weeks
I forget the commands too… fortunately Konsole remembers them for me. But I agree, in this modern era we need Discover in wholly working order.
Bug reports upstream to the developers of Discover might be the best way forward.