Bug 676089

Summary: [abrt] seamonkey-2.0.11-1.fc13: Process /usr/lib64/seamonkey-2.0.11/seamonkey-bin was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Timur Tabi <timur>
Component: seamonkeyAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED CANTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 13CC: caillon, campbecg, gecko-bugs-nobody, kengert
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:de4864fb6a69f9d364d6fa006c14c3e0a45333c6
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-09 13:52:21 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-02-08 19:32:00 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/seamonkey-2.0.11/seamonkey-bin
component: seamonkey
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/seamonkey-2.0.11/seamonkey-bin
kernel: 2.6.34.7-66.fc13.x86_64
package: seamonkey-2.0.11-1.fc13
rating: 4
reason: Process /usr/lib64/seamonkey-2.0.11/seamonkey-bin was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
How to reproduce: I was just reading a web page that hadn't finished download yet, and it just crashed.
time: 1297193443
uid: 65001749
Comment 1 Timur Tabi 2011-02-08 19:32:02 UTC 
Created attachment 477676 [details]
File: backtrace
Comment 2 Chris Campbell 2011-03-09 13:52:21 UTC 
Thank you for taking the time to make this bug report.

Unfortunately, crash here happened in the moonlight extension, which is on the Forbidden Items (http://fedoraproject.org/wiki/ForbiddenItems#Moonlight) list and as such is not shipped with Fedora or within it's native repositories, so unfortunately we cannot help you with it.

Closing as CANTFIX (because that's our situation)



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers
Comment 3 Timur Tabi 2011-03-09 15:14:45 UTC 
It would be nice if the crash reporter told me the module name where the crash actually occurred.  Searching through the log for the stack trace isn't intuitive at all.  I understand that Moonlight bugs are off-limits, but if people have to scour the bug report in order to determine that, there are going to be lots of Moonlight bugs reported here.