Closed
Bug 320301
Opened 19 years ago
Closed 13 years ago
New NNTP/News messages do not appear in an open folder until switching to another one and back or pressing "Get mail"
Categories
(MailNews Core :: Networking: NNTP, defect)
MailNews Core
Networking: NNTP
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: dee, Unassigned)
Details
(Whiteboard: [closeme 2011-03-01])
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50215) Build Identifier: When i am currently reading items in a nntp/news account, any new items appear in the unread count but do not appear in the folder. If I press "Get Mail" or swicth to another folder and back again, they do appear. I'd have thought this would be reported already but I cant find it. Reproducible: Always Steps to Reproduce: 1. Switch to a newsgroup folder in an NNTP account 2. Wait for a new item to be posted (Or post one yourself) 3. Wait for Thunderbird to pick it up Actual Results: The unread count increases, but the item does not appear in the folder list and "Next unread mail" wont go to it. Expected Results: The unread count should increase and the item should appear in the folder view. This happens regardless of server (I use news.jrsoftware.org, news.micorsoft.com and news.zen.co.uk), and I'm using 1.5RC2 (20051025)
Reporter | ||
Comment 1•18 years ago
|
||
This still happens on 1.5.0.2 (20060308). Forcing a "Gat Mail" makes it appear.
Reporter | ||
Comment 2•18 years ago
|
||
This is still an issue in 1.5.0.4 (20060516)
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 3•18 years ago
|
||
Oops, didn't mean to resolve it.
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Comment 4•18 years ago
|
||
I see something similar, sometimes clicking a newsgroup A doesn't show messages - I have to click another newsgroup and come back to newsgroup A - with trunk builds
Version: unspecified → 1.5
Comment 5•18 years ago
|
||
similar to bug 217940 comment 1
Comment 6•18 years ago
|
||
(In reply to comment #0) > When i am currently reading items in a nntp/news account, > any new items appear in the unread count but do not appear in the folder. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ They do? As far as I know, there are no checks back for new messages on any kind of timed basis. Manual 'Get New' or revisiting the newsgroup are the only ways I know of to update the count, let alone to load new headers.
Reporter | ||
Comment 7•18 years ago
|
||
(In reply to comment #6) > As far as I know, there are no checks back for new messages on any > kind of timed basis. Manual 'Get New' or revisiting the newsgroup > are the only ways I know of to update the count, let alone to load > new headers. I assume this is what the "Check for new messages every X minutes" option is for in the NTTP account settings. Manually "getting new" mail makes it appear in the post listing as well as just the group tree.
Comment 8•18 years ago
|
||
(In reply to comment #7) > I assume this is what the "Check for new messages every X minutes" option is > for in the NTTP account settings. duh, I'm an idiot. I believe this is the same as bug 365016. Altho that's a newer bug, it's confirmed, so if you agree it's the same, please dupe this bug to that one.
Comment 9•17 years ago
|
||
Mike in comment #8: > (In reply to comment #7) > > I assume this is what the "Check for new messages every X minutes" option is > > for in the NTTP account settings. > > duh, I'm an idiot. > > I believe this is the same as bug 365016. Mike, is clearing the problem by switching folders/newsgroups the only thing these bugs have in common? Dean, a) does your problem go back before v1.5? b) so you never have a problem with an explicit get new messages? It's only when you have X minutes set that messages don't show in the folder? note - if bug 217940 never went away and is related, then the problem may go back to 20030830
Reporter | ||
Comment 10•17 years ago
|
||
> Dean, a) does your problem go back before v1.5? Yes, I still run that at work and the problem still appears. I don't seem to remember it being an issue on 1.0 > b) so you never have a problem with an explicit get new messages? > It's only when you have X minutes set that messages don't show in > the folder? Exactly. The count increases in the folder list, but i need to "Get mail" to make them appear in the message list. > note - if bug 217940 never went away and is related, then the problem may go > back to 20030830 Bug 217940 is one i see occasionally where the newsrc file gets out of sync. I need to adjust that file to make the IDs contiguious and the "phantom messages" go away.
Comment 11•17 years ago
|
||
(In reply to comment #9) > Mike in comment #8: > > I believe this is the same as bug 365016. > > Mike, is clearing the problem by switching folders/newsgroups the only thing > these bugs have in common? That must be what I meant. I don't think I've reproduced the symptoms of this bug.
Reporter | ||
Comment 12•17 years ago
|
||
(In reply to comment #10) > > Dean, a) does your problem go back before v1.5? > Yes, I still run that at work and the problem still appears. > I don't seem to remember it being an issue on 1.0 Sorry, I misread. My comment still stands about not thinking its in 1.0.
Comment 13•17 years ago
|
||
Dean, is your problem gone with TB2 since bug 365016 was fixed on 3-24?
Reporter | ||
Comment 14•17 years ago
|
||
Nope, it still exists in 2.0.0.0 (20070326). It requires a manual F5 or "Get mail" before the new items appear in the post list. Am I the only one that can see reproduce behaviour? It does happen on two completely independant machines with different servers and groups (one running 1.5 , the other 2.0) Thanks
Comment 15•17 years ago
|
||
If it's not gone with bug 365016 (fixed in bug 298737) then it seems you are all alone, unless bug 301211 is a bosom buddy. I find no other similar bugs. bug 365016 was reported on build 20051113, yours is 20051025, bug 301211 is 20050712
Reporter | ||
Comment 16•17 years ago
|
||
Well, I do see both these "bugs" although bug 301211 is a lot less frequent. This one however, happens every single time.
Updated•17 years ago
|
QA Contact: front-end
Comment 17•17 years ago
|
||
duping to 217940 if want a last ditch attempt at making it go away (which I doubt will work) remove the news account(s), delete your news directory, and start from scratch.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago → 17 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 18•17 years ago
|
||
I'm sorry, but these bugs are NOT the same, they manifest themselves in completely different ways and have very different causes. Bug 217940 is related to messages being deleted on the server confusing TB, this is related to TB not updating the message list as appropriate. The only thing they have in common seems to be the fact that the group item becomes bold, as with any new item received.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Reporter | ||
Comment 19•17 years ago
|
||
Additionally, the "last ditch resolution" you mentioned is for the other bug. This bug just requires the pressing of F5 and is not related to a corrupt news spool.
Comment 20•16 years ago
|
||
I think I've seen this before, but I can't check this right now.
Comment 21•16 years ago
|
||
Confirmed on Linux with 2.0.0.15pre. By sheer luck.
Assignee: mscott → nobody
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: PC → All
Version: 1.5 → unspecified
Reporter | ||
Comment 22•16 years ago
|
||
Wahoooo, I'm not going mad (well, not relating to this anyway) Thank you for confirming that you've seen ti as well. It still happens every single time for me...
Comment 23•15 years ago
|
||
Unless I am very much mistaken, bug 311774 will fix this bug.
Component: Mail Window Front End → Networking: News
Product: Thunderbird → MailNews Core
QA Contact: front-end → networking.news
Reporter | ||
Comment 25•13 years ago
|
||
I've not noticed it for a while so I think it's fixed. I'm running 3.1.something now
Status: NEW → RESOLVED
Closed: 17 years ago → 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•