Bug 352833 - Message list cleared after deleting top message
Summary: Message list cleared after deleting top message
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: message list (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-17 11:14 UTC by der_fenix
Modified: 2018-01-31 16:51 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description der_fenix 2015-09-17 11:14:14 UTC
Almost everytime I delete top message from messages list in inbox all other messages dissapears. Switch to another folder and then switch back - returns other messages.

Tryed to reproduce this within other folders, but with no luck. Tryed to move some messages in inbox and then reproduce - no luck too. Move messages, mark them as unreaded - first top message was deleted without the bug, on second - other messages dissapears again.

Reproducible: Sometimes

Steps to Reproduce:
1. Have some unread mail in your inbox (may be in other too, but only with short messages list)
2. Delete messages one by one from top

Actual Results:  
Messages list become visually empty, but messages still present - you can switch to another folder and switch back to get messages list back.
Comment 1 Rajeev Bhatta 2015-09-17 18:22:09 UTC
It happens to me too... though not every time...  Once I remove or move the 1st message in the list the message list disappears and only appears after going to another folder and coming back.
Comment 2 Denis Kurz 2017-06-23 20:16:43 UTC
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.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 opportunity 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.
Comment 3 Denis Kurz 2018-01-31 16:51:49 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input.