Version: 1.6.52 (using KDE 3.2.90 (3.3 alpha1, CVS >= 20040522), compiled sources) Compiler: gcc version 3.3.3 (Debian 20040422) OS: Linux (i686) release 2.6.6 Hi, the deletion of the index file made me aware of yet another bug: the progress dialog does not indicate at all how much progress went on already, it is always stuck at 0%. When opening an imap folder for the first time it stays at 0% until, it seems, the data from the imap server is retrieved. Then it jumps to 100% for a while and CPU goes up to 100% as well; a few seconds later the progress dialog disappears, but KMail is still busy and after yet a bit more time the messages finally appear. The detailed progress dialog does not work, either (i.e., same behavior). Similar issue when checking for new mail: the progress dialog starts at about 10% (no number is shown, either!) and stays there until the action is finished, then jumps to 100% and eventually disappears. The detailed progress dialog works fine in this case though (if it is shown at all). Cheers, Michael
Working on it. My development machine's drive died today, so it'll be a few days, I fear, before I can get back to this. Till
Michael, at least the second issue should be fixed in cvs now. Can you check, please?
No, not the first one, the second one is fixed :-) The first case changed, though: the progressbar now stays at 0% until it is done. Then it jumps to 100%. But thanks for fixing the second one! Much more important ;-)
I'm just writing to confirm the issue about the progress bar showing 0% until its done. KDE 3.3.0 with courier-imap Gentoo
Hi, I can confirm this for KDE 3.3.1. I have a very big IMAP mailbox with about 8000 messages in there (mailing list), and when KMail updates this box, the (expanded) progress dialog stays at 100% (with KMail using 100% CPU) for about a minute before any messages are displayed. This seems like KMail has frozen and at first I thought that was the case and killed it, which didn't help (obviously). It needs that much CPU while reading the IMAP cache files (I found out via strace). Thanks for looking into this! Jens
I can't confirm any of the two issues on trunk r855160 any longer.
it works for me also.