Around a week ago I started experiencing an annoying issue with Discover. It tries to fetch the updates, even shows the number of pending updates, but then freezes forever in this state:
Updating via flatpak update and updatectl update gives no errors.
What can cause this issue? A broken repository, incorrect settings, something else?
It could be this issue:
However, it depends what you mean by “about a week ago” 
We think this issue appeared only in the 2026-08-18 image, and rolling back to 2026-08-14 fixes it.
So if you’ve had this issue for more than the last 3 days, it looks like something else may be going on.
Yes, the 2026-08-14 build works fine.
That’s the one, yeah. The next image will fix it.
In the meantime, follow the instructions at Keep the System Up to Date - KDE Linux.
Bonjour, je suis sur 26.08.19 et j’ai le même problème mais malgré les commandes:
[kubu@kubu-system-product-name:~] $ updatectl check
No updates available.
[kubu@kubu-system-product-name:~] $ updatectl update
host: ✓ Already up-to-date
[kubu@kubu-system-product-name:~] $ flatpak update
Looking for updates…
Info: runtime org.kde.Platform branch 6.8 is end-of-life, with reason:
We strongly recommend moving to the latest stable version of the Platform and SDK
Info: applications using this runtime:
io.github.congard.qnvsm
Info: runtime org.gnome.Platform branch 48 is end-of-life, with reason:
The GNOME 48 runtime is no longer supported as of March 24, 2026. Please ask your application developer to migrate to a supported platform.
Info: applications using this runtime:
io.github.nokse22.inspector
**ID Branch Op Remote Download**
Error: While pulling app/org.mozilla.firefox/x86_64/stable from remote flathub: Decompressed delta part exceeds configured limit of 76330069 bytes
Changes complete.
error: There were one or more errors
[kubu@kubu-system-product-name:~] [1] $
This is an upstream bug in the libostree library; see "Decompressed delta part exceeds configured limit" error while updating Firefox · Issue #3635 · ostreedev/ostree · GitHub.
It looks like a fix has already been released, so hopefully that fix should make its way into KDE Linux within a few days.
merci de votre réponse rapide, J’attendrais avec impatience une nouvelle version ou un correctif, et super travail que vous faites pour cette distribution. En phase d’essai pour moi mais déjà adoptée.
Merci beaucoup! Ça me fait plaisir d’apprendre que KDE Linux functionne bien pour toi. 
résolu provisoirement avec la commande
flatpak update -y --no-static-deltas
issue de github
Merci
Updatectl still displays no updates (5 days after the last image). Is this correct or is it a new bug?
Correct, there is no new build yet.
We think there is a fix for the recent KWallet issue, but right now there are a couple of issues blocking new builds from being produced.
A new build is out now!
je vois qu’il y a 6 mises a jour depuis 20260819 mais «ça pédale dans le vide» (expression française).
un reboot vers 20260814 et je vois les 6 mises à jour dont kdelinux 20260823
merci
Je crois que c’était la 2026-08-18 mais oui, elle avait un problème sur Discover qui bloquait le chargement des mises à jour.
C’est réglé sur la nouvelle version d’hier.
Hi Nate. You or someone marked your post as having solved this Issue, but fwiw, for me, neither today’s update to 202609110254, nor last Sunday’s one, was offered to me in Discover; only the various Flatpaks needing update were listed. Both times i had to update via CLI, in Yakuake. I think that also happened the previous Sunday, but i can’t recall for certain. 
202609110254 is from 2 days ago (unrelated but newer builds failed), and you were probably on a build which still had the metainfo 403 issue that prevented Discover to install system updates.
It should work for future updates, when we get one.
Oh nice, thank you.
That sounds like this issue. Essentially everyone is going to need to do one updatectl update to jump to an image 20260907 or later. With the new image in place, Discover upgrades should be working again.
Sounds good. I respectfully suggest though that Nate’s post being marked as “the solution” is rather misleading. IMO that marking should be removed.
Did you experience the specific issue described in the OP, where Discover freezes at “Fetching updates…”? Or did you see the symptoms in this OP, with an explicit 403 error?