166583 - newsgroup client indicates unread messages in tree, although there are none

Status: VERIFIED DUPLICATE of bug 59681

(MailNews Core :: Networking: NNTP, defect)

Description

[Jacob Hallenoborg]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826

In the tree to the left of the newsgroup client, unread messages are indicated
within parentheses eg. (3). Sometimes these alleged messages can't be found in
the main window to the right.

Reproducible: Sometimes

Steps to Reproduce:
1.Login to the newsgroup atlas.dsv.su.se at port 1199.
2.Look at the tree to the right, and find eg. p.i.a.3 (3).
3.Look for the messages above in the right window, in vain.

Actual Results:  
No unread messages found.

Expected Results:  
It should not indicate unread messages at all.

Comment 1

[Boris 'pi' Piwinger]

This is a dupe. Depending on your answer to the following question we can
determine to which one:

Does the number go away when you enter the group? Or do you have to mark the
group read by hand?

pi

Comment 2

[[e-mail] (gone - use [e-mail] instead)]

No answer yet.  Please reopen if you have answers to Boris' questions, thanks.

Comment 3

[Jacob Hallenoborg]

I'm sorry, didn't see Your question until now. 
Answer: When I go to the group, the number disappears for a while, 
only to reappear some twenty seconds later. 

Comment 4

[Boris 'pi' Piwinger]

What do you do in those seconds before it reappears?

pi

Comment 5

[Jacob Hallenoborg]

Nothing really. Sometimes I read some messages, somtimes I do something else
(not touching Mozilla at all). It doesn't seem to matter.
/j

Comment 6

[Boris 'pi' Piwinger]

Hm, actually the number should not change as long as you stay in the same group.
Maybe you can log the NNTP dialogs:
http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html
And then attach it to this bug.

pi

Comment 7

[Boris 'pi' Piwinger]

Does the problem still occur? If so, please produce some log file.

pi

Comment 8

[Jacob Hallenoborg]

This log comes from the followong actions:
- I start the News client
- I click on the group where there is supposed to be a unread message, and the 
   indicator disappears. 

/jacob

0[2c42d8]: (247f9a0) setting busy to 0
0[2c42d8]: (247f9a0) creating
0[2c42d8]: (247f9a0) initializing, so unset m_currentGroup
0[2c42d8]: (247f9a0) setting busy to 1
0[2c42d8]: (247f9a0) opening connection to atlas.dsv.su.se on port 1199
0[2c42d8]: (247f9a0) setting busy to 1
0[2c42d8]: (247f9a0) ParseURL
0[2c42d8]: (247f9a0) fullPath = /
0[2c42d8]: (247f9a0) m_messageID = (null)
0[2c42d8]: (247f9a0) group = (null)
0[2c42d8]: (247f9a0) commandSpecificData = (null)
0[2c42d8]: (247f9a0) m_key = -1
0[2c42d8]: (247f9a0) Next state: NNTP_RESPONSE
0[2c42d8]: (247f9a0) Receiving: 200 Welcome to CoffeeLink News Server
http://www.burton-computer.com
0[2c42d8]: (247f9a0) Next state: NNTP_LOGIN_RESPONSE
0[2c42d8]: (247f9a0) Next state: NNTP_SEND_MODE_READER
0[2c42d8]: (247f9a0) Sending: MODE READER

0[2c42d8]: (247f9a0) Next state: NNTP_RESPONSE
0[2c42d8]: (247f9a0) Receiving: 200 Welcome to CoffeeLink News Server
http://www.burton-computer.com
0[2c42d8]: (247f9a0) Next state: NNTP_SEND_MODE_READER_RESPONSE
0[2c42d8]: (247f9a0) Next state: SEND_FIRST_NNTP_COMMAND
0[2c42d8]: (247f9a0) Next state: NEWS_DISPLAY_NEWS_RC
0[2c42d8]: (247f9a0) Sending: GROUP public.ip1.a.1

0[2c42d8]: (247f9a0) Next state: NNTP_RESPONSE
0[2c42d8]: (247f9a0) Receiving: 211 77 1 80 public.ip1.a.1 group selected
0[2c42d8]: (247f9a0) Next state: NEWS_DISPLAY_NEWS_RC_RESPONSE
0[2c42d8]: (247f9a0) Next state: NEWS_DISPLAY_NEWS_RC
0[2c42d8]: (247f9a0) Sending: GROUP public.ip1.a.2

