firefox-bin crashed with SIGSEGV in __longjmp()

Bug #566800 reported by mrl586
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: firefox

mrl586@ADVENT:~$ lsb_release -rd;apt-cache policy firefox
Description: Ubuntu lucid (development branch)
Release: 10.04
firefox:
  Asennettu: 3.6.3+nobinonly-0ubuntu3
  Ehdokas: 3.6.3+nobinonly-0ubuntu3
  Versiotaulukko:
 *** 3.6.3+nobinonly-0ubuntu3 0
        500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: firefox 3.6.3+nobinonly-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
CrashCounter: 1
Date: Mon Apr 19 19:24:16 2010
ExecutablePath: /usr/lib/firefox-3.6.3/firefox-bin
FirefoxPackages:
 firefox 3.6.3+nobinonly-0ubuntu3
 firefox-gnome-support N/A
 firefox-branding 3.6.3+nobinonly-0ubuntu3
 abroswer N/A
 abrowser-branding N/A
InstallationMedia: Kubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100414)
ProcCmdline: /usr/lib/firefox-3.6.3/firefox-bin
ProcEnviron:
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xa36422 <__kernel_vsyscall+2>: ret
 PC (0x00a36422) ok
 destination "(%esp)" (0xa6cf6b4c) ok
 SP (0xa6cf6b4c) ok
 Reason could not be automatically determined. (Unhandled exception in kernel code?)
Signal: 11
SourcePackage: firefox
StacktraceTop:
 __longjmp () at ../sysdeps/i386/__longjmp.S:68
 ?? ()
Title: firefox-bin crashed with SIGSEGV in __longjmp()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
mrl586 (mrl586) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __longjmp () at ../sysdeps/i386/__longjmp.S:68
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
Revision history for this message
mrl586 (mrl586) wrote :
visibility: private → public
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report didn't yield the required information. Please go ahead and submit a new crash report if it crashed again with the latest available package. Thanks in advance for your cooperation and understanding.

Changed in firefox (Ubuntu):
importance: Undecided → Medium
status: New → Invalid
Revision history for this message
mrl586 (mrl586) wrote :

I think that is some kernel related issue. Previously reported bug (#564316) include similar 'Unhandled exception in kernel code' line.

mrl586 (mrl586)
Changed in firefox (Ubuntu):
status: Invalid → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in firefox (Ubuntu):
status: New → Confirmed
Revision history for this message
Paul White (paulw2u) wrote :

To all those affected,

We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. This bug reported was some time ago and there have been many changes in Ubuntu and Firefox since that time.

Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.

Do you still see a problem related to the one that was reported using currently supported versions of Ubuntu and Firefox?

Please let us know if you do otherwise this bug report will expire in approximately 60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

Changed in firefox (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for firefox (Ubuntu) because there has been no activity for 60 days.]

Changed in firefox (Ubuntu):
status: Incomplete → Expired
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.