Bug 441926 - "Fetching Updates" progress bar sometimes goes backwards
Summary: "Fetching Updates" progress bar sometimes goes backwards
Status: RESOLVED DUPLICATE of bug 435450
Alias: None
Product: Discover
Classification: Applications
Component: PackageKit (show other bugs)
Version: 5.21.5
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: Dan Leinir Turthra Jensen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-09-02 22:00 UTC by David
Modified: 2022-01-21 05:37 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
discover_progress_bar (32.33 KB, image/png)
2021-09-10 17:12 UTC, David 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description David 2021-09-02 22:00:41 UTC 
SUMMARY
Somtimes, the progress bar in discover moves backwards and then continues forwards, sometimes with this happening multiples times in a single bar fill (usually happens before the first half of the bar is reached). Logically, such a thing should not happen in a progress indicator.
Comment 1 Nate Graham 2021-09-08 19:57:40 UTC 
Yes, it does, and no it shouldn't. :(

What were you doing to trigger this? Performing an upgrade or installing an app? WHich app, from which backend?
Comment 2 David 2021-09-08 20:06:10 UTC 
At times, it happens while fetching updates from the software repositories (like "aptitude update") after clicking the system tray icon, without installing anything.

Don't know which backend it's using - I installed it from the debian main repository and haven't changed its configuration.
Comment 3 Nate Graham 2021-09-10 16:58:03 UTC 
Can you provide a screenshot of exactly which progress bar you're talking about?
Comment 4 David 2021-09-10 17:12:30 UTC 
Created attachment 141449 [details]
discover_progress_bar

Attached a screenshot (it's the big bar in the middle of the window).
Comment 5 Nate Graham 2021-09-14 16:23:05 UTC 
OK, thanks.
Comment 6 Nate Graham 2022-01-21 05:37:39 UTC 

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