Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1341163 - don't reset progress bar for system upgrade when resuming download
Summary: don't reset progress bar for system upgrade when resuming download
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-software
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1308538
TreeView+ depends on / blocked
 
Reported: 2016-05-31 11:58 UTC by Kamil Páral
Modified: 2020-09-15 08:35 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-15 08:35:36 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1335414 0 unspecified CLOSED Graphical upgrade failed with error with no details 2022-05-16 11:32:56 UTC

Internal Links: 1335414

Description Kamil Páral 2016-05-31 11:58:12 UTC 
Description of problem:
Originally reported as bug 1335414 comment 5 through 7.

When the system upgrade download is interrupted for any reason (network timeout, network down, system shutdown, etc) and then resumed, the progress bar starts at 0%, even though many packages are already downloaded. The users have no detailed information available, which means they have to assume the whole download operation starts from scratch. That can be very infuriating. It is not true, but that's how it looks like.

When the user resumes system upgrade download, please adjust the progress bar accordingly (so if e.g. 50% of packages are already downloaded and present on disk, start the progress bar at 50%).

Version-Release number of selected component (if applicable):
PackageKit-1.1.1-2.fc23
libgusb-0.2.9-1.fc23
libhif-0.2.2-4.fc23
gnome-software-3.20.3-1.fc23
libappstream-glib-0.5.14-1.fc23
json-glib-1.2.0-1.fc23

How reproducible:
always

Steps to Reproduce:
1. download some packages during system upgrade (e.g. 30% of them) and then interrupt the download somehow
2. resume the download
3. see the progress bar starting at 0% (well, it's more like 10% because it counts repo initialization for that much)

Additional info:
The progress bar fills up more rapidly after resume (because there's less stuff to download), but that's almost imperceptible on slow links or when you haven't already downloaded a very large percentage of the overall bulk already).
Comment 1 Fedora End Of Life 2016-11-25 09:10:22 UTC 
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 2 Richard Hughes 2020-09-15 08:35:36 UTC 
>the progress bar starts at 0%, even though many packages are already downloaded

We don't get the previous percentage from PackageKit; we only know the percentage from the current transaction unfortunately.
Note You need to log in before you can comment on or make changes to this bug.