Bug 398399 - using + to move to next unread message keeps the current message also selected
Summary: using + to move to next unread message keeps the current message also selected
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: message list (show other bugs)
Version: 5.9.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-08 19:00 UTC by paul vixie
Modified: 2022-12-30 05:24 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
screen shot showing two selected messages (26.32 KB, image/png)
2018-09-10 07:38 UTC, paul vixie
Details

Note You need to log in before you can comment on or make changes to this bug.
Description paul vixie 2018-09-08 19:00:22 UTC
if i'm focused on a message, and i hit + to move the focus to the next unread message, i end up with both the message i am coming from AND the message i am moving to, selected. this means when i then hit Delete to delete the second message, both the second and first messages are deleted.
Comment 1 Christian Kalkhoff 2018-09-10 07:07:21 UTC
I am unable to reproduce this bug in 5.9.1 on Archlinux. 

Are you able to update and reproduce? If not, can you please tell which message list mode, ordering, grouping, etc you are using?
Comment 2 paul vixie 2018-09-10 07:38:59 UTC
Created attachment 114875 [details]
screen shot showing two selected messages

after i read your message, i hit +, and both your message and the one following it in my inbox became selected. i took a screen shot. i attached that here.

this is not a reliable problem. sometimes i can reproduce it, as now.

my pane geometry may be unusual. i have sorting by date/time, aggregation by flat date, theme classic. headers are kmail 5.2, attachments are smart. i "use fixed font".
Comment 3 Christian Kalkhoff 2018-09-12 20:19:02 UTC
I did some tests but wasn't able to reproduce in kontact/kmail 5.9.1 on Archlinux. Not sure when 5.9.1 will be released to you by OpenSUSE but chances are, that the bug got fixed in the meantime.

So if nobody else is able to reproduce, I would suggest you to wait for 5.9.1 and see if the problem persists. I will have my focus on the described behaviour in my daily usage of kontact, but I cannot remember that something alike happend to me in the past.
Comment 4 paul vixie 2018-09-18 08:49:14 UTC
suse tumbleweed upgraded kmail to v5.9.1 today.

i was able to reproduce the + behaviour i described earlier.

but only when i was on the last previously-read message, and new unread messages had been received. + gave me a double selection: keeping the last previously-read message, but also selecting the first of the newly-received unread messages.

v5.9.1 fixes a lot of other things related to mailbox and imap server asynchrony, so i am extremely grateful to all who participate as devs here. i don't know KDE or C++, so i'm strangely limited to being just-a-user of this software.

please do not take any of my bug reports as critical of anyone's skills or motives -- i am trying to help with feedback of any kind.
Comment 5 Christian Kalkhoff 2018-09-20 18:31:22 UTC
I still cannot reproduce. But I have had similar issues regarding the last message in the list. When I deleted them, the message list went empty and i had to switch to anouther folder and back to get the list again.

That might be related somehow, but is just a guess.
Comment 6 Justin Zobel 2022-11-30 05:28:14 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 7 Bug Janitor Service 2022-12-15 05:14:10 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Bug Janitor Service 2022-12-30 05:24:46 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!