Closed Bug 598028 Opened 14 years ago Closed 13 years ago

seamonkey mail/news sometimes sees article as 'empty', never tries to retrieve it

Categories

(SeaMonkey :: MailNews: Backend, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: last_available_id, Unassigned)

Details

(Whiteboard: [SmBugEvent])

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.10) Gecko/20100915 Ubuntu/10.04 (CK-IBM) (CK-IBM) Firefox/3.6.10
Build Identifier:  Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.13) Gecko/20100915 Lightning/1.0b1 SeaMonkey/2.0.8

This is really an annoying bug.  For some messages - including replies to me, not just top-level news articles/posts - seamonkey does not seem to go out to the server to get the article. It cannot be made to retrieve the article when this happens.  Also, when this happens, there are no message headers, and you canNOT reply to the group - even if you right-click and say 'reply to group', the address in the composer is the person's email address!  Maybe that will help you isolate this......or maybe not. 

It happens once or twice each and every session (session being up to 12 hour workday). 

Please let me know if/how I can help debug.  Otherwise I've got to stop using seamonkey - and maybe go back to TB3 (gaaaack).

Reproducible: Sometimes

Steps to Reproduce:
1. click around in forum list for a news server.  I have over 100 groups on a server, for example.  As long as there are unread articles in a forum, you have a chance of getting an empty window.
Actual Results:  
You get an empty message window, and the headers shown are for the last successfully-retrieved message.

Expected Results:  
display the message

I have pipelining turned on - http options.
Please try:
1. totally turning off http pipelining.
2. Starting SeaMonkey in seamonkey safe mode.
No reply in eight months. Closing as INCOMPLETE.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [SmBugEvent]
You need to log in before you can comment on or make changes to this bug.