Bug 682747 - [abrt] seamonkey-2.0.10-1.fc12: Process /usr/lib/seamonkey-2.0.10/seamonkey-bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] seamonkey-2.0.10-1.fc12: Process /usr/lib/seamonkey-2.0.10/seamonkey-b...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: seamonkey
Version: 12
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5341940667f5572a2bc0c0702c7...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-07 13:18 UTC by mbreitfe
Modified: 2011-03-26 13:10 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-26 13:10:52 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (59.42 KB, text/plain)
2011-03-07 13:18 UTC, mbreitfe 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description mbreitfe 2011-03-07 13:18:26 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: /usr/lib/seamonkey-2.0.10/seamonkey-bin
component: seamonkey
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib/seamonkey-2.0.10/seamonkey-bin
kernel: 2.6.32.26-175.fc12.i686.PAE
package: seamonkey-2.0.10-1.fc12
rating: 4
reason: Process /usr/lib/seamonkey-2.0.10/seamonkey-bin was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
time: 1299503259
uid: 501
Comment 1 mbreitfe 2011-03-07 13:18:33 UTC 
Created attachment 482676 [details]
File: backtrace
Comment 2 Johan Kok 2011-03-26 13:10:52 UTC 
Thank you for your bug report.

We are sorry, but the Fedora Project is no longer releasing bug fixes or any other updates for this version of Fedora. This bug will be set to CLOSED:WONTFIX to reflect this, but please reopen it if the problem persists after upgrading to the latest version of Fedora, which is available from:

http://fedoraproject.org/get-fedora
Note You need to log in before you can comment on or make changes to this bug.