SUMMARY Discover stuck at Fetching updates STEPS TO REPRODUCE 1. Open discover 2. Navigate to Updates (Fetching) 3. Wait, wait and wait :-) I've successfully verified and installed updates using pkconf, so there were actually updates. And I have experienced this for the last week, so it is not a one of. OBSERVED RESULT It never returns to the list of updates nor reports that there are no updates EXPECTED RESULT Either a list of updates or a message saying that there are no updates. SOFTWARE/OS VERSIONS Operating System: Ubuntu 24.04.2 LTS (Noble Numbat) KDE Plasma Version: 6.3.1 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.11.0-17-generic (64-bit) Graphics Platform: X11 Processors: 24 × Intel® Core™ i7-14650HX Memory: 31,1 GiB of RAM Graphics Processor 1: Intel® Graphics Graphics Processor 2: NVIDIA GeForce RTX 4060 Laptop GPU Graphics Processor 3: llvmpipe Manufacturer: LENOVO Product Name: 21N5 System Version: ThinkBook 16p G5 IRX
For me it doesn't get stuck, but it just takes a lot of time and doesn't explain what it's doing, what servers is contacting, what are their pings, what are their download speeds. I think it was made with the idea of noobs feeling fine by hiding every kind of useful information. Feels very similar to Windows updater that hides everything. A few days ago one of my DNS servers was responding very slow and I had not idea until I got the same problem in Firefox too, as Discover is always very slow on Debian, but I can't say it was any difference with it on KDE Neon.
I'm also experiencing this issue since plasma desktop update to 6.3. The update to 6.3.1 does not resolve this issue.
I actually git past this now. I deleted the configuration file for discover from .config in my homedir and then it just worked
(In reply to Jarl Gjessing from comment #3) > I actually git past this now. > I deleted the configuration file for discover from .config in my homedir and > then it just worked I tried this too but it didn't work.
I ran pkmon when Discover was fetching. It looks like it finalizes without ever returning (using g_task_return_*()) Transactions: [none] daemon connected=1 network status=online Transactions: 1 /157867_accbccec /157867_accbccec allow_cancel 1 /157867_accbccec percentage 99 /157867_accbccec role refresh-cache /157867_accbccec sender /usr/bin/plasma-discover /157867_accbccec status running (pkmon:3474776): GLib-GIO-CRITICAL **: 07:02:53.732: GTask 0x56e851ba5340 (source object: 0x56e851ba6200, source tag: 0x7d52be0e26c0) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program. updates-changed Transactions: 1 /157867_accbccec 2 /157868_aecaeacb /157868_aecaeacb allow_cancel 1 /157868_aecaeacb percentage -1 /157868_aecaeacb role get-updates /157868_aecaeacb sender /usr/lib/x86_64-linux-gnu/libexec/DiscoverNotifier /157868_aecaeacb status wait (pkmon:3474776): GLib-GIO-CRITICAL **: 07:03:04.254: GTask 0x56e851bae1e0 (source object: 0x56e851ba6200, source tag: 0x7d52be0e26c0) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program. Transactions: 1 /157868_aecaeacb updates-changed Transactions: 1 /157868_aecaeacb 2 /157869_cedababa /157869_cedababa allow_cancel 1 /157869_cedababa percentage -1 /157869_cedababa role get-updates /157869_cedababa sender /usr/bin/plasma-discover /157869_cedababa status wait (pkmon:3474776): GLib-GIO-CRITICAL **: 07:03:05.141: GTask 0x56e851bae4d0 (source object: 0x56e851ba6200, source tag: 0x7d52be0e26c0) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program. Transactions: 1 /157868_aecaeacb 2 /157869_cedababa 3 /157870_eecdeced /157870_eecdeced allow_cancel 1 /157870_eecdeced percentage -1 /157870_eecdeced role get-updates /157870_eecdeced sender /usr/lib/x86_64-linux-gnu/libexec/DiscoverNotifier /157870_eecdeced status wait (pkmon:3474776): GLib-GIO-CRITICAL **: 07:03:05.403: GTask 0x56e851bae1e0 (source object: 0x56e851ba6200, source tag: 0x7d52be0e26c0) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program. Transactions: 1 /157869_cedababa 2 /157870_eecdeced Transactions: 1 /157870_eecdeced Transactions: [none]
(In reply to Brian Wright from comment #2) > I'm also experiencing this issue since plasma desktop update to 6.3. The > update to 6.3.1 does not resolve this issue. same here. pkcon update *does* work. Discover instead is stuck on "Fetching" for hours but never finishes with that. reinstalled, deleted all caches .. to no avail. Since 6.3
I have a slight supicion it can be related to KNewStuff updates not ending, or not signaling when it ends. Could you please try running from the command line: plasma-discover --backends=flatpak,packagekit --mode=Update
(In reply to Ismael Asensio from comment #7) > I have a slight supicion it can be related to KNewStuff updates not ending, > or not signaling when it ends. > > Could you please try running from the command line: > plasma-discover --backends=flatpak,packagekit --mode=Update $ time plasma-discover --backends=flatpak,packagekit --mode=Update org.kde.plasma.libdiscover: OdrsReviewsBackend: Fetch ratings: true adding empty sources model QStandardItemModel(0x6501bc8e4d00) qrc:/qt/qml/org/kde/discover/qml/LoadingPage.qml:3:1: QML LoadingPage: Created graphical object was not placed in the graphics scene. QObject::startTimer: Timers cannot have negative intervals qrc:/qt/qml/org/kde/discover/qml/UpdatesPage.qml:11:1: QML UpdatesPage: Created graphical object was not placed in the graphics scene. qrc:/qt/qml/org/kde/discover/qml/UpdatesPage.qml:40:5: QML OverlaySheet: Binding loop detected for property "implicitHeight": file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/kirigami/templates/OverlaySheet.qml:132:5 ^C real 0m20,927s user 0m11,785s sys 0m1,914s
(In reply to Ismael Asensio from comment #7) > I have a slight supicion it can be related to KNewStuff updates not ending, > or not signaling when it ends. > > Could you please try running from the command line: > plasma-discover --backends=flatpak,packagekit --mode=Update and it *shows* the Updates after a couple of seconds as usual
I confirm that running from the command line shows a normal behavior, while running from the GUI results in "eternal" fetching. I would also like to point out that not all computers are affected - for example, my desktop (~ 10 years old) has the problem described above since a coouple of weeks, while my laptop (2024 model) does not, although they both run KDE 6.3.2 and should have (for all I know) the same configuration.
Also, disconnecting and reconnecting the network can occasionally result in the "eternal fetching" to stop and show results, but not always (sometimes you have to repeat this 2-3 or more times). On the other hand, deleting the Discover configuration file (as suggested in comment 3 above) had no effect for me.
A possibly relevant merge request was started @ https://invent.kde.org/plasma/discover/-/merge_requests/1051
*** Bug 500722 has been marked as a duplicate of this bug. ***
A possibly relevant merge request was started @ https://invent.kde.org/plasma/discover/-/merge_requests/1053
Git commit b1b171f7c51d0aec9cd63953b83719a7c773fd77 by Aleix Pol Gonzalez. Committed on 10/03/2025 at 01:28. Pushed by apol into branch 'master'. kns: Ensure we deactivate the updater when the backend gets invalidated Otherwise it just gets stuck ad eternum. FIXED-IN: 6.3.3 M +7 -0 libdiscover/backends/KNSBackend/KNSBackend.cpp M +7 -0 libdiscover/resources/AbstractResourcesBackend.h M +10 -1 libdiscover/resources/StandardBackendUpdater.cpp https://invent.kde.org/plasma/discover/-/commit/b1b171f7c51d0aec9cd63953b83719a7c773fd77
Git commit f7aec1dca82865945af2638dd40b645831181905 by Aleix Pol Gonzalez. Committed on 10/03/2025 at 01:36. Pushed by apol into branch 'Plasma/6.3'. kns: Ensure we deactivate the updater when the backend gets invalidated Otherwise it just gets stuck ad eternum. FIXED-IN: 6.3.3 (cherry picked from commit b1b171f7c51d0aec9cd63953b83719a7c773fd77) M +7 -0 libdiscover/backends/KNSBackend/KNSBackend.cpp M +7 -0 libdiscover/resources/AbstractResourcesBackend.h M +10 -1 libdiscover/resources/StandardBackendUpdater.cpp https://invent.kde.org/plasma/discover/-/commit/f7aec1dca82865945af2638dd40b645831181905
now in: https://kde.org/announcements/changelogs/plasma/6/6.3.2-6.3.3/ congrats the the devs and thanks to all involved!
The bug is actually still occurring some time or has returned. This actually can be fixed in a proper way if the developers added a setting to not auto-update apt every time Discover is launched. Just add a toggle switch so the user can choose.
I'm encountering this bug in current Neon testing (plasma 6.6.91). Running discover from a terminal plasma-discover --backends=flatpak,packagekit --mode=Update works, but from the GUI it remains stuck at refreshing.
(In reply to Jérôme Brenier from comment #19) > I'm encountering this bug in current Neon testing (plasma 6.6.91). > Running discover from a terminal plasma-discover > --backends=flatpak,packagekit --mode=Update works, but from the GUI it > remains stuck at refreshing. Same thing here. Running Fedora KDE 44 with Plasma 6.7.0, terminal works, from the GUI it seems stuck. I can see there are updates pending on the left side bar icon showing the badge withe the number of available packages to update
Reporting in form Fedora 44, after the KDE 6.7 update the update tab in discover is stuck on "Fetching Updates" Updating through Konsole does work.
I'm having this issue as well and it started after updating to Plasma 6.7 on Fedora 44.
I can confirm this on KDE Neon with latest updates since Plasma 6.7 release. At least on KDE Neon, it seems to be related to Snap. For example this works: plasma-discover --backends=flatpak,packagekit --mode=Update but as soon as I add Snap backend: plasma-discover --backends=flatpak,packagekit,snap --mode=Update the update window get stuck. These messages can be immediately be seen in dmesg after running the Descover from console: [pet jun 19 14:46:54 2026] loop0: detected capacity change from 0 to 8 [pet jun 19 14:46:54 2026] audit: type=1400 audit(1781873214.281:134): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/usr/lib/snapd/snap-confine" pid=12270 comm="apparmor_parser" Also, funny, Disks & Devices sometimes pop up from the system tray as soon as Discover is started even thou I have no removable devices connected.
(In reply to Bojan Vitnik from comment #23) > I can confirm this on KDE Neon with latest updates since Plasma 6.7 release. > At least on KDE Neon, it seems to be related to Snap. For example this works: > > plasma-discover --backends=flatpak,packagekit --mode=Update > > but as soon as I add Snap backend: > > plasma-discover --backends=flatpak,packagekit,snap --mode=Update > > the update window get stuck. > > These messages can be immediately be seen in dmesg after running the > Descover from console: > > [pet jun 19 14:46:54 2026] loop0: detected capacity change from 0 to 8 > [pet jun 19 14:46:54 2026] audit: type=1400 audit(1781873214.281:134): > apparmor="STATUS" operation="profile_replace" info="same as current profile, > skipping" profile="unconfined" name="/usr/lib/snapd/snap-confine" pid=12270 > comm="apparmor_parser" > > Also, funny, Disks & Devices sometimes pop up from the system tray as soon > as Discover is started even thou I have no removable devices connected. I'm also using snaps, so I'm going to try to replicate what you did here and report back.
(In reply to Bojan Vitnik from comment #23) > I can confirm this on KDE Neon with latest updates since Plasma 6.7 release. > At least on KDE Neon, it seems to be related to Snap. For example this works: > > plasma-discover --backends=flatpak,packagekit --mode=Update > > but as soon as I add Snap backend: > > plasma-discover --backends=flatpak,packagekit,snap --mode=Update > > the update window get stuck. > > These messages can be immediately be seen in dmesg after running the > Descover from console: > > [pet jun 19 14:46:54 2026] loop0: detected capacity change from 0 to 8 > [pet jun 19 14:46:54 2026] audit: type=1400 audit(1781873214.281:134): > apparmor="STATUS" operation="profile_replace" info="same as current profile, > skipping" profile="unconfined" name="/usr/lib/snapd/snap-confine" pid=12270 > comm="apparmor_parser" > > Also, funny, Disks & Devices sometimes pop up from the system tray as soon > as Discover is started even thou I have no removable devices connected. Can confirm that on Fedora 44 with KDE 6.7.0 that it worked when using the command: plasma-discover --backends=flatpak,packagekit --mode=Update And does not work, stays on the fetching updates screen when using: plasma-discover --backends=flatpak,packagekit,snap --mode=Update So it appears something with snaps is tripping is up as you've said.
Yeah, disabling Snap does indeed solve the issue.
Thanks for the additional information, that's helpful.
(In reply to jz5678910 from comment #25) > plasma-discover --backends=flatpak,packagekit --mode=Update Really works. But strange situation, I disabled Snap at all. I don't use it and its mark is unchecked inside Discover.
I have had several problems with Neon update to 6.7 KDE, so downloaded latest ISO and created a clean install alongside my original. There was a bug with the ISO as I could only install the latest using safe mode. Rebooted and logged in - safe mode was still set. Clicked on Icon indicating updates available. Discovery started indicating 74 updates to be applied. These could not be applied as the update window got stuck. Terminated discovery and ran plasma-discover --backends=flatpak,packagekit --mode=Update. The update window remained stuck. Leaving snap out had no impact. This is on a clean new install. Ran "sudo pkcon" update and replied "Y" to install updates. The update command above without snap now had the Discovery update window unstuck. Discover on my original install has similar update window issues. System info from the new install: Operating System: KDE neon User Edition KDE Plasma Version: 6.7.0 KDE Frameworks Version: 6.27.0 Qt Version: 6.11.1 Kernel Version: 6.17.0-35-generic (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 1700 Eight-Core Processor Memory: 16 GiB of RAM (15.5 GiB usable) Graphics Processor: llvmpipe (should be NVIDIA GeForce GTX 750 Ti but when safe mode is turned off the new install fails on reboot and does not display logon screen - this will be another bug issue).
Disabled snap a few days ago, someone in another conversation referred to this one but the problem persists in my experience. Until Discover update tab is fixed, I'll continue updating via konsole
*** Bug 521642 has been marked as a duplicate of this bug. ***
I was able to reproduce this on KDE Neon Testing, and see the same output in the terminal as in bug 521642
Suddenly it's working. Just been updating DNF and Flatpak in the meanwhile and I did leave my computer on for the last couple of days but this time discover shows all the updates and the update all button is active. I'm going try it and report back...
So today it's working, after restarting and running DNF and FlatPak updates manually and getting "nothing to do" and "nothing to update" I see the discover updates worked today. I am now seeing new crash extraction pop-ups if that continues I'll search for/add a new topic. However, Discover updates worked for me today.
*** Bug 522034 has been marked as a duplicate of this bug. ***
Fedora 44 KDE Today updated from Plasma 6.7.0 to 6.7.1 Problem reappeared. Discover update once again hung at never ending Update. Checked for package: "plasma-discover-snap" and it was reinstalled with KDE Plasma 6.7.1 Removing the package and rebooting once again fixed the problem.
Can confirm that on Fedora 44 with KDE 6.7.2 this issue still exists. Bypassing the snap backend still fixes it.
Try logging into a sudoer account (if not already) Open terminal Paste: sudo dnf remove snapd So far I was able to install system updates quickly and it stops searching for updates that aren't there. Right now it just says up to date. Will test over time and confirm.
System: Fedora 44 (KDE Plasma Desktop Edition), Discover 6.7.2, Wayland session. Confirming this also happens on Fedora, not just Neon/Kubuntu. Symptoms matched exactly what's described here: the Updates page would show the correct update count (badge + systray notification) but stay stuck indefinitely on "Fetching updates..." with no list ever showing. I also noticed the Snap source checkbox in Settings > Software Sources was broken independently (toggling it on wouldn't stick — reverts to unchecked, likely related to bug 494738), and this journal line appeared repeatedly while the Updates page was hung: QIODevice::read (QSslSocket): device not open Workaround that fixed it for me: sudo dnf remove plasma-discover-snap (this only removes the Discover snap plugin + snapd-glib/snapd-qt bindings — snapd itself and the snap CLI are untouched). After removing it and restarting Discover, the Updates page immediately showed the full list again. One thing worth flagging for triage: plasma-discover-snap is pulled back in as a weak dependency on subsequent system updates, so this workaround doesn't stick permanently — it may need to be reapplied after each Plasma update until there's a real fix in the snap backend itself.
This appears to be resolved in KDE 6.7.3 for me on Fedora 44
(In reply to jz5678910 from comment #40) > This appears to be resolved in KDE 6.7.3 for me on Fedora 44 I spoke too soon. It worked while there was a snap update available. After updating that snap it is now back in the infinite "Fetching Updates" It is once again fixed by the uninstalling the snap backend.
After doing sudo remove snapd, it consisitently fetches and installs updates on my Fedora 44 system. Caveat: Once in a while my discover app doesn't launch at all but returns to normal after a reboot. Not sure whether this is a pre-existing condition, whether it was caused by removing snapd or if one of the updates causes the issue. However the previously mentioned window management crash at login has stopped (forgot the name of the window management program for KDE. Maybe wayland?)
Happening to me too on Fedora 44, Plasma 6.7.3 (plasma-discover-snap 6.7.3-1.fc44). Discover hangs on "Fetching updates" until plasma-discover-snap is removed; after removing it, Discover immediately shows updates correctly. Note for Fedora users: the package gets reinstalled by system updates (it is a weak dependency of snapd), so the workaround needs excludepkgs=plasma-discover-snap in /etc/dnf/dnf.conf to stick. Possibly useful detail: while Discover is hung, snapd itself responds fine at the CLI (snap refresh --list returns instantly), and all plasma-discover threads sit idle at 0% CPU in poll/futex. So it looks like the snap backend never emits its finished signal, rather than a snapd communication problem.
*** Bug 523442 has been marked as a duplicate of this bug. ***
Same on Fedora 44, but Discover hangs on microcode update with snap removed. This application should behave like "dnf update", i.e. shows a useful log and implements timeouts ! Look like its design was only tested on a working environment : it works or hangs/crashes !
*** Bug 522546 has been marked as a duplicate of this bug. ***
It would appear this was just fixed; see Bug 524077. *** This bug has been marked as a duplicate of bug 524077 ***