Bug 709822 - [abrt] seamonkey-2.0.14-1.fc13: Process /usr/lib64/seamonkey-2.0.14/seamonkey-bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] seamonkey-2.0.14-1.fc13: Process /usr/lib64/seamonkey-2.0.14/seamonkey...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: seamonkey
Version: 13
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:20f6f00a0779c0c1c59e889e7fe...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-01 18:05 UTC by Timur Tabi
Modified: 2011-06-27 11:41 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-27 11:41:37 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (90.44 KB, text/plain)
2011-06-01 18:05 UTC, Timur Tabi 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Timur Tabi 2011-06-01 18:05:41 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/seamonkey-2.0.14/seamonkey-bin
component: seamonkey
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/seamonkey-2.0.14/seamonkey-bin
kernel: 2.6.34.8-68.fc13.x86_64
package: seamonkey-2.0.14-1.fc13
rating: 4
reason: Process /usr/lib64/seamonkey-2.0.14/seamonkey-bin was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
How to reproduce: Just cliked on an email in the message index pane.  
time: 1306951333
uid: 65001749
Comment 1 Timur Tabi 2011-06-01 18:05:44 UTC 
Created attachment 502338 [details]
File: backtrace
Comment 2 Bug Zapper 2011-06-27 11:41:37 UTC 
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.
Note You need to log in before you can comment on or make changes to this bug.