Bug 279094

Summary: Message list gets "confused" about what is the current row when deleting mails
Product: [Applications] kmail2 Reporter: Albert Astals Cid <aacid>
Component: message listAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: kde, sven.burmeister
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Albert Astals Cid 2011-08-01 21:27:14 UTC 
Version:           unspecified (using KDE 4.7.0) 
OS:                Linux

Deleting a few mails with shift+click and then doing shift+click again selects the wrong rows

Reproducible: Always

Steps to Reproduce:
* Go to a folder with a few mails to delete (say 10)
* Click in the first one
* Hold shift
* Click in the fourth email
* Release shift
* Press the Delete key
* You now have 6 mails and the first one is the selected one
* Hold shift
* Click in the third email
* Release shift
* Observe how the wrong emails have been selected (i.e. the second email is not selected)


Expected Results:  
* The right emails should be selected (i.e. first that was the selected one already, third that was the one you clicked in and second that lies between them)

OS: Linux (x86_64) release 2.6.39-ARCH
Compiler: gcc
Comment 1 Scott Kitterman 2011-09-26 17:03:09 UTC 
With KDE 4.7.1 I see it getting confused when deleting just a single message.  I think this may be related to Bug 266056 as well.
Comment 2 Scott Kitterman 2011-10-05 01:58:37 UTC 
This seems to me to be resolved with one of the commits shortly before 4.7.2.
Comment 3 Denis Kurz 2016-09-24 18:23:22 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:39:52 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.