381017 - After deleting unread message counter becomes negative

Status: RESOLVED WORKSFORME

(Thunderbird :: Mail Window Front End, defect)

Description

[bugzilla]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.4pre) Gecko/20070504 blub
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a5pre) Gecko/20070516 Thunderbird/3.0a1 ID:2007051603 [cairo]

After deleting unread message counter is set to a negative value in grouped view. See the attached picture.

Reproducible: Sometimes

Steps to Reproduce:
1. Have a Folder with some unread and some read messages
2. Delete some of the unread
Actual Results:  
Counter becomes negative

Expected Results:  
Counter stays positive

Comment 1

[bugzilla]

Attachment: Negative Counter

Comment 2

[Adam Guthrie]

And you're using a Thunderbird trunk build?

Comment 3

[Lee Houghton]

This looks like it could be the same as bug 423845, but mine looks more similar to this, so I'll comment here. I just encountered the bug today, I think it was caused by an email being automatically marked as spam. The group header afterwards showed as "Today (-1/2)" (and then "Today (-1/1)" when I actually deleted that email).

Using Shredder 3.0a2pre: version 3.0a2pre (2008070503)

Comment 4

[Lee Houghton]

Sorry for spam, but I meant bug 432845.

Comment 5

[Wayne Mery (:wsmwk)]

Lee, what results do you get with current beta? 
 ftp://ftp.mozilla.org/pub/thunderbird/nightly/latest-comm-1.9.1/

Comment 6

[Lee Houghton]

It's still there in my nightly build; it seems to be caused by a filter which automatically performs "Mark as Read".

To reproduce this bug, do the following:
 1. Add a message filter which will automatically mark messages as read when the subject contains "bug423845".
 2. Activate "Group by sort" on your inbox view.
 3. Read everything else from "Today" in your inbox, so that you have 0 unread messages in that group.
 4. Send a message to yourself with the subject "bug423845".
 5. Notice the unread message count becomes negative.

Comment 7

[Ludovic Hirlimann [:Usul]]

Kent any idea why the filter is messing up with the message count ?

Comment 8

[Kent James (:rkent)]

(In reply to comment #7)
> Kent any idea why the filter is messing up with the message count ?

Count and related errors are usually not hard to fix when they have a clear STR. I have not tried comment 6, but if accurate that would be enough. The "why" in this case is probably because the counts are being removed twice, but I would need to trace it out to see the real "why". 

I went on a count-fixing spree about a year ago. Someone (perhaps me) should do it again when the TB3 code base stabilizes, as the counts are very easy to break when people are doing reorganizations, like asuth is doing now.

Comment 9

[Wayne Mery (:wsmwk)]

let's assume valid on kent's rationale and get off unco list.

Comment 10

[:aceman]

Is this still happening?

Comment 11

[bugzilla]

(In reply to :aceman from comment #10)
> Is this still happening?

I haven't seen it in for a long time and cannot reproduce it easily with TB 16.