Bug 221759

Summary: After moving emails, highlighted record is wrong
Product: [Applications] kmail Reporter: Lars Erlandsen <lars_erlandsen>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: bjoern
Priority: NOR    
Version: 1.12.2   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:

Description Lars Erlandsen 2010-01-08 07:38:38 UTC
Version:           1.12.2 (using KDE 4.3.2)
OS:                Linux
Installed from:    Ubuntu Packages

1. Click on an email in the list view.
2. Shift-click on another email
3. Move the highlighted emails to another folder
4. After the move, a different record is now highlighted as the current entry. However, the highlighted entry has no relationship with the internal entry that the software thinks it is pointing to. If you shift-click any email, you will get a random collection of records highlighted, and if you do anything else with the highlighted entry through the menu or keyboard shortcuts, these will operate on a completely different email from the one that is highlighted in the window.

You always have to deliberately click on a new email before being able to do anything else after moving emails.

lerlands@lenny:~$ lsb_release -rd
Description: Ubuntu 9.10
Release: 9.10

lerlands@lenny:~$ apt-cache policy kmail
kmail:
  Installed: 4:4.3.2-0ubuntu6
  Candidate: 4:4.3.2-0ubuntu6
  Version table:
 *** 4:4.3.2-0ubuntu6 0
        500 http://gb.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
Architecture: i386
Date: Tue Jan 5 06:42:55 2010
DistroRelease: Ubuntu 9.10
Package: kmail 4:4.3.2-0ubuntu6
ProcEnviron:
 LANGUAGE=
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
SourcePackage: kdepim
Uname: Linux 2.6.31-16-generic i686

Reported as ubuntu bug #503611, they suggested reporting it directly to the KDE team.
Comment 1 Björn Ruberg 2010-03-12 00:22:31 UTC

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