0[2c42d8]: (247f9a0) Next state: NNTP_RESPONSE
0[2c42d8]: (247f9a0) Receiving: 211 86 1 88 public.ip1.a.2 group selected
0[2c42d8]: (247f9a0) Next state: NEWS_DISPLAY_NEWS_RC_RESPONSE
0[2c42d8]: (247f9a0) Next state: NEWS_DISPLAY_NEWS_RC
0[2c42d8]: (247f9a0) Sending: GROUP public.ip1.a.3

0[2c42d8]: (247f9a0) Next state: NNTP_RESPONSE
0[2c42d8]: (247f9a0) Receiving: 211 75 1 77 public.ip1.a.3 group selected
0[2c42d8]: (247f9a0) Next state: NEWS_DISPLAY_NEWS_RC_RESPONSE
0[2c42d8]: (247f9a0) Next state: NEWS_DISPLAY_NEWS_RC
0[2c42d8]: (247f9a0) Sending: GROUP public.ip1.a.4

0[2c42d8]: (247f9a0) Next state: NNTP_RESPONSE
0[2c42d8]: (247f9a0) Receiving: 211 49 1 50 public.ip1.a.4 group selected
0[2c42d8]: (247f9a0) Next state: NEWS_DISPLAY_NEWS_RC_RESPONSE
0[2c42d8]: (247f9a0) Next state: NEWS_DISPLAY_NEWS_RC
0[2c42d8]: (247f9a0) Sending: GROUP public.ip1.a.6

0[2c42d8]: (247f9a0) Next state: NNTP_RESPONSE
0[2c42d8]: (247f9a0) Receiving: 211 17 1 21 public.ip1.a.6 group selected
0[2c42d8]: (247f9a0) Next state: NEWS_DISPLAY_NEWS_RC_RESPONSE
0[2c42d8]: (247f9a0) Next state: NEWS_DISPLAY_NEWS_RC
0[2c42d8]: (247f9a0) Sending: GROUP public.ip1.a.5

0[2c42d8]: (247f9a0) Next state: NNTP_RESPONSE
0[2c42d8]: (247f9a0) Receiving: 211 74 1 74 public.ip1.a.5 group selected
0[2c42d8]: (247f9a0) Next state: NEWS_DISPLAY_NEWS_RC_RESPONSE
0[2c42d8]: (247f9a0) Next state: NEWS_DISPLAY_NEWS_RC
0[2c42d8]: (247f9a0) Sending: GROUP public.ip1.a.7

0[2c42d8]: (247f9a0) Next state: NNTP_RESPONSE
0[2c42d8]: (247f9a0) Receiving: 211 27 1 27 public.ip1.a.7 group selected
0[2c42d8]: (247f9a0) Next state: NEWS_DISPLAY_NEWS_RC_RESPONSE
0[2c42d8]: (247f9a0) Next state: NEWS_DISPLAY_NEWS_RC
0[2c42d8]: (247f9a0) Sending: GROUP public.ip1.a.8

0[2c42d8]: (247f9a0) Next state: NNTP_RESPONSE
0[2c42d8]: (247f9a0) Receiving: 211 8 1 9 public.ip1.a.8 group selected
0[2c42d8]: (247f9a0) Next state: NEWS_DISPLAY_NEWS_RC_RESPONSE
0[2c42d8]: (247f9a0) Next state: NEWS_DISPLAY_NEWS_RC
0[2c42d8]: (247f9a0) Sending: GROUP public.ip1.misc

0[2c42d8]: (247f9a0) Next state: NNTP_RESPONSE
0[2c42d8]: (247f9a0) Receiving: 211 136 1 137 public.ip1.misc group selected
0[2c42d8]: (247f9a0) Next state: NEWS_DISPLAY_NEWS_RC_RESPONSE
0[2c42d8]: (247f9a0) Next state: NEWS_DISPLAY_NEWS_RC
0[2c42d8]: (247f9a0) Sending: GROUP public.ip1.a.9

