Closed Bug 263222 Opened 21 years ago Closed 21 years ago

Erroneous total message count in folder pane

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 223091

People

(Reporter: mozilla.org, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3 As shown in this picture, Thunderbird is not reporting right count of messages : http://libre-essai.com/ThunderbirdIsCrazy.jpg Reproducible: Always Steps to Reproduce: 1.Use Thunderbird for a few weeks. I restarted the program to no improvement.
Confirming based on screenshot. Possibly related to bug 260588.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Oh, wait -- which version of Thunderbird are you running? Those column headers for the folder pane no longer appear (at least, they don't appear by default, and I don't know how to enable them if that's possible).
Summary: Erroneous message count in left pane → Erroneous total message count in folder pane
(In reply to comment #2) > Oh, wait -- which version of Thunderbird are you running? Those column headers > for the folder pane no longer appear (at least, they don't appear by default, > and I don't know how to enable them if that's possible). I'm using version 0.8 (20040913). At the top of left pane, on the right, you have a very small button that gives you access to optional column headers : Unread, Total, Size.
(In reply to comment #3) > > Those column headers for the folder pane no longer appear > > At the top of left pane, on the right, you have a very small button that gives > you access to optional column headers : Unread, Total, Size. OK, I found it -- there's an advanced option to enable column headers, which I had turned off.
*** This bug has been marked as a duplicate of 223091 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.