abrt 1.0.1 detected a crash. Attached file: backtrace cmdline: /usr/lib/eclipse/eclipse component: eclipse executable: /usr/lib/eclipse/eclipse kernel: 2.6.31.6-166.fc12.i686.PAE package: eclipse-platform-1:3.5.1-20.fc12 rating: 3 reason: Process was terminated by signal 6 (Aborted)
Created attachment 378379 [details] File: backtrace
I think the crash is related to old/invalid pydev settings for a google app engine project. I was about to make some changes to project properties. (I had some problems with abrt, so this report might be incomplete somehow)
Do you have GNOME accessibility enabled? If so, it might be a dupe of bug #522187.
I had been playing with orca and trying to make it work - but couldn't. I thought it was completely disabled, but "Enable assistive technologies" was checked. (I unchecked it and X hang completely a moment later (caps lock and ctrl-alt-f2 did however work). I assume that that isn't related, but I just wanted to mention it.)
Well ... I have filed https://fedorahosted.org/abrt/ticket/113 for a crash which abrt couldn't file to Fedora bugzilla. That crash is easily reproduced with assistive technologies enabled. I have however not been able to reproduce _this_ crash. But I guess you are right; it was caused by assistive technologies. Marking as duplicate. *** This bug has been marked as a duplicate of bug 522187 ***