Bug 131397 - Odd progress bar behaviour (negative percent completed, etc.)
Summary: Odd progress bar behaviour (negative percent completed, etc.)
Status: RESOLVED DUPLICATE of bug 89620
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-26 15:02 UTC by Tristan Miller
Modified: 2009-07-14 18:10 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
Progress bar stuck on 19%, but details show 100% complete (159.78 KB, image/png)
2006-07-26 15:04 UTC, Tristan Miller
Details
Progress bar shows -1% complete (160.08 KB, image/png)
2006-07-26 15:04 UTC, Tristan Miller
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tristan Miller 2006-07-26 15:02:58 UTC
Version:            (using KDE KDE 3.5.2)
Installed from:    SuSE RPMs

In the far right of the status bar is a progress bar which gives the percent completed of the current task.  Sometimes after a certain task is completed (checking or sending mail, for example), the progress bar continues to show a certain value.  For example, my progress bar is currently stuck on 19% complete, even though no task is running.  If I click on the arrow next to the progress bar to get more information, the pop-up pane tells me that the task is 100% complete, but the progress bar below still shows 19%.

Other times, again while the system is idle, the progress bar will show ridiculous values, such as -1% complete.

See attached screenshots.
Comment 1 Tristan Miller 2006-07-26 15:04:11 UTC
Created attachment 17131 [details]
Progress bar stuck on 19%, but details show 100% complete
Comment 2 Tristan Miller 2006-07-26 15:04:38 UTC
Created attachment 17132 [details]
Progress bar shows -1% complete
Comment 3 Thomas McGuire 2007-03-28 15:34:32 UTC
For the -1% case, see also bug 89620.
Comment 4 Jaime Torres 2009-07-14 18:10:26 UTC

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