firefox crashed with SIGSEGV in getenv()

[Neelavar]

Binary package hint: firefox-3.0

I'm using Firefox 3.0 with Ubuntu 8.10.

Was filing a bug report through apport crash report and prompted into launchpad.net webpage in firefox. I was expecting to complete the form to file the bug, instead another apport prompt appeared before me, prompting me to file bug report on firefox 3.0.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/firefox-3.0.3/firefox
Package: firefox-3.0 3.0.3+nobinonly-0ubuntu2
ProcAttrCurrent: unconfined
ProcCmdline: /usr/lib/firefox-3.0.3/firefox https://bugs.launchpad.net/ubuntu/+source/evolution/+filebug/52ZMfLxmyavdNoTo1v2FqVZ9lTT?field.title=evolution+crashed+with+SIGSEGV+in+g_signal_emit_valist%28%29
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: firefox-3.0
StacktraceTop:
 getenv () from /lib/libc.so.6
 ?? () from /usr/lib/gtk-2.0/modules/libatk-bridge.so
 exit () from /lib/libc.so.6
 __libc_start_main () from /lib/libc.so.6
 ?? ()
Title: firefox crashed with SIGSEGV in getenv()
Uname: Linux 2.6.27-7-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

[Apport retracing service (apport)]

StacktraceTop:getenv () from /lib/libc.so.6
spi_atk_bridge_exit_func () at bridge.c:643
exit () from /lib/libc.so.6
__libc_start_main () from /lib/libc.so.6
?? ()

[Brett Alton (brett-alton-deactivatedaccount)]

This happened to me when submitting an apport bug report. Firefox didn't actually crash though... weird.

[goto (gotolaunchpad)]

I surfed in the internet with firefox and clicked on a link in pidgin. Apport popped up and said firefox had crashed, but firefox is still running as it should.

I don't know if the files transferred by Apport appear here, but there was a
ProcCmdline: /usr/lib/firefox-3.0 [link to a site]
somewhere. Thanks!

[goto (gotolaunchpad)]

This particular bug has already been reported and is a duplicate of bug 278095, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.