Build ID: 2001-11-05-03, Windows 2000. Summary: Unread counts toggle back and forth between twisty open and selection. Steps to Reproduce: 1. Subscribe to a number of newsgroups (4 will work) on news.mozilla.org. 2. Get all headers, shutdown. 3. Upon restart, goto your collapsed newsgroups and open the twisty. 4. Notice the unread counts. 5. Select each newsgroups. 6. Notice the unread counts. 7. Now, go back and close/reopen the twisty. The values get reset. Expected Results: They shouldn't be different, since we do the equiv of biff when you open a twisty. Actual Results: I had the following after doing step (3): Newsgroup name (unread count) ---------------------------- n.test (80) n.p.test (40) n.p.m.performance (18) n.p.m.mail-news (4697) After making a selection on each group (step (5)): n.test (81) n.p.test (46) n.p.m.performance (16) n.p.m.mail-news (4696)
adding shiny nsbeta1 keyword
16 years ago
this sounds very similiar to bug 59681 (which is also listed as blocker of 71728)
*** Bug 136587 has been marked as a duplicate of this bug. ***
*** Bug 136859 has been marked as a duplicate of this bug. ***
Bug 136859 is almost identical, with one exception: - Almost all of the newsgroups have correct number of news - The ones with wrong number get 0 read news each time the newsgroup reader is opened, and 7 read news when the newsgroup is selected! - This occures even if the newsgroups is practically dead (one of them got a total of 6 messages). The number of unread news drop to 0 again if one of the newspostings get selected... I changed to build 2002042221 and the number of news have been correct, except on a few newsgroups.
One last comment: This bug is originally reported as a bug on Windows, I got it on RedHat 7.2
15 years ago
*** Bug 160534 has been marked as a duplicate of this bug. ***
*** Bug 187711 has been marked as a duplicate of this bug. ***
In my long experience, the problem finds its way onto a newsgroup, and then there's no way to get rid of it. The higher number is a constant (for the time being) added to the actual unread count, and the lower number is the actual unread count. The higher number appears when you open the twisty or press Get Msgs. The lower number appears when you open the newsgroup, read an unread message or toggle the read/unread status of a message. But I don't know why half of them increased at step 5 of the reporter's example (maybe something has changed here since). And it isn't related to ignored threads, or to having not downloaded all headers when there are more than specified in the 'Ask me before downloading more than xxx messages' pref. Is anyone still working on this? For that matter, why is it ASSIGNED even though the assignee has never touched this bug?
Maybe this bug is not progressing because it's assigned to someone who stopped working on this over a year ago (if I'm not mistaken).
*** Bug 280448 has been marked as a duplicate of this bug. ***
11 years ago
is this gone for you all? WFM TB version 3.0a1pre (2007100604)
Wayne, still as bad as ever in nightly from 2007100703
Yep, confirmed with Linux 220.127.116.11pre. Nelson, what's the newsrc? The group in question has the line: mozilla.test: Another newsrc problem?
> Nelson, what's the newsrc? Joshua, I don't know how to answer your question. Do you want the file pathname? Snapshots of the file before & after the events that change the unread counts?
(In reply to comment #15) > > Nelson, what's the newsrc? > Joshua, I don't know how to answer your question. > Do you want the file pathname? > Snapshots of the file before & after the events that change the unread counts? The text of the file, or even just the lines of the group in question. If my reasoning is correct, then the time shouldn't matter.
I can reproduce this bug in a nightly. What files are you referring from in comment 16 that would help you debug?
The contents of the newsrc file (either News/<server>.rc or News/newsrc-<server>, relative from the profile directory).
It shows the faulty unread count, for an example: >mozilla.dev.tech.gfx: 1-374,378-385 is actually all read, and displays 3 unread in the faulty case.