Open Bug 301103 Opened 19 years ago Updated 2 years ago

[v1.8a1--] Displayed unread news message count resets to 0(zero) while it shouldn't, and unread message not "focused" in thread pane

Categories

(MailNews Core :: Database, defect)

x86
Windows 98
defect

Tracking

(Not tracked)

People

(Reporter: sgautherie, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: regression, Whiteboard: [Regression Timeframe: between MAS "v1.7.8" and v1.8a1])

[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.8) Gecko/20050511] (release) (W98SE)

Works fine: unread count not reseted to 0, and unread message "focused" in
thread pane.

[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b) Gecko/20050217] (<-- 1.8b1 !)
(W98SE)
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b3) Gecko/20050714 SeaMonkey/1.0a]
(nightly) (W98SE)
and
[Mozilla Thunderbird, version 1.0+ (20050319)] (nightly) (W98SE)

Steps: (one way to always reproduce)
1. Have a .rc file containing a line like "netscape.public.mozilla.seamonkey:
1-16749,16751" (== 1+ unread message "in-between")
2. Delete (all) .msf (and .dat) file
3. Start SM-MailNews/ThunderBird
4. Expand the related news server: the unread count shows 1 = fine.
5. Select the newsgroup; the headers are downloaded, then:

R. The unread count is reset to 0, and the thread pane stays at its top; instead
of "focusing" the unread message.
Flags: blocking1.8b4?
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8a1) Gecko/20040520] (release) (W98SE)

Already has this regression.
Summary: Displayed unread news message count resets to 0(zero) while it shouldn't, and unread message not "focused" in thread pane → [v1.8a1--] Displayed unread news message count resets to 0(zero) while it shouldn't, and unread message not "focused" in thread pane
Whiteboard: [Regression Timeframe: between MAS "v1.7.8" and v1.8a1]
Flags: blocking1.8b4? → blocking1.8b4-
Flags: blocking1.9a1?
[Netscape® Communicator 4.8 : en-20020722] (W98SE)

Works fine.

[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b4) Gecko/20050720 SeaMonkey/1.0a]
(nightly) (W98SE)

(Bug still there)
Keywords: 4xp
I have that bug with Thindebird version 1.5 (20051201). Sometimes I see unread messages in a newsgroup, but can't read them. When I focus on that group, the unread counter is decreased (sometimes to 0, and sometimes to some positive value, and then I can read so many messages). When I press "Get new message", the unread counter is increased again (or after some time passes and Thunderbird checks for new messages in the group), but again I can't read messages.
I have the same 'holes' in .rc file (for example, groupname: 1-25603,25604), and the number of messages in 'holes' is equal to the number of unread messages shown. I use to cure this by editing .rc file by hand filling the 'holes' (simply erasing all numbers inside leaving only 1-<final number>), but this is quite annoying and I am not sure I do not lose messages.
I see this bug since I began using Mozilla and in Thinderbird too, when I switched to it.
Forgot to say, I see this in Windows 2000 and Windows XP.
Flags: blocking1.9a1?
See dependency tree of meta Bug 71728. 
DUP of one of Bug 24592, Bug 34406, Bug 41457, Bug 79130, Bug 108650, Bug 202341.
Sorry but I don't know which bug is correct one to DUP.
QA Contact: database
Product: Core → MailNews Core
(In reply to comment #5)
> See dependency tree of meta Bug 71728. 
> DUP of one of Bug 24592, Bug 34406, Bug 41457, Bug 79130, Bug 108650, Bug
> 202341.
> Sorry but I don't know which bug is correct one to DUP.

Serge, still see this with current versions? your thoughts on this being a duplicate?
Assignee: dbienvenu → nobody

Marco, does this reproduce for you?

Flags: needinfo?(starless)

Sorry Wayne, I'm not sure I understand the description of the bug, especially the "focus" part. And I seldom use newsgroups nowadays.
I can tell you that - in version 78.14.0 on Mac - if I open a "newsserver tree" in the folder tree, so showing the subscribed newsgroups, a certain unread count is displayed for the newsgroups, but then when I select the single newsgroups the count can get lower. Intuitively it looks as if the count shown initially is some approximate number sent by the server, and then when you select the group the real number of unread messages is revealed (maybe meaning that some messages have been deleted or whatever).

Flags: needinfo?(starless)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.