530059 - Some threads with all messages read are still visible in "Threads->read with new messages" view

Status: RESOLVED INCOMPLETE

(MailNews Core :: Database, defect)

Description

[Wojtus]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; pl; rv:1.9.1.4) Gecko/20091017 SeaMonkey/2.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; pl; rv:1.9.1.4) Gecko/20091017 SeaMonkey/2.0

I'm using "Threads -> Read with new messages" view option (may be named a bit differently, I'm not using english SeaMonkey). If a newsgroup have no unread messages, the thread/messages panel should appear empty. If there are unread messages, threads containing them should be listed.

However, in circumstances still unknown to me, sometimes a thread is going "panzer" and is always displayed, despite having all it's messages read. See URL with the screenshot. There's no way to make this thread "read" apart from resubscribing newsgroup from the scratch.

The "panzer" thread is not watched, marked, no filtering is used.

The "panzer" state is permanent, does not change if SeaMonkey is restarted.

The "panzer" threads happened to me several times, but unfortunately I cannot give you the steps to make a thread "panzer". It happens randomly(?) with normal day-to-day usenet reading.

Reproducible: Couldn't Reproduce

Steps to Reproduce:
This is only how to reproduce the view with "panzer" thread. I don't know how to create one.

1. Open MailNews
2. Select a newsgroup with "panzer" thread
3. Make sure the "Threads -> Read with new messages" view is enabled
4. Mark group as read
5. Select another newsgroup
6. Select a problematic newsgroup again
Actual Results:  
Some threads (I call them "panzer") are displayed in the messages panel. They contain no unread messages, and are not printed in bold.

Expected Results:  
Empty messages panel.

I can provide SeaMonkeys internal newsgroup files which I believe you could use to reproduce the buggy behaviour.

Comment 1

[Wojtus]

Attachment: SeaMonkeys newsgroup files with "panzer" threads

Comment 2

[Wojtus]

It's still not fixed. I've found an old bug which had very same symptoms: #64476.

Comment 3

[[:Aureliano Buendía]]

Wojtus, bug #64476 is now fixed: could you confirm that your issue is fixed too? I assume that this issue is a dupe of bug #64476

Comment 4

[Joshua Cranmer [:jcranmer]]

RESOLVED INCOMPLETE due to lack of response to previous question. If you feel this change was made in error, please respond to this bug with your reasons why.