Red Hat Bugzilla – Bug 527733
crash on startup with libmoblin
Last modified: 2010-08-23 15:40:01 EDT
Created attachment 363977 [details]
error log file
Description of problem:
with the moblin desktop installed i can't start eclipse. i get the following error message:
# A fatal error has been detected by the Java Runtime Environment:
# SIGSEGV (0xb) at pc=0x00219f87, pid=2149, tid=3085903552
# JRE version: 6.0-b16
# Java VM: OpenJDK Client VM (14.0-b16 mixed mode linux-x86 )
# Distribution: Custom build (Thu Sep 10 17:09:30 EDT 2009)
# Problematic frame:
# C [libmoblin-netbook-engine.so+0x4f87]
# An error report file with more information is saved as:
# If you would like to submit a bug report, please include
# instructions how to reproduce the bug and visit:
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.install moblin desktop
eclipse IDE :-)
removing moblin-gtk-engine allows eclipse to start.
Could you try with a download from upstream and if it fails with that, too, file a bug at bugs.eclipse.org? The SWT committers there will have a much better idea of where the problem lies.
Grab a .tar.gz from:
for your architecture, extract, and then run the included 'eclipse' binary. If you have java-1.6.0-openjdk-devel installed, it should just work.
sorry, that downloaded eclipse crashes faster (with or without moblin-gtk-engine) with an error about /usr/lib/jvm/java-1.6.0-openjdk-184.108.40.206/jre/bin/../lib/i386/client/libjvm.so (which is from java-1.6.0-openjdk-220.127.116.11-31.b16.fc12.i686) and this in a pop-up window:
JVM terminated. Exit code=-1
Can you attach the hs_err file from that failure? If there wasn't one generated, can you run it with the arguments:
and attach the output here? Thanks.
This may be happening because of selinux denying permission.
Try running eclipse with selinux in permissive mode?
Then start eclipse.
looks like all is okay again now.
for the record - yes, setenforce 0 worked with the downloaded tarball version of eclipse. thanks for that tip.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.
More information and reason for this action is here: