seamonkey-2.0-bin crashed with SIGSEGV

Bug #675055 reported by yamo
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
seamonkey (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: seamonkey

I was using web mail, nntp and a dailymotion vidéo...

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: seamonkey-browser 2.0.10+build1+nobinonly-0ubuntu0.10.10.1
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Sun Nov 14 00:47:32 2010
Disassembly: => 0x3bbcd76b: Cannot access memory at address 0x3bbcd76b
ExecutablePath: /usr/lib/seamonkey-2.0.10/seamonkey-2.0-bin
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4)
ProcCmdline: /usr/lib/seamonkey-2.0.10/seamonkey-2.0-bin
ProcEnviron:
 PATH=(custom, user)
 LANG=fr_FR.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x3bbcd76b: Cannot access memory at address 0x3bbcd76b
 PC (0x3bbcd76b) not located in a known VMA region (needed executable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: seamonkey
Stacktrace:
 #0 0x3bbcd76b in ?? ()
 No symbol table info available.
StacktraceTop: ?? ()
Title: seamonkey-2.0-bin crashed with SIGSEGV
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

Revision history for this message
yamo (stephane-gregoire) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x3bbcd76b in ?? ()
 No symbol table info available.
StacktraceTop: ?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in seamonkey (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libkrb5-3: installed version 1.8.1+dfsg-5ubuntu0.1, latest version: 1.8.1+dfsg-5
libpam0g: installed version 1.1.1-4ubuntu2, latest version: 1.1.1-4ubuntu1
libk5crypto3: installed version 1.8.1+dfsg-5ubuntu0.1, latest version: 1.8.1+dfsg-5
seamonkey-browser: installed version 2.0.10+build1+nobinonly-0ubuntu0.10.10.1, latest version: 2.0.10+build1+nobinonly-0ubuntu0.10.04.1
libpam-modules: installed version 1.1.1-4ubuntu2, latest version: 1.1.1-4ubuntu1
libssl0.9.8: installed version 0.9.8o-1ubuntu4.1, latest version: 0.9.8o-1ubuntu4
libcups2: installed version 1.4.4-6ubuntu2.2, latest version: 1.4.4-6ubuntu2
libc-bin: installed version 2.12.1-0ubuntu8, latest version: 2.12.1-0ubuntu6
tzdata: installed version 2010m-0ubuntu0.10.10, latest version: 2010o-0ubuntu0.10.04
libgssapi-krb5-2: installed version 1.8.1+dfsg-5ubuntu0.1, latest version: 1.8.1+dfsg-5
libnss3-1d: installed version 3.12.8-0ubuntu0.10.10.1, latest version: 3.12.8-0ubuntu0.10.04.1
libxml2: installed version 2.7.7.dfsg-4ubuntu0.1, latest version: 2.7.7.dfsg-4
libfreetype6: installed version 2.4.2-2ubuntu0.1, latest version: 2.4.2-2
libasound2: installed version 1.0.23-1ubuntu2.1, latest version: 1.0.23-1ubuntu2
libkrb5support0: installed version 1.8.1+dfsg-5ubuntu0.1, latest version: 1.8.1+dfsg-5
libc6: installed version 2.12.1-0ubuntu8, latest version: 2.12.1-0ubuntu6

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-i386-retrace
yamo (stephane-gregoire)
Changed in seamonkey (Ubuntu):
status: Invalid → New
Revision history for this message
yamo (stephane-gregoire) wrote :

Hi my maverick is up to date!

for exemple :

libpam0g: installed version 1.1.1-4ubuntu2, latest version: 1.1.1-4ubuntu1

http://packages.ubuntu.com/search?suite=default&section=all&arch=any&lang=fr&searchon=names&keywords=libpam0g say : 1.1.1-4ubuntu2

$ lsb_release -r
Release: 10.10

visibility: private → public
Revision history for this message
dino99 (9d9) wrote :

This version is outdated and no more supported

Changed in seamonkey (Ubuntu):
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.