GNOME Bugzilla – Bug 617659
Side pane shows unread mail although there is none
Last modified: 2010-10-01 08:18:59 UTC
Created attachment 160267 [details] Screenshot of evolution 2.30.0 main dialog: side pane vs. message list Sometimes when I move mail to another folder, evolution suddenly shows unread meal in that folder although there definitely is none. This behavior appeared in 2.30.x, I have never seen it before.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 588448 ***
I think that bug 588448 is what I reported here because - it was filed against 2.26.x while my problem only appeared after upgrading to 2.30.x and *never* before. - I was talking about local POP3 folders while bug 5884848 deals with IMAP. The problem does not appear with IMAP in fact. - My 'unread' mails are caused by moving messages which is not mentioned in bug 588448. Therefore I am reopening this bug now.
(In reply to comment #2) > I think that bug 588448 is what I reported here because > - it was filed against 2.26.x while my problem only appeared after upgrading to > 2.30.x and *never* before. That is why changed the version to 2.30.x in original bug. > - I was talking about local POP3 folders while bug 5884848 deals with IMAP. The > problem does not appear with IMAP in fact. see https://bugzilla.gnome.org/show_bug.cgi?id=588448#c4 > - My 'unread' mails are caused by moving messages which is not mentioned in bug > 588448. > This can be added in original bug it self. > Therefore I am reopening this bug now.
(In reply to comment #3) > see https://bugzilla.gnome.org/show_bug.cgi?id=588448#c4 According to that comment it was wrong to close bug 593698 a duplicate of bug 588448. You should have left it open mark this one a duplicate of bug 593698 since both deal with local folders. Should we do this now or do you prefer this one since it was filed using the template?
Similar bugs are filled against various providers (IMAP/local/...) and I believe it's because each provider uses pretty the same logic of unread counting and it's apparently "broken" for some cases. Having the exact steps what to do (as 'sometimes' doesn't count) would help to catch the corner cases and finally fix it. I agree with Akhil, with respect of duplicates, because duplicate-tree is leading up to bug #577542, which is just a generic bug report about incorrect unread counts on folders. I'm marking this bug as a duplicate of it. Also note that the bug seems to contain similar steps as you described above in bug #577542 comment #13. *** This bug has been marked as a duplicate of bug 577542 ***