Bug 180250 - kpackagekit progress bar is hard to understand
Summary: kpackagekit progress bar is hard to understand
Status: RESOLVED INTENTIONAL
Alias: None
Product: kpackagekit
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 0.3.1
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Steven M. Parrish
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-10 14:21 UTC by Steven M. Parrish
Modified: 2009-01-28 16:45 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steven M. Parrish 2009-01-10 14:21:56 UTC
Version:           0.3.1 (using KDE 4.1.3)
OS:                Linux
Installed from:    Fedora RPMs

Description of problem:
kpackagekit uses a single progress bar to indicate both download and install
progress, and it also seems to indicate download progress by number of
packages, not by package size. This makes it a bit difficult to work out what
it's doing sometimes -- for example, I didn't initially realise that "40%"
really means "download done", and it can often "stick" for a while at 39% if
the last package to download is big. I have a couple of suggestions:

- Use a separate progress bar for downloading and installing -- so let it get
to 100% downloaded and then start again (with clear UI indication) for the
install
- (May be harder) make the downloading progress bar indicate download *size*,
not number of packages. (I don't think this is already the case)

Version-Release number of selected component (if applicable):
kpackagekit-0.3.1-9.fc10.i386
Comment 1 Torrie Fischer 2009-01-28 16:45:16 UTC
This is actually a technical limitation in PackageKit, not KPackageKit.

All we do is listen to the backend which sends periodic updates of the transaction progress. On my fedora system with the yum backend, the entire 'install a package' transaction is split into a few sections. when a transaction is in a certain stage, the progress is in one of these ranges:

5%: Dependency resolution
10%-40%: Downloading
40%: Signature checking
45%: Test commit
55%-95%: Installation
95%-100%: Cleanup

In any PackageKit backend, any of these steps is entirely optional. The percentage reported by PackageKit is for the entire transaction which includes all those steps, so its a bit difficult to figure out the exact sub-percentage for one step.

In the latest KPackageKit SVN, there is an update to the transaction dialog that shows a sub-percentage progress bar (as reported by PackageKit). In the yum backend's case, it shows the specific package's progress (eg download or installation).

It currently isn't possible to get the size of the packages to be downloaded, so we can't show the bar per size. However, the overall transaction progress is updated according to the downloaded size in recent packagekit versions (its just rounded to the nearest whole number).

I'm marking this as WONTFIX because all this is handled upstream in PackageKit, and is already fixed :)