Bug 296201 - Cannot open initial 2nd mail item, after moving to trash initial 1st item of the list
Summary: Cannot open initial 2nd mail item, after moving to trash initial 1st item of ...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.7
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-17 12:31 UTC by Frans Leerink
Modified: 2017-01-07 22:34 UTC (History)
0 users

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 Frans Leerink 2012-03-17 12:31:59 UTC
Hello,
In the incoming mail list I cannot open the initial 2nd item, after 
moving to trash the 1st item of the list.
To read the initial 2nd item I have to select first an other mail item 
and than reselect the initial 2nd item.
I read my mail on a separate screen. 


HOW TO CREATE THIS PROBLEM
1. Read 1st mail item of the list, return to the list and move 1st item 
to trash
2. Select initial 2nd item for reading on seperate screen
3.


WHAT HAPPENED
At the end of step 1 the 1 st mail item of list is moved to trash and 
deleted from the list
In step 2 system does not display, the selected, initial 2nd item on 
separate screen


WHAT SHOULD HAVE HAPPENED
That in step 2 the initial 2nd item is displayed on the separate screen


REMARKS
To overcome this problem I have first to select an other item of the 
list (without reading) and than reselect the initial 2nd item
Comment 1 Denis Kurz 2016-09-24 18:03:49 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 2 Denis Kurz 2017-01-07 22:34:19 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.