Bug 513220

Summary: Regression in how the updates for packages are displayed
Product: [Applications] Discover Reporter: John <ilikefoss>
Component: UpdatesAssignee: Plasma Bugs List <plasma-bugs-null>
Status: CONFIRMED ---    
Severity: minor CC: aleixpol, nate
Priority: HI Keywords: regression
Version First Reported In: 6.5.3   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description John 2025-12-11 15:11:56 UTC 
SUMMARY
Regression in how the updates for packages are displayed

STEPS TO REPRODUCE
1. Use Debian with the 'testing' repository.
2. Open Discover.
3. Click on the Updates item in the left panel to go to that page.
4. If the the updates searching is in progress, do nothing, otherwise click on the Refresh button.

OBSERVED RESULT
After see the 'Fetching updates...' message and a bit of info with a progress bar below about what is doing...
An 'Up to date' message and an icon (an arrow pointing up mainly) above it is shown...
After 1-3 seconds, the updates for various pages appear.

EXPECTED RESULT
Once the search for updates if done (the progress bar is at 100%), the updates available for various packages are presented directly.
Without first saying that everything is up to date and then having a second automatic refresh that shows them.
Many times being in a hurry I was tempted to just close Discover without installing any updates as I thought that there were no updates.
This is a regression compared to before.
Starting a few releases ago, probably in 6.5 release.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.9.2

ADDITIONAL INFORMATION
It probably happens only with Apt / Deb packages from what I could notice until now.
Please check if it's similar / duplicate of this one happening on KDE Neon:
https://bugs.kde.org/show_bug.cgi?id=510973
Comment 1 Nate Graham 2025-12-11 16:18:42 UTC 
Can reproduce on KDE Linux too (which has git master of everything); looks like it's not backend-specific.
Comment 2 John 2025-12-11 22:00:22 UTC 
(In reply to Nate Graham from comment #1)
> Can reproduce on KDE Linux too (which has git master of everything); looks
> like it's not backend-specific.

I was also a bit "lucky" a few minutes ago for a few moments, with something being slower than usual (the servers or the networks) an I could see that it's doing something like these steps:
Refreshing Debian / GNU Linux forky/sid

Refreshing Flatpak
Refreshing Debian / GNU Linux forky/sid

Refreshing Debian / GNU Linux forky/sid

But it's still very fast and confusing on what exactly is doing and in what order.
And why the output is:
1 line
2 lines
1 line

Plus I wish it would be consistent with the names like:
Refreshing the (stable|testing|unstabe) repository of APT
Refreshing the (stable|beta) repository Flatpak
OR:
Refreshing the (stable|testing|unstabe) repository of Debian
 Refreshing the (stable|beta) repository of Flathub

So either show the packaging formats' names or the repositories' names!

I'm more interested in which repositories are contacted and which branch of them than for which packaging format.
And for APT, I am interested to see also which mirror has been contacted as we can put multiple ones in the configuration.
Especially if we use Nala that makes finding and using the fastest mirrors really easy with the fetch command.
https://github.com/volitank/nala?tab=readme-ov-file#fetch

IF APT term is shown, it must be written exactly like that as it's an acronym:
https://en.wikipedia.org/wiki/APT_(software)

Thanks and good luck with whatever you can fix / improve here!