Bug 286054

Summary:	sometimes mails cannot be marked read
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Milian Wolff <mail>
Component:	Mail Filter Agent	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	amantia, martin+kde
Priority:	NOR
Version:	GIT (master)
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	screenshot showing this issue

Description Milian Wolff 2011-11-07 22:00:03 UTC

Version:           Git (master)
OS:                Linux

again, not sure whether this is related to filtering but afaik I only see it in my dimap account that gets filled via filters from another pop3 account.

now the bug: sometimes I see new mail in my dimap account, but when I read them they are not marked "unread". restarting kmail fixes this problem. note: I can delete or move these mails without problems.

Reproducible: Sometimes

Steps to Reproduce:
not sure, maybe again the filter setup ...

Actual Results:  
mail stays "unread" even though I just read it...

Expected Results:  
always be able to mark unread mails as read

Comment 1 Milian Wolff 2011-11-07 22:02:14 UTC

Created attachment 65369 [details]
screenshot showing this issue

note how I selected the message but it's still marked as unread (closed envelope icon)

Comment 2 András Manţia 2012-10-13 19:01:55 UTC

This doesn't look like a filtering issue. Is it still reproducible?

Comment 3 Martin Bednar 2013-01-18 02:56:39 UTC

I'm seeing this on my 4.10 RC3 setup, definitely not related to filtering. A restart fixes it in the way that the mails can get marked as read. I haven't figured out a pattern (yet) as to when it happens.

Comment 4 Denis Kurz 2016-09-24 20:39:47 UTC

This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 5 Denis Kurz 2017-01-07 22:43:47 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.