Bug 278678

Summary: Select multiple email after deleting emails completely messed up
Product: [Applications] kmail2 Reporter: FiNeX <finex>
Component: message listAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: public
Priority: NOR    
Version: 4.7   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:

Description FiNeX 2011-07-28 08:03:51 UTC
Steps to reproduce:

* CASE A *
1) Select the first 4 email
2) Press "DEL"
-> the selected emails are deleted
-> the first email on the list is selected
3) SHIFT+Click on the second email on the list
-> the first five email are selected

* CASE B *
1) repeat steps A1 and A2
2) SHIFT+Click on the fifth email of the list
-> The first and the fifth email of the list are selected, the second, the third and the fourth aren't.

* CASE C * 
1) repeat steps A1 and A2
2) SHIFT+Click on the fourth email of the list
-> The first, the fourth and the fifth email of the list are selected, the second and the third aren't.

Recap:

1. Click on email 1

2. SHIFT+Click email 4 
[1..4] are selected

3. Press DEL
[1] is selected

4/A. SHIFT+Click email 2
[1..5] are selected instead of [1,2]

4/B. SHIFT+Click email 5
[1,5] are selected instead of [1..5]

4/C. SHIFT+Click email 4
[1,4,5] are selected instead of [1..4]


There are even other cases, for example starting the selection not from the first item of the list, or from the last...

Thanks for the attention.
Comment 1 FiNeX 2011-09-08 08:37:37 UTC
The bug is still reproducible using KDE 4.7.1
Comment 2 Alvise 2012-08-13 17:10:12 UTC
This bug is confirmed also in version 4.9.0
Comment 3 Denis Kurz 2016-09-24 18:08:48 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:05: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.