377483 - Thuderbird 2 RC1 shows incorrect unread message count for folders

Status: RESOLVED DUPLICATE of bug 261201

(Thunderbird :: Mail Window Front End, defect)

Description

[(no longer active)]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3 Creative ZENcast v1.02.10
Build Identifier: version 2.0.0.0 (20070326)

I'm running Thunderbird 2 RC1 with a profile set to use a global Inbox.  Thunderbird shows incorrect unread message count for folder during usage.  Here is what I have managed to gather about this behavior:

1. Most of the time it happens in Inbox, but it does happen in other mail *and* RSS folders.
2. Most of the time, when the number of unread messages for a folder is incorrect, clicking on it and navigating to the folder solves the problem, *but* that's not always the case.
3. The problem happens in three forms (sorted in order of maximum occurrence.):
  a) the unread message count is 0, but there are unread messages in the folder).
  b) the unread message count is less than the actual unread message count.
  c) the unread message count is more than the actual unread message count.
4. Marking a read message as unread solves this problem *most* of the time (but not always.)
5. Restarting Thunderbird solves the problem *most* of the time (but not always.)
6. The unread message count shown in folder view is always at sync with the one shown on the status bar when the folder is active.
7. Sometimes in the (a) state above, the folder name appears bold in the folder list, other times it does not.
8. During a typical usage session, I see this inconsistency quite a few times, but I have not yet been able to reproduce the problem reliably.

Reproducible: Sometimes

Comment 1

[(no longer active)]

This bug still happens in Thunderbird 2.0.0.4.  Is there any way for me to provide useful data to debug this problem?

Comment 2

[Ryan Hayle]

Please confirm whether this happens in a 3.0 nightly build, and if so, try to narrow down the problem and ensure there isn't an existing bug report covering this issue.