From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.2-2 i686; en-US; 0.7) Gecko/20010316 BuildID: any This is similar to bug #60968, but more specific. When talkback data is to be sent to the server, the connection is opened and data starts to move. But my connection is a pathetic little 28.8 and the connection times out before the report is complete. The error messages become annoying and I eventually delete the talkback report instead of sending it, which is not good because I really wanted to report the crash. Reproducible: Always Steps to Reproduce: 1. Get mozilla running on a machine with a low bandwidth, high latency connection. 2. Make it crash and set up a talkback report. 3. Send the talkback report. 4. Observe that the data is starting to move upstream but the transmission gets cut off, claiming that the server did not respond. Actual Results: The bug report was not sent and it remained in the queue. It tries to send itself again at regular intervals but always fails with the same error. Expected Results: The transmission should have been sent (even if it takes a while.) As far as I can tell, all that is needed is for the talkback to work is a longer timeout.

I have reset the timeouts on the talkback system: Connect timeout from 5000ms to 10000ms and Receive timeout from 2000ms to 10000ms. j13moh, try to submit again and tell me if that helps. If not we can readjust. cc'ing bclary. Bob, you have had similar issues. I'd be interested to know if this helps you also. ->greer. I know namachi will gladly give me this one.

Using the new 0.9.9 build, I quickly crashed the browser (by accident) and the talkback was able to send the report from linux through my 28.8 (via Win2k NAT) just fine. I am still downloading the windows build and will try it once I get a chance to crash it ;-)

I finally got the Windows Mozilla 0.9.9 to crash and the talkback went through just fine. Apparently the timeout resets from greer@netscape.com did the trick. I would classify this bug as 'fixed' .

j13moh, thanks for the feedback. Marking fixed. We can reopen if you or bclary have trouble in the future.