Red Hat Bugzilla – Bug 811754
Process /usr/lib/jvm/java-1.6.0-openjdk-220.127.116.11.x86_64/jre/bin/java was killed by signal 6 (SIGABRT)
Last modified: 2012-05-09 07:06:06 EDT
Created attachment 576903 [details]
hs_err log file associated with the bug
I get this error when trying to open the newly installed Eclipse Indigo.
I installed Eclipse by downloading the tar.gz and extracting it into /opt
Then I created an executable in /usr/bin and also a launcher in /user/share/applications
Eclipse splash opens where it lets me choose a workspace but then, when i pick one and hit OK, it crashed
the err log file is attached
the problem remains even after upgrading to Java 7 DEV JDK (yum install java-1.7.0-openjdk-devel.x86_64)
Your best bet is to do yum install eclipse . Upstream builds often crash because of incompatibility with newer versions of xulrunner. I see in your bug report that it's g_object_get_qdata call that fails but I cannot reproduce it. Let me know whether eclipse from rpm works fine for you.
Thanks, Alexander, however, the oddity is that this happened during an overhaul reinstall of my Fedora 16 system. I previously had the same version of OS and Eclipse Indigo (albeit if could have been a different build). I had installed it the same way (tar extraction, which is normally how Eclipse is installed, even on Windows). What could have happened that some system update on top of the regular OS install could have broken it.
Alexander, i did as you suggested, installed it from yum (yum install eclipse-jdt), it installed version 3.7.1. Unfortunately, the same error occurred.
I have a feeling the problem is within the kernel, I've tried different versions of both Eclipse as well as Java. Do you see any issues in trying previous versions of the Kernel??
the solution suggested above did not do. can we keep working on it?
I found this bug that is similar but the Linux distro is different:
i forgot to mention this was in KDE
i logged into GNOME -- Eclipse opened no problem
when i went back into KDE, the bug was gone. i can now use Eclipse :)
so the problem is solved. i still would like to know what was wrong.
Closing the bug as we can't find a way to reproduce. Please reopen if/when there are instructions how to reproduce.