Bug 320967 - Progress % goes to 100% very quickly but job is not complete yet
Summary: Progress % goes to 100% very quickly but job is not complete yet
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.10.3
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-09 19:02 UTC by Emre
Modified: 2017-01-07 22:35 UTC (History)
0 users

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 Emre 2013-06-09 19:02:37 UTC
I'm opening an IMAP mailbox folder. Server is running on localhost so pretty fast.
There are 10+ thousand mails inside the folders. 
When I open a folder, the status bar counting the % completed on the bottom right side of the status bar quickly reaches 100%, but I can still see messages being updated in the message list. 
So the status % is not giving correct information and it is also not giving idea if the job has been finished or not (ie in this case, opening a folder). So I have to wait for indefinite time and guess that work is done.

Reproducible: Always

Steps to Reproduce:
1. Setup a new IMAP account and enter a  folder with many messages
2. Watch the progress bar at bottom right corner (or Akonadi configuration window status)
3. See that it goes to 100% but there is still progress on message list
Actual Results:  
As explained above.

Expected Results:  
The progress shall show % progress depending on how many message headers it opened from total # of messages in that folder, and only reach 100% once it opened 100% of the headers.
Comment 1 Denis Kurz 2016-09-24 18:06:42 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:35:13 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.