Kmail doesn't seem so save the cursor position in the message list across restarts. For some reason it initially selects some old message in the list. I can't see the pattern which message it selects, it can be a week or a month old. Reproducible: Always Steps to Reproduce: 1. Open Kmail. 2. Select some message in the message list (I typically select the most recent one). 3. Quit Kmail and start it again. Actual Results: Kmail selects some random message in the list. Expected Results: Kmail should select the message I selected before closing it.
I can confirm this bug. I believe it showed up when I first installed KDE 4 in Fedora. It persists to this day. I'm on kmail 4.14.2. (I just reported another irritating bug vaguely related, bug 341114.)
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Due to many bugs in Kmail and PIM and apparently no support for it I stopped using Kmail long time ago, so I won't be able to test. The same goes about the other bugs I reported or participated in.
(In reply to Denis Kurz from comment #2) > This bug has never been confirmed for a KDE PIM version that is based on KDE > Frameworks (5.x). Those versions differ significantly from the old 4.x > series. Therefore, I plan to close it in around two or three months. In the > meantime, it is set to WAITINGFORINFO to give reporters the oportunity to > check if it is still valid. As soon as someone confirms it for a recent > version (at least 5.1, ideally even more recent), I'll gladly reopen it. > > Please understand that we lack the manpower to triage bugs reported for > versions almost two years beyond their end of life. This bug still persists. It has never been corrected. My current version is: kmail-16.12.3-1.fc25.x86_64 kmail-libs-16.12.3-1.fc25.x86_64
Thanks for the update; reopening.
I can also reproduce this with kmail 17.04.2-1.7 from openSUSE Leap 42.3. What kind of additional information can I provide?
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!
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!
I am not the original reporter, but I confirmed the bug. I can report that the bug seems to be fixed. kmail-22.08.1-1.fc37.x86_64
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!