Created attachment 150421 [details] Please Discover, tell me what's wrong SUMMARY I propose to display more progress information in the "fetching update" screen. Sometimes, a mirror can be slow or whatever else happen, and showing a progress of the 'fetching updates' process could help users to see where the bottleneck is and take action (like choosing another mirror) Plus, there is a lot of space available in this screen STEPS TO REPRODUCE 1. Launch Discover, and watch the silent progress bar doing its thing SOFTWARE/OS VERSIONS KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.3 Discover: 5.24.5
Yeah. We used to do this but it was implemented in a way that was kind of visually annoying, and people complained so we removed it. I think we need to strike a better balance there. An idea is to display the progress for each individual backend, and then remove the display for that backend once it reaches 100%. So when something is stuck (which is what's happening here), you can see which one it is because it's the only backend left in the display of what's happening.
That would be perfect !
Like showing several progress bars?
Yes, one per backend. Then the user always has visual feedback on what's happening and can also immediately identify which backend is to blame when fetching updates is slow.
Discover 6.3.3 got me today while testing Fedora 42 pre-release. "Fetching updates" progress bar was stuck for over 10 minutes and I had no idea what was happening. What's even worse, until updates are fetched, I cannot install any rpm packages and cannot see installed packages. Only after running `dnf update` I understood what was happening: package repository was especially slow, downloading data at ~10KB/s speed. But dnf displayed a progress bar and even time estimate until completion. At the end I left PC and after hour Discover had completed fetching updates. It would be very useful for casual users to have similar information (download speed and estimate) visible in Discover.