460254 - crash reporter fails to submit report, mysteriously.

Status: RESOLVED DUPLICATE of bug 455101

(Toolkit :: Crash Reporting, defect)

Description

[sbeam]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.0.3) Gecko/2008092416 Firefox/3.0.3
Build Identifier: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.0.3) Gecko/2008092416 Firefox/3.0.3

When Firefox crashes (which right now occurs anytime there is Flash on the page, separate issue) crash reporter comes up OK but on restart says "There was a problem submitting your report". 

~/.mozilla/firefox/Crash Reports/submit.log contains lines that look like:

[Thu 16 Oct 2008 06:27:21 AM EDT] Crash report submission failed:

thats it! 

Also - about:crashes says "No crash reports have been submitted." - there is nothing there either. All the crash reports seem to be remaining "~/.mozilla/Crash Reports/pending"

below is a sample report from the pending/ dir and a wireshark capture of the send attempt, which is nominal as far as I can tell. 

No idea why CR is having problems.


Reproducible: Always

Steps to Reproduce:
1.Have firefox crash
2.fill out crashreporter dialog
3.hit one of the buttons at the bottom
Actual Results:  
crashreporter says "there was a problem..." and report does not seem to be sent, and no one hears my screams

Expected Results:  
report is sent to https://crash-reports.mozilla.com/ and the awesome mozilla team reads it and smashes the bug and all is right with the world

wireshark capture of the report submission attempt:

  0.000000 205.234.175.175 -> 192.168.1.28 TCP http > 52930 [FIN, ACK] Seq=1 Ack=1 Win=14 Len=0 TSV=723215834 TSER=89275127
  0.040073 192.168.1.28 -> 205.234.175.175 TCP 52930 > http [ACK] Seq=1 Ack=2 Win=68 Len=0 TSV=89285169 TSER=723215834
  0.050096 205.234.175.175 -> 192.168.1.28 TCP http > 52929 [FIN, ACK] Seq=1 Ack=1 Win=16 Len=0 TSV=723381742 TSER=89275169
  0.079637 205.234.175.175 -> 192.168.1.28 TCP http > 52932 [FIN, ACK] Seq=1 Ack=1 Win=14 Len=0 TSV=723309845 TSER=89275198
  0.090065 192.168.1.28 -> 205.234.175.175 TCP 52929 > http [ACK] Seq=1 Ack=2 Win=182 Len=0 TSV=89285219 TSER=723381742
  0.119061 192.168.1.28 -> 205.234.175.175 TCP 52932 > http [ACK] Seq=1 Ack=2 Win=69 Len=0 TSV=89285248 TSER=723309845
  0.306477 216.115.104.240 -> 192.168.1.28 TCP http > 47212 [FIN, ACK] Seq=1 Ack=1 Win=27 Len=0 TSV=778853068 TSER=89275438
  0.346042 192.168.1.28 -> 216.115.104.240 TCP 47212 > http [ACK] Seq=1 Ack=2 Win=65 Len=0 TSV=89285475 TSER=778853068
  3.839970 66.235.142.2 -> 192.168.1.28 TCP http > 45269 [RST] Seq=1 Win=4380 Len=0
  4.898143 140.211.166.65 -> 192.168.1.28 TCP http > 44416 [FIN, ACK] Seq=1 Ack=1 Win=14 Len=0 TSV=686290914 TSER=89170595
  4.938864 192.168.1.28 -> 140.211.166.65 TCP 44416 > http [ACK] Seq=1 Ack=2 Win=62 Len=0 TSV=89290068 TSER=686290914
  5.897811 140.211.166.65 -> 192.168.1.28 TCP http > 44417 [FIN, ACK] Seq=1 Ack=1 Win=15 Len=0 TSV=686291164 TSER=89170703
  5.898199 140.211.166.65 -> 192.168.1.28 TCP http > 44419 [FIN, ACK] Seq=1 Ack=1 Win=14 Len=0 TSV=686291164 TSER=89170708
  5.923695 140.211.166.65 -> 192.168.1.28 TCP http > 44418 [FIN, ACK] Seq=1 Ack=1 Win=14 Len=0 TSV=686226019 TSER=89170706
  5.937813 192.168.1.28 -> 140.211.166.65 TCP 44417 > http [ACK] Seq=1 Ack=2 Win=55 Len=0 TSV=89291067 TSER=686291164
  5.938806 192.168.1.28 -> 140.211.166.65 TCP 44419 > http [ACK] Seq=1 Ack=2 Win=60 Len=0 TSV=89291068 TSER=686291164
  5.963805 192.168.1.28 -> 140.211.166.65 TCP 44418 > http [ACK] Seq=1 Ack=2 Win=55 Len=0 TSV=89291093 TSER=686226019

Comment 1

[sbeam]

Attachment: a sample crash report from the pending/ dir, in case it helps

Comment 2

[Marcia Knous [:marcia]]

sbeam: Sounds like you may be hitting Bug 422308.

Comment 3

[sbeam]

But crashreporter does come up, it just doesn't send the report. So this is different.

Comment 4

[Marcia Knous [:marcia]]

Moving this over to the Socorro component since it doesn't belong in Firefox|General.

Comment 5

[(not currently active) Ted Mielczarek]

Duping to bug 455101 unless proven otherwise. You're running a 32-bit build on an x86-64 system, you probably don't have a 32 bit libcurl installed.

Comment 6

[sbeam]

yep 32bit curl solved it. I have to suggest that the error message in submit.log should be better, that would resolve all these bugs and could save someone a couple hours if it mentioned libcurl.so