181702 - Talkback can't send crash reports

Status: RESOLVED INVALID

(Camino Graveyard :: General, defect)

Description

[Jeff Williams]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20021122 Chimera/0.6+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20021122 Chimera/0.6+

Talkback is consistently unable to send crash reports to Netscape. I get the
same results when it's automatically sending a crash report and when I click
Send All myself.


Reproducible: Always

Steps to Reproduce:
1. Make Chimera crash somehow.
2. Wait for Talkback to open and attempt to send the crash report.
After Chimera crashes, Talkback opens and tries to send a crash report.

Actual Results:  
The status flips between "Connecting," "Sending," and "Processing" several
times; eventually it displays the error message "A network error
occurred/Processing Failed."


Expected Results:  
Send the crash report.


My Mac sits behind a Linksys router, but that's never caused problems for
Mozilla Talkback on my Linux box.

Comment 1

[Simon Fraser [no longer active]]

Was this just a one-off, or is it consistent? If consistent, do you have any
proxy settings set up?

Comment 2

[Jeff Williams]

I'm seeing this consistently, and I'm not using any proxy settings.

Are there any known, reproducible crashers in the December 20 build? If so,
point me at them, and I'll see if I can get Talkback to work with that build.

Comment 3

[Simon Fraser [no longer active]]

Yes: http://bugzilla.mozilla.org/show_bug.cgi?id=163697

Comment 4

[Jeff Williams]

Okay, I tried this with the December 20 build, and Talkback was still unable to
send the crash report.

Let me know how I can help you diagnose this problem.

Comment 5

[Jeff Williams]

It turns out that this was caused by a misconfigured firewall. I had used
BrickHouse (http://personalpages.tds.net/~brian_hill/brickhouse.html) to set up
the firewall; when I uninstalled BrickHouse, the problem went away. Talkback was
the only application affected by this problem.

This bug can be closed as INVALID.