Ubuntu
firefox-3.0 package

firefox crashed with SIGSEGV

Bug #214104 reported by Guillaume on 2008-04-08

This bug report is a duplicate of: Bug #213948: firefox crashed with SIGSEGV with flash plugin. Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	firefox-3.0 (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: firefox-3.0

Crash when watching a .flv

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue Apr 8 20:25:02 2008
Disassembly: 0xb7fcc410:
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/firefox-3.0b5/firefox
Package: firefox-3.0 3.0~b5+nobinonly-0ubuntu1
PackageArchitecture: i386
ProcCmdline: /usr/lib/firefox-3.0b5/firefox
ProcEnviron:
PATH=/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
Stacktrace: #0 0xb7fcc410 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: firefox crashed with SIGSEGV
Uname: Linux 2.6.24-15-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags:

Revision history for this message

Guillaume (bou-gui) wrote on 2008-04-08:

Dependencies.txt Edit (2.6 KiB, text/plain; charset="utf-8")
ExtensionSummary.txt Edit (937 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (31.0 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (678 bytes, text/plain; charset="utf-8")
Registers.txt Edit (459 bytes, text/plain; charset="utf-8")
pluginreg.dat.txt Edit (4.6 KiB, text/plain; charset="utf-8")
profiles.ini.txt Edit (160 bytes, text/plain; charset="utf-8")

Revision history for this message

Carlos Hellin (carloshellin) wrote on 2008-04-08:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 213948, 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.