Open
Bug 217940
Opened 21 years ago
Updated 2 years ago
Newsgroup entry bold but without unread/new messages
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
NEW
People
(Reporter: peter, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: Read comment #15 before commenting or duping)
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030830 Firebird/0.6.1+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030830 Firebird/0.6.1+ I've got a newsgroup which has 0 unread and 0 new messages in it. When i select the News account OR the news group in the sidebar and hit "Get Mail" the newsgroup entry is bolded and the count of messages is displayed after the name of the newsgroup. Example: <bold>a.foobar (400)</bold> To have it displayed correctly i need to leave the newsgroup (select a different) and reselect it. Then its displayed like i expect: a.foobar Reproducible: Always Steps to Reproduce:
Updated•21 years ago
|
QA Contact: asa
Comment 1•20 years ago
|
||
This is probably related to same problem and have existed for a some time in thunderbird. If I have selected newsgroup where there is no new messages and then new messages scan noticed a new posting in it. It correctly shows new messages in sidebard but no new messages is seen in messages view. Need to select another newsgroup and then go back to old one to see new messages.
Comment 2•20 years ago
|
||
For me it happens the other way around. If I scan for new mail, the news account sometimes shows the total number of messages on the server (not the number I have downloaded). Then when I re-select the newsgroup the number is corrected (typically back to 1, or to none at all) This image shows what happens after I scan for new mail
Comment 3•20 years ago
|
||
...And this second screen grab shows what happens once I display the newsgroup. This happens regularly. But not very time. It is not every newsgroup - sometimes the 1st and 4th are affected, sometimes the 1st and 2nd. But if it is going to happen at all, the 1st one on my list is /always/ affected. The first one does not have to be uk.local.east-anglia, it has happened with a different group in that position. I am using the server at News.Individual.NET (http://www.individual.net/) This is, of course "minor". But annoying, and not very swish.
Comment 4•20 years ago
|
||
Is this a duplicate of bug 245589 ? If so, has bug 245044 fixed this ? or is it something to do with bug 249337 ? (I only display threads with unread messages)
Thunderbird v0.9 (official build) I have the same problem where the unread count for various newsgroups is all over the place, it doesn't reflect reality. It seems that the markers in the configuration files become corrupted, I have to get in and edit them by hand once in a while. It doesn't look like the range and list approach is robust in the implementation. I lot of the times I end up with a list of read messages when they could be converted to a range, e.g. a.b.c.foo: 1,2,3,4,5,6,7,8-50 When it could be: a.b.c.foo: 1-50 As soon as I fix it by hand the unread count is back to being correct, for a while, until it breaks again ...
Comment 6•20 years ago
|
||
My problems persist in version 1.0
Comment 7•20 years ago
|
||
(In reply to comment #6) > My problems persist in version 1.0 But only with one group (uk.local.lincolnshire) on one server (news.individual.net). I have tried the parameter file edit mentioned above, and it broke again soon after. Currently it always says 106 messages, regardless...
Comment 8•19 years ago
|
||
The problem is still present in version 1.0.2. Furthermore, in such accounts, there are underlined threads (even though each message in theses threads are marked as read). And I do not manage to mark the whole thread as read... Perhaps related to bug 71728 and bug 208082 ?
Comment 9•19 years ago
|
||
*** Bug 304037 has been marked as a duplicate of this bug. ***
Comment 10•18 years ago
|
||
I have a similar problem but I don't know if it's related to the same bug: With the inbox is selected, I click on the (+) next to the news account. First, the news groups are displayed without any unread messages. Then, the status bar information tells me TB is checking for messages. Now, one or more groups show either 1 or 2 unread messages. I'm still viewing the contents of the inbox at this point. As soon as I click on the news group so that its messages are displayed, the number of unread messages disappear and the caption for the group is un-bolded. Repeatable any number of times by selecting the in-box, clicking the (-) next to the news account so the groups are hidden, and then pressing (+). TB version 1.5 (20051201)
Comment 11•18 years ago
|
||
dups? bug 320301? (XP) bug 335338? (linux)
Comment 12•17 years ago
|
||
I see occasionally where the IDs in the newsrc file get out of sync. I need to adjust that file to make the IDs contiguious and the "phantom messages" go away. I guess the server said a post didn't exist at one point so the lost ID got stuck.
Updated•17 years ago
|
QA Contact: front-end
Updated•17 years ago
|
Blocks: messagecount
Comment 15•16 years ago
|
||
I see several different issues in this bug, IIUC. Description, which I take to mean this: <b>random.newsgroup </b> (notice no unread count); i.e., the biff state claims new but with no new messages. Comment 1: The newsgroup says no new messages when there really is some. Most likely not a problem since it may just indicate that a new message has been posted since our last biff. Comments 2-4, 6-7: Most likely a combination of bug 311774 and bug 71390. Comment 5,12: Extremely vague, but sounds like bug 71390 again. Comment 8: Definitely 71390. Comment 9: Vague again, but does sound like description Comment 10: Probably bug 311774 Comment 11, 13: different problems. Comment 14: Another vague bug (a lot of those, aren't there?), but it can be construed to be the description or a hodgepodge of 71728 deps, mostly 311774, 71390, and 24592.
Whiteboard: Read comment #15 before commenting or duping
Updated•16 years ago
|
Assignee: mscott → nobody
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•