firefox-bin crashed with SIGSEGV in __kernel_vsyscall()

Bug #157372 reported by mabovo
6
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Invalid
Undecided
Mozilla Bugs

Bug Description

Binary package hint: firefox

Firefox 2.0.0.8 is plenty of bugs and together with Compiz they compound a perfect couple.
Every time I have to press the reset buttom in order to have Gutsy operating back.
I thought it was the Compiz the guilty but had disable it and so on the problem persist.
The connection with internet still suffers a lot with the browser communication flowing in small packages stumbling over the wired eth0.
If I upgrade Gutsy from the repo directory I can get rates up to 250 kbs meaning that it's not a network problem.

ProblemType: Crash
Architecture: i386
Date: Fri Oct 26 06:17:06 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/firefox/firefox-bin
NonfreeKernelModules: cdrom
Package: firefox 2.0.0.8+2nobinonly-0ubuntu1
PackageArchitecture: i386
ProcCmdline: /usr/lib/firefox/firefox-bin
ProcCwd: /home/marcos
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: firefox
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libpthread.so.0
 ?? ()
 ?? ()
 ?? ()
Title: firefox-bin crashed with SIGSEGV in __kernel_vsyscall()
Uname: Linux autoxtreme 2.6.22-14-386 #1 Sun Oct 14 22:36:54 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev powerdev scanner video

Revision history for this message
mabovo (mabovo) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:__kernel_vsyscall ()
raise () from /lib/tls/i686/cmov/libpthread.so.0
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Revision history for this message
Alexander Sack (asac) wrote :

Thanks for submitting your crash report.

Unfortunately it doesn't contain the needed information to properly process this bug. This can happen and is not due to any wrong doing
of the bug reporter. Please submit any crashes you see in future. Maybe we will have more luck with those.

Thanks for your contribution,
 - Alexander

Changed in firefox:
assignee: nobody → mozilla-bugs
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.