Closed Bug 539166 Opened 16 years ago Closed 16 years ago

unread message count in dock icon too high

Categories

(Thunderbird :: OS Integration, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 516477

People

(Reporter: gary, Unassigned)

Details

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.6) Gecko/20091201 Firefox/3.5.6 GTB6 Build Identifier: 8.0b8 the unread message count in the dock icon is too high, exaggerating the actual unread count. Reproducible: Always
Problem is present in Thunderbird 3 as well. Assigning there.
Assignee: mozilla-bugs → nobody
Product: Penelope → Thunderbird
QA Contact: general → general
Version: unspecified → 3.0
Component: General → OS Integration
QA Contact: general → os-integration
Whiteboard: dupme
Gary this happeans only in smart folders?
this is happening with my Inbox. Only my Inbox has unread messages, 58 in total. the dock shows 118. note that in eudora 8.0b6 (based on Tb 3.0 beta ?), the dock almost always showed 1 unread message.
I see this as well. I think it is associated with the Message Synchronizing. If this is turned on the counts are high by a factor of two. If it is off it seems to work correctly (I just tried this so I'm not 100% sure of this yet). Another peculiarity is that if one explicitly clicks the "Get Mail" button then it doesn't occur. However, if TB find the mail on its own the factor of two error occurs. I will test this observations more but hope this will help someone in tracking down what is wrong. I do find this bug annoying.
No I spoke to soon. The problem persists even after Message Synchronizing. It just takes a while for it show up (i.e., the counts are correct for a while and then get off by a factor of two). I am surprised there is not more noise about this. Do most people not see it?
i am observing the same behaviour. the count is correct for a while, and then becomes 2x.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Whiteboard: dupme
You need to log in before you can comment on or make changes to this bug.