Bug 709497

Summary: [abrt] seamonkey-2.0.14-1.fc13: Process /usr/lib64/seamonkey-2.0.14/seamonkey-bin was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Timur Tabi <timur>
Component: seamonkeyAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 13CC: caillon, gecko-bugs-nobody, kengert
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:0c00c5afbb0296792a358b518d400ff9580755ec
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-27 11:41:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Timur Tabi 2011-05-31 20:12:18 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: I just crashed all by itself.  I didn't even have the window focus.
time: 1306872671
uid: 65001749
Comment 1 Timur Tabi 2011-05-31 20:12:20 UTC 
Created attachment 502097 [details]
File: backtrace
Comment 2 Bug Zapper 2011-06-27 11:41:57 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.