firefox crashed with SIGSEGV in __kernel_vsyscall()

Bug #204726 reported by Thomas LAROCHE
4
Affects Status Importance Assigned to Milestone
firefox-3.0 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: firefox-3.0

Firefox 3 Béta 4

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Fri Mar 21 18:02:45 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/firefox-3.0b4/firefox
NonfreeKernelModules: fglrx
Package: firefox-3.0 3.0~b4+nobinonly-0ubuntu1
PackageArchitecture: i386
ProcCmdline: /usr/lib/firefox-3.0b4/firefox
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: firefox-3.0
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libpthread.so.0
 ?? () from /usr/lib/xulrunner-1.9b4/libxul.so
 ?? ()
 ?? ()
Title: firefox crashed with SIGSEGV in __kernel_vsyscall()
Uname: Linux 2.6.24-12-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

Tags: apport-crash
Revision history for this message
Thomas LAROCHE (mikaye) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:IA__gtk_widget_queue_draw_area (widget=0xa166810, x=0, y=0, width=164,
IA__gtk_widget_queue_draw (widget=0xa166810)
gtk_window_on_composited_changed (screen=0x8080100, window=0xa166810)
IA__g_cclosure_marshal_VOID__VOID (closure=0x9d7e4c8, return_value=0x0,
IA__g_closure_invoke (closure=0x9d7e4c8, return_value=0x0, n_param_values=1,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in firefox-3.0:
importance: Undecided → Medium
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your report, may you tell us a few easy steps in order to trigger the crash? Is this reproducible with another new user profile created on your system? thanks.

Changed in firefox-3.0:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

Changed in firefox-3.0:
status: Incomplete → 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.