Bug 285063 - Thread marked as "Unread" goes back to "Read" after some time
Summary: Thread marked as "Unread" goes back to "Read" after some time
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: message list (show other bugs)
Version: 4.7
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-27 07:26 UTC by Elias Probst
Modified: 2017-01-07 22:47 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 Elias Probst 2011-10-27 07:26:57 UTC
Version:           4.7 (using KDE 4.7.2) 
OS:                Linux

When marking a thread as "Unread", all mails in this thread go back to the "Read" state after some time.
Account is IMAP on a Citadel Groupware server.

Reproducible: Always

Steps to Reproduce:
→ Open Kontact/KMail2
→ Select a thread
→ Rightclick on the root mail of the thread
→ Select "Mark Thread as" → "Unread"
→ Continue to work with KMail in other folders/accounts/etc.
→ Return to initial mailfolder after some minutes and check the read/unread state of the thread

Actual Results:  
→ The thread is marked as read again

Expected Results:  
→ The thread shouldn't go back to "Read" without explicitely requesting it by clicking on mails of the thread or using "Mark Thread as" → "Read"
Comment 1 Silver Salonen 2012-02-10 09:19:52 UTC
Although it's about the entire thread, maybe it's still duplicate of 276856?
Comment 2 Denis Kurz 2016-09-24 18:07:14 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 3 Denis Kurz 2017-01-07 22:47: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.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.