Bug 581379

Summary: [abrt] crash in eclipse-platform-1:3.5.1-22.fc12: Process /usr/lib/eclipse/eclipse was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: speamr18
Component: eclipseAssignee: Andrew Overholt <overholt>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: akurtako, oliver, overholt, zx
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:ea2a4e1cbc648c91127e04dbbd9f38390412ddb4
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-09-01 12:40:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description speamr18 2010-04-12 03:28:48 UTC 
abrt 1.0.8 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/lib/eclipse/eclipse
component: eclipse
executable: /usr/lib/eclipse/eclipse
kernel: 2.6.32.10-90.netbook.fc12.i686
package: eclipse-platform-1:3.5.1-22.fc12
rating: 3
reason: Process /usr/lib/eclipse/eclipse was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
Comment 1 speamr18 2010-04-12 03:28:50 UTC 
Created attachment 405882 [details]
File: backtrace
Comment 2 Andrew Overholt 2010-04-12 20:05:59 UTC 
When the crash happened, was GNOME Accessibility enabled?
Comment 3 speamr18 2010-04-21 00:08:22 UTC 
(In reply to comment #2)
> When the crash happened, was GNOME Accessibility enabled?    

I don't think so. I don't use Accessibility so unless it was turned on by default it was not on.
Comment 4 Chris Aniszczyk 2010-04-23 14:46:29 UTC 
Can you be a bit more specific on what you were doing when Eclipse crashed?
Comment 5 Chris Aniszczyk 2010-04-23 14:46:43 UTC 
And what may have been installed?