Bug 690602

Summary: PackageKit needs to display more technical information when in action
Product: [Fedora] Fedora Reporter: DJ <djzn.br>
Component: PackageKitAssignee: Richard Hughes <rhughes>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 14CC: jonathan, rhughes, smparrish, ugo.viti
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 15:16:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
In this mockup we see 4 added lines of information: package name being downloaded, download speed, time left and local from where it's being fetched.
none
In this mockup, we can see the current package being installed.
none
In this mockup, we see dependencies being resolved, and technical info below the progress bar. none

Description DJ 2011-03-24 18:42:57 UTC
Created attachment 487407 [details]
In this mockup we see 4 added lines of information: package name being downloaded, download speed, time left and local from where it's being fetched.

PackageKit does not display ongoing information, but only a progress bar.
Information like download speed, location from fetching, and estimated left time should be available for user to see on main software management application as well as when installing stand-alone RPM packages. Screenshots included for suggestion.

Comment 1 DJ 2011-03-24 18:43:58 UTC
Created attachment 487408 [details]
In this mockup, we can see the current package being installed.

Comment 2 DJ 2011-03-24 18:44:48 UTC
Created attachment 487409 [details]
In this mockup, we see dependencies being resolved, and technical info below the progress bar.

Comment 3 Richard Hughes 2011-03-29 07:56:05 UTC
It's perfectly possible to add the additional information, but my main question is why we want to show such low level information in a high level UI? I'm always designing PackageKit for these users; http://www.packagekit.org/pk-profiles.html and I'm not sure what they would benefit from showing which file is being depsolved.

Comment 4 DJ 2011-03-29 15:19:48 UTC
Hi Richard, well I have read the reason why "technical info shouldn't bother users" when installing packages and I understand that point of view. While it's perfectly fine to design such thing for common users, I believe that skilled users shouldn't be left in the dark. 

I myself don't fit in any of the profiles you have showed me, and the suggestion I made can really make PackageKit better. 

I can give you a couple of arguments:

a) Download speed: For many times now I had the progress bar completely stuck on me, for God knows whatever reason, because I am unable to decipher beyond the progress bar itself. If there were some information displaying the download speed went down to 10 KB/s I would probably know that the current mirror/repository is suffering from speed issues. That would help me to cancel the operation faster and try another time, than just wait 20 minutes to realize the progress bar got really stuck.

b) Package name: Knowing the name of the current package being downloaded can also help to see what is exactly being downloaded at that moment. While I understand it can be of no help for the common user, I can also understand that skilled users like to know what is being fetched, and what particular time will be spent on downloading that package (now I realize I forgot to include package file size download in the mockup).

c) Time Left for download: Well, this is some useful information as it can give me the actual time so I can calculate, leave the computer, make some coffee or tea with peace of mind, and get back in the right time. (Time left only for download, not installing packages).

d) Location: Location from where is being fetched is also important I think. It's good to know what you actually get from Fedora official repo, and what you don't, since we have RPMFusion, etc. Again, not much good for the users, but if I had a problem with a certain package, that would remind me that it might not be from any official source.

e) Other two mini window mockups, well, while it can't help the common user, it couldn't hurt either, and that way everyone is happy.

f) Last reason is that, we should have this. Ubuntu is a distro targeted at beginners, but even like that they did not leave these kind of information in their "Update Manager". (However, they started to migrate some of the stand alone installation to Software Center and that sucked a little because that info was removed).

Hope this helps.

Comment 5 DJ 2011-03-29 15:22:42 UTC
ERRATA: did not leave these kind of information should read "leave out".

Comment 6 DJ 2011-03-29 18:53:35 UTC
Just want to add another suggestion, like a button to toggle "Advanced View". Clicking on that button would show up all this information. While leaving it alone, would just be the way users want, not bothered at all. That button can be placed near "Help" button.

Comment 7 Ugo Viti 2011-11-06 11:18:26 UTC
I definitely agree with DJ, the download speed and remaining time is very usefull to display, because too often the progress bar stuck and there isn't a easy way to understand if packagekit is working or not.

solution? open a terminal, and use yum... this isn't a solution not for beginner user and not for the power user.

please make us happy adding an [+] option under the progress bar to display technical details of the download :)

example:

Percent completion: 23 %
Package count: 14/23
Total process ETA: 01:23:00

Current package name: Firefox 7.1
Current package ETA: 00:14:13
Download speed: 230 KB/Sec

Comment 8 Fedora End Of Life 2012-08-16 15:17:02 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

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

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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 to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping