Discover in KDE seems stuck

, ,

Good afternoon,

I’m intending to finally update to Fedora 44 this week and it seems that the updater is stuck at the moment. I let it sit for about 30 minutes and it’s still on the same status.

Is there anything I can do to maybe get this sped along so I can get to the next step of trying to update for 44?

Thanks.

Try executing the following command:

sudo dnf clean all && sudo dnf check-upgrade

This clears your package manager’s cache to force a fresh metadata download and displays all pending updates.

Unfortunately still stuck on fetching updates for the moment.

That’s why I suggested running that command. Try closing Discover first and see if that helps.

Hi Reshad,

Sorry I think i chose my words poorly.

I went ahead and closed it from system monitor to make sure it was cleared and tried again.

I also went ahead and restarted just to check. It seems to still be stuck on the same step.

Thanks.

It is a known problem that if you have the package plasma-discover-snap installed, you get this problem.

To uninstall run

sudo dnf remove plasma-discover-snap

There is a bug report for this at
Bug 2499464 - Discover freezes when attempting to update

FYI Discover uses PackageKit that is not affected by theses commands.

In This Week in Plasma: QtWidgets Apps Join the Union - KDE Blogs I see this:

Plasma 6.7.5
Fixed a pretty bad bug that made Discover get stuck while checking for updates when its Snap backend was present, but there were no upgradeable Snap apps. (Dustin Trumps, KDE Bugzilla #524077)

It would help, but only if plasma-discover has been fixed with a fix for this problem.

I suspect you’ll do this anyway, but don’t update via the GUI - do it from the command line.

Should I just try a regular dnf update in that case see if it fixes?

sudo snap refresh && flatpak update && sudo dnf udpate --refreesh should take care of everything

This for sure updated things are you’d expect.

Strangely though there’s still one update that’s hung up still in updates.

Is it possible to run kde discover from the command line and perhaps figure out what the freeze is?

Would it just be wiser to update to 44 from the command line?

The command line method is robust and if it does fail is easier to debug.

It is how I update my systems.

Did you uninstall the snap plugin?

sudo dnf remove plasma-discover-snap

Or was it never installed? Do you actually install snap packages?

That was question for @gamingdad655

sorry I thought from the conversation someone mentioned that snap should’ve been fixed by now.

I ran dnf repoquery --whatrequires plasma-discover-snap to see if anything requires it and I got this output

Updating and loading repositories:
Repositories loaded.

Assume this means nothing will explode if this is gone and it’s good to leave?

Edit:

Also went ahead and ran snap list

Output is as follows:

Name Version Rev Tracking Publisher Notes
bare 1.0 5 latest/stable canonical✓ base
core18 20260204 2999 latest/stable canonical✓ base
core22 20260410 2437 latest/stable canonical✓ base
gang-garrison-2 2.9.2 1 latest/stable marisag1967 -
gnome-3-28-1804 3.28.0-19-g98f9e67.98f9e67 198 latest/stable canonical✓ -
gtk-common-themes 0.1-81-g442e511 1535 latest/stable canonical✓ -
i2pd 2.59.0 606 latest/stable supervillain -
snapd 2.76.2 27710 latest/stable canonical✓ snapd
wine-platform-5-stable 5.0.3 18 latest/stable mmtrt -
wine-platform-runtime v1.0 409 latest/stable mmtrt -

Thanks.

Think i might’ve figured it out.

I had two packages that i removed that i never ended up using… gang-garrison and I2PD.

After removing these two it appears like the menu has refreshed itself. So it’s likely one of these two was broken.

I’m going to try to make some time to upgrade to 44 this weekend but this might’ve been it.

Sorry to mislead, I reported that KDE had fixed this.

The fix has not hit Fedora yet.

I think it’s coming in 6.7.5 release that has not been built yet.

Also run snap list --all to see the old versions that are no longer needed.