Bug 334270 - Marking thread does not apply colors to new received messages
Summary: Marking thread does not apply colors to new received messages
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: Git (master)
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL: https://drive.google.com/file/d/0B-ih...
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-03 07:44 UTC by kdeuser56
Modified: 2017-01-07 22:02 UTC (History)
2 users (show)

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 kdeuser56 2014-05-03 07:44:09 UTC
If you have a thread and mark it, the color is applied to all mails of that thread as expected, but if a new mail arrives it seems to be marked internally, but the color is not applied.
I think I could also reproduce this on 4.13, but I am not completely sure, so to be safe, I mark it against 4.11.5 where I am sure the issue is present.
The issue can be seen in a thread in the following screencast: https://drive.google.com/file/d/0B-ihXi2hkCPfY0JkQW9BczlSdjg/edit?usp=sharing


Reproducible: Always
Comment 1 kdeuser56 2014-05-03 08:12:08 UTC
Okay affects current master too.
I am not sure if my bug report is a duplicate of the following bugs:
https://bugs.kde.org/show_bug.cgi?id=310737
https://bugs.kde.org/show_bug.cgi?id=277454

I am having this issue on an imap account (gmail), it is reproducible every time.
Comment 2 Denis Kurz 2016-09-24 18:02:44 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:02:12 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.