Bug 290811 - After deleting a mail, Kmail shows wrong mail when clicking on it.
Summary: After deleting a mail, Kmail shows wrong mail when clicking on it.
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: message list (show other bugs)
Version: 1.99.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-06 17:03 UTC by m.wege
Modified: 2017-01-07 22:07 UTC (History)
2 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description m.wege 2012-01-06 17:03:49 UTC 
Version:           1.99.0 (using Devel) 
OS:                Linux

After deleting an Email in Inbox via [entf (I believe del on English keybord)] I see the wrong email when clicking on it. The mail above is not shown, the mail two emails above shows the mail which is not shown below. 
I have Kmail set to show the newest email last and it is also set to classic view (just plain subject, sender, date, no grouping).
I am usign 4.8. RC1, RC2 is not available yet in Kubuntu.

Reproducible: Always

Steps to Reproduce:
see above

Actual Results:  
see above

Expected Results:  
see above

OS: Linux (x86_64) release 3.0.0-15-generic
Compiler: gcc
Comment 1 Davide 2012-01-07 15:39:47 UTC 
This is a duplicated of 290409. It seems to be fixed in RC2.
Comment 2 dasaan.san 2013-11-03 13:53:28 UTC 
Unable to reproduce with KMail 4.10.5 on KDE 4.10.5 and as mentioned above looks to be a dupe of bug 290409
Comment 3 Denis Kurz 2016-09-24 18:00:43 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 4 Denis Kurz 2017-01-07 22:07:37 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.