Bug 632666 - [abrt] seamonkey-2.0.6-1.fc13: Process /usr/lib64/seamonkey-2.0.6/seamonkey-bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] seamonkey-2.0.6-1.fc13: Process /usr/lib64/seamonkey-2.0.6/seamonkey-b...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: seamonkey
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c20a9fed9118db1169699c98966...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-10 17:32 UTC by Chris Schanzle
Modified: 2011-05-31 14:18 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-31 14:18:28 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (65.40 KB, text/plain)
2010-09-10 17:32 UTC, Chris Schanzle
no flags Details

Description Chris Schanzle 2010-09-10 17:32:20 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/seamonkey-2.0.6/seamonkey-bin
component: seamonkey
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/seamonkey-2.0.6/seamonkey-bin
kernel: 2.6.34.6-54.fc13.x86_64
package: seamonkey-2.0.6-1.fc13
rating: 4
reason: Process /usr/lib64/seamonkey-2.0.6/seamonkey-bin was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1284139206
uid: 18183

How to reproduce
-----
after a currently-typical seamonkey crash (closing windows/tabs), restarting seamonkey mail and entering password for either of two IMAP accounts causes seamonkey to crash before any messages are displayed.

Tried removing all files in the imap cache directory to with no success.

Going to try to create a new profile.  Ugh.

Comment 1 Chris Schanzle 2010-09-10 17:32:23 UTC
Created an attachment (id=446571)
File: backtrace

Comment 2 Bug Zapper 2011-05-31 13:53:12 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Chris Schanzle 2011-05-31 14:18:28 UTC
closing due to obsolescence/no action.  I don't recall what I did to get it working again.


Note You need to log in before you can comment on or make changes to this bug.