firefox-bin crashed with SIGSEGV in raise()

Bug #123643 reported by Juan Pablo Salazar Bertín
12
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Invalid
Medium
Mozilla Bugs

Bug Description

Binary package hint: firefox

I switched to a VT, then switched back to my gnome desktop. Instead of my desktop, there was only a gdm screen.

ProblemType: Crash
Architecture: i386
Date: Mon Jul 2 19:05:07 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/firefox/firefox-bin
NonfreeKernelModules: cdrom
Package: firefox 2.0.0.4+2-0ubuntu2
PackageArchitecture: i386
ProcCmdline: /usr/lib/firefox/firefox-bin
ProcCwd: /home/snifer
ProcEnviron:
 PATH=/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
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 raise () from /lib/tls/i686/cmov/libpthread.so.0
Title: firefox-bin crashed with SIGSEGV in raise()
Uname: Linux snifer-laptop 2.6.22-7-generic #1 SMP Mon Jun 25 17:33:14 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
Juan Pablo Salazar Bertín (snifer) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
John Vivirito (gnomefreak) wrote :

Is this always reproducible? Was there other crash files in /var/crash after you found only gdm? Are you running compiz/beryl if so can you reproduce without it enabled at log in

Changed in firefox:
assignee: nobody → mozilla-bugs
status: New → Incomplete
Changed in firefox:
importance: Undecided → Medium
Revision history for this message
Juan Pablo Salazar Bertín (snifer) wrote :

I can't reproduce this bug. I was using metacity.

Changed in firefox:
status: Incomplete → New
Revision history for this message
Hilario J. Montoliu (hjmf) (hmontoliu) wrote :

Thank you for the bug report however this report lacks information we need to investigate it further. Of course this is not your fault, but the coredump attached to your report doesn't provide useful information for us. For this reason, we are now going to close the bug report - please feel free to reopen when you have more information at hand.

And please don't doubt to report any other crashes/issues you might have in the future.

Further information can be found at [1].

[1] https://wiki.ubuntu.com/MozillaTeam/Bugs

Changed in firefox:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.