Bug 399869 - No feedback on the update page when updating backends
Summary: No feedback on the update page when updating backends
Status: RESOLVED DUPLICATE of bug 399571
Alias: None
Product: Discover
Classification: Applications
Component: discover (other bugs)
Version First Reported In: 5.14.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Aleix Pol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-16 08:31 UTC by Mayeul C.
Modified: 2018-10-19 19:05 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
looking for updates (55.35 KB, image/png)
2018-10-16 23:26 UTC, Aleix Pol
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mayeul C. 2018-10-16 08:31:02 UTC
SUMMARY
This is probably due to slow backends.
As originally stated in https://bugs.kde.org/show_bug.cgi?id=385754#c22 Discover can be slow to display the list of packages that need updates. During this time, it displays "no updates available", which is a bit misleading, as can be seen in the aforelinked thread.

STEPS TO REPRODUCE
1. Wait for some updates to show up
2. Click on the tray icon -> display updates
3. Wait for a few seconds in front of the "no updates" screen (up to a few minutes, especially on slow connections) for updates to be displayed

OBSERVED RESULT
Discover is slow to display the list of updates.
The user does not receive any feedback during this time.


EXPECTED RESULT
It would be nice to display something like "Discover is compiling the list of updates" or "Discover is checking for updates", with a spinner.

Best would be to list each backend separately, and display its status: no updates, checking, X updates, separately.

SOFTWARE VERSIONS
KDE Plasma Version: 5.14.0
KDE Frameworks Version: 5.50.0
Qt Version: 5.11.2
Comment 1 Aleix Pol 2018-10-16 23:26:35 UTC
Created attachment 115694 [details]
looking for updates

This is what I see when I do what you describe.
Comment 2 Aleix Pol 2018-10-19 19:05:40 UTC

*** This bug has been marked as a duplicate of bug 399571 ***