Bug 325338 - kmail2 shows only mails in newly opened folder that were moved there in the same session
Summary: kmail2 shows only mails in newly opened folder that were moved there in the s...
Status: RESOLVED DUPLICATE of bug 319212
Alias: None
Product: kmail2
Classification: Applications
Component: message list (show other bugs)
Version: 4.11.1
Platform: Ubuntu Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-26 18:29 UTC by Michael Büker
Modified: 2013-10-09 20:32 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Büker 2013-09-26 18:29:01 UTC
If I move mails from folder A to folder B and then open folder B, only the mails I moved there are shown, even if folder B also contains other messages.

This happens only if I have not opened folder B before the moving operation.

Restarting kmail2 always eliminates the problem.

Reproducible: Always

Steps to Reproduce:
1. Launch kmail2. (Let's say, folder B already contains messages from Alice, Bob and Christa.)
2. Move message(s) from folder A to folder B. (Let's say we move messages from Dennis and Elliot to folder B.)
3. Open folder B.
Actual Results:  
Only the messages from Dennis and Elliot are shown.

Expected Results:  
All messages from Alice, Bob, Christa, Dennis and Elliot should be shown in folder B.

I have a local dovecot IMAP server. Previous versions of kmail2 (up to 4.10) did not show this problem with the very same server.
Comment 1 Rigo Wenning 2013-10-03 17:14:52 UTC
I can confirm this for KDE 4.11.2 on OpenSUSE KR 411 repos. Ending kmail2, waiting 10 seconds, restarting kmail2 and all content is there. I see all content in akonadiconsole, but happened that I did not even see all content there.
Comment 2 graham 2013-10-09 18:29:34 UTC
This appears to be a duplicate of Bug 319212
Comment 3 Jekyll Wu 2013-10-09 20:32:19 UTC

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