GNOME Bugzilla – Bug 576430
Search folders show wrong number of unread messages
Last modified: 2011-10-07 05:35:52 UTC
Search folders still not working. They show wrong number of unread messages and the only way to get it to update is to change the filter(s). Distribution: Fedora release 10 (Cambridge) Gnome Release: 2.24.3 2009-01-16 (Red Hat, Inc) BugBuddy Version: 2.24.2
Thanks for taking the time to report this bug. This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to this bug.
Can you please try 2.24.5 or 2.26.1.1 and report back, thanks.
Have tried 2.24.5 and my Search Folders still show that there is unread messages in some of the folders, but all messages is read. When a new message arrive the search folder indicate that a message is unread, but reading it does not make the folder update only if I read the mail in the search folder. Normally I just read the mail in the "Unread" search folder or the "Inbox" itself.
Is now on 2.26.2 and Search Folders is still not behaving corretly, ex: I have a search folder called "fedora-devel-list" the filter is "fedora-devel-list@redhat.com" (mailinglist) and is using my IMAP INBOX, is shows like: "fedora-devel-list (18)" meaning there is 18 unread messages in this folder, but there is no unread messages in the INBOX, so the folder is wrong. The folders do update sometimes, but is always showing the wrong numbers, unless you read the messages from the folder. If I read the messages directly in the INBOX all the search folders is wrong, they don't update. Really no one else have this problem.
*** Bug 580408 has been marked as a duplicate of this bug. ***
*** Bug 570279 has been marked as a duplicate of this bug. ***
*** Bug 569986 has been marked as a duplicate of this bug. ***
*** Bug 563947 has been marked as a duplicate of this bug. ***
*** Bug 563118 has been marked as a duplicate of this bug. ***
*** Bug 549913 has been marked as a duplicate of this bug. ***
This might be fixed with bug #562912, could you retest with 3.0.3/3.1.90 or later, please? Both will be released soon.
Closing this bug report as no further information has been provided. Please feel free to reopen the bug if the problem still occurs with a newer version of GNOME 3.2.0 or later, thanks.