0[2c42d8]: (247f9a0) Next state: NNTP_RESPONSE
0[2c42d8]: (247f9a0) Receiving: 211 2 1 2 public.ip1.a.9 group selected
0[2c42d8]: (247f9a0) Next state: NEWS_DISPLAY_NEWS_RC_RESPONSE
0[2c42d8]: (247f9a0) Next state: NEWS_DISPLAY_NEWS_RC
0[2c42d8]: (247f9a0) Sending: GROUP public.ip1.test

0[2c42d8]: (247f9a0) Next state: NNTP_RESPONSE
0[2c42d8]: (247f9a0) Receiving: 211 39 1 39 public.ip1.test group selected
0[2c42d8]: (247f9a0) Next state: NEWS_DISPLAY_NEWS_RC_RESPONSE
0[2c42d8]: (247f9a0) Next state: NEWS_DISPLAY_NEWS_RC
0[2c42d8]: (247f9a0) Sending: GROUP public.is.a.5

0[2c42d8]: (247f9a0) Next state: NNTP_RESPONSE
0[2c42d8]: (247f9a0) Receiving: 211 0 0 0 public.is.a.5 group selected
0[2c42d8]: (247f9a0) Next state: NEWS_DISPLAY_NEWS_RC_RESPONSE
0[2c42d8]: (247f9a0) Next state: NEWS_DISPLAY_NEWS_RC
0[2c42d8]: (247f9a0) Next state: NEWS_DONE
0[2c42d8]: (247f9a0) Next state: NEWS_FREE
0[2c42d8]: (247f9a0) CleanupAfterRunningUrl()
0[2c42d8]: (247f9a0) setting busy to 0
0[2c42d8]: (247f9a0) setting busy to 1
0[2c42d8]: (247f9a0) setting busy to 1
0[2c42d8]: (247f9a0) ParseURL
0[2c42d8]: (247f9a0) fullPath = /public.ip1.a.3
0[2c42d8]: (247f9a0) m_messageID = (null)
0[2c42d8]: (247f9a0) group = public.ip1.a.3
0[2c42d8]: (247f9a0) commandSpecificData = (null)
0[2c42d8]: (247f9a0) m_key = -1
0[2c42d8]: (247f9a0) Next state: SEND_FIRST_NNTP_COMMAND
0[2c42d8]: (247f9a0) Sending: GROUP public.ip1.a.3

0[2c42d8]: (247f9a0) Next state: NNTP_RESPONSE
0[2c42d8]: (247f9a0) Receiving: 211 75 1 77 public.ip1.a.3 group selected
0[2c42d8]: (247f9a0) Next state: SEND_FIRST_NNTP_COMMAND_RESPONSE
0[2c42d8]: (247f9a0) Next state: SETUP_NEWS_STREAM
0[2c42d8]: (247f9a0) Next state: NNTP_XOVER_BEGIN
0[2c42d8]: (247f9a0) SetCurrentGroup to public.ip1.a.3
0[2c42d8]: (247f9a0) Next state: NNTP_FIGURE_NEXT_CHUNK
0[2c42d8]: (247f9a0) Next state: NEWS_PROCESS_XOVER
0[2c42d8]: (247f9a0) Next state: NEWS_DONE
0[2c42d8]: (247f9a0) Next state: NEWS_FREE
0[2c42d8]: (247f9a0) CleanupAfterRunningUrl()
0[2c42d8]: (247f9a0) setting busy to 0

Comment 9

[Jacob Hallenoborg]

I'm sorry that I missed the attachment facicility of bugzilla. Maybe I should
add that indicator reappears after some time, even if I turn off the "Check for
new message every X minutes". 
/jacob

Comment 10

[Boris 'pi' Piwinger]

Sorry, I could not help you so far. Maybe you can find something in bug 71728.

pi

Comment 11

[Boris 'pi' Piwinger]

Could you find something in bug 71728? Does a new build still show the problem?

pi

Comment 12

[Jacob Hallenoborg]

This bug actually resembles #59681, perhaps this is a duplicate. But it's still
 unresolved, even with Mozilla 1.3a build 2002113004 I'm running now.

/jacob

Comment 13

[Boris 'pi' Piwinger]

Marking as dupe then.

pi

*** This bug has been marked as a duplicate of 59681 ***

Comment 14

[Stephen Donner [:stephend] Not actively reading bugmail]

Verified dup