regchrome crashed with SIGSEGV

Bug #437595 reported by Hans B on 2009-09-27
328
This bug affects 77 people
Affects Status Importance Assigned to Milestone
seamonkey (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: seamonkey

I used Ubuntu Software Store to install Seamonkey.
During the instalation Apport wanted me to report a bug.
Here it is.
The installation seems to be ok. I tried to work with the programm and had no problems.

ProblemType: Crash
Architecture: amd64
Date: Sun Sep 27 13:00:25 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/seamonkey/regchrome
NonfreeKernelModules: nvidia
Package: seamonkey-browser 1.1.17+nobinonly-0ubuntu1 [modified: usr/share/seamonkey/chrome/installed-chrome.txt]
ProcCmdline: /usr/lib/seamonkey/regchrome
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF8
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SegvAnalysis:
 Segfault happened at: 0x7fbc285b4fba: repnz scas %es:(%rdi),%al
 PC (0x7fbc285b4fba) ok
 source "%es:(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%al" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: seamonkey
StacktraceTop:
 ?? () from /usr/lib/seamonkey/libxpcom_core.so
 ?? () from /usr/lib/seamonkey/libxpcom_core.so
 ?? () from /usr/lib/seamonkey/libxpcom_core.so
 ?? () from /usr/lib/seamonkey/libxpcom_core.so
 ?? () from /usr/lib/seamonkey/libxpcom_core.so
Title: regchrome crashed with SIGSEGV
Uname: Linux 2.6.31-11-generic x86_64
UserGroups:

Hans B (chonz) wrote :
visibility: private → public

StacktraceTop:?? () from /usr/lib/seamonkey/libxpcom_core.so
?? () from /usr/lib/seamonkey/libxpcom_core.so
?? () from /usr/lib/seamonkey/libxpcom_core.so
?? () from /usr/lib/seamonkey/libxpcom_core.so
?? () from /usr/lib/seamonkey/libxpcom_core.so

tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
IKT (ikt) wrote :

I was also affected by this bug, after updating to the latest packages the bug no longer exists, will change to fix released but feel free to change if it's still affecting others.

Changed in seamonkey (Ubuntu):
status: New → Confirmed
status: Confirmed → Fix Released
Changed in seamonkey (Ubuntu):
status: Fix Released → Confirmed
IKT (ikt) wrote :

Running Lucid Alpha 3, still bugged

Marin Nedea (marin-n) wrote :

still bugged. ubuntu 10.04 x86

Martin Erik Werner (arand) wrote :

Happened both during install and removal of seamonkey (+seamonkey-chatzilla)

jeffpiatt (jeffpiatt) wrote :

Happened to me too after install from software center in 10.04 beta 2

dino99 (9d9) wrote :

This version is outdated and no more supported

Changed in seamonkey (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers