Bug 250221
Summary: | eclipse does not start up | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jens Petersen <petersen> | ||||||
Component: | eclipse | Assignee: | Andrew Overholt <overholt> | ||||||
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | high | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | rawhide | CC: | drepper, dwalsh | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2007-10-04 15:56:51 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: | |||||||||
Bug Depends On: | |||||||||
Bug Blocks: | 235703 | ||||||||
Attachments: |
|
Description
Jens Petersen
2007-07-31 03:15:11 UTC
Created attachment 160292 [details]
workspace/.metadata/.log
Can you try changing 'eclipse.product=org.eclipse.sdk.ide' to 'eclipse.product=org.eclipse.platform.ide' in /usr/lib/eclipse/configuration/config.ini and let me know if that fixes the problem? Thanks. Scratch that. I think the problem is with the Manifest files I put in the Lucene jars. I'll update the lucene packages tomorrow and get you to test things then. Thanks, Ben Ok, I just pushed the lucene build: http://koji.fedoraproject.org/koji/taskinfo?taskID=84077 Can you test eclipse with that version of lucene? THanks, Ben It still gave an error. I can try again later with the new eclipse build. I tried eclipse-3.3.0-4.fc8 now and still get an error dialog at startup. It would be nice to have working eclipse in test1 but maybe too late now? Created attachment 160498 [details]
workspace/.metadata/.log
I can't reproduce this problem. Can you try running with a clean workspace and ~/.eclipse directory. Just run: mv ~/.eclipse ~/.eclipse-back and then run eclipse with: eclipse -data workspace-test Let me know how that goes. Ben In addition, could you try this line: for f in `rpm -aq | egrep "eclipse|swt"`; do rpm -qV $f; done and post the output? Thanks, Ben (In reply to comment #8) > Can you try running with a clean workspace and > ~/.eclipse directory. Just run: > mv ~/.eclipse ~/.eclipse-back > and then run eclipse with: > eclipse -data workspace-test That gives me an error dialog again. (In reply to comment #9) > In addition, could you try this line: > for f in `rpm -aq | egrep "eclipse|swt"`; do rpm -qV $f; done No output. I will certainly try again when the latest eclipse packages land in fedora devel after test1. I guess this is related to selinux. If I set "setenforcing permissive", eclipse runs fine for me. Do you have any SELinux failures specifically mentioned in the panel applet thingy or in a log somewhere? Nope, I don't see any. Adding dwalsh to cc. Are you seeing avc messages in /var/log/audid/audit.log or /var/log/messages This is probably a badly written/labeled shared library. Yes, in /var/log/audid/audit.log: type=AVC msg=audit(1187913845.427:80): avc: denied { execmem } for pid=6126 comm="eclipse" scontext=system_u:system_r:unconfined_t:s0 tcontext=system_u:system_r:unconfined_t:s0 tclass=process type=SYSCALL msg=audit(1187913845.427:80): arch=40000003 syscall=192 success=no exit=-13 a0=0 a1=2000 a2=7 a3=22 items=0 ppid=1 pid=6126 auid=500 uid=500 gid=500 euid=500 suid=500 fsuid=500 egid=500 sgid=500 fsgid=500 tty=(none) comm="eclipse" exe="/usr/lib/eclipse/eclipse" subj=system_u:system_r:unconfined_t:s0 key=(null) type=AVC msg=audit(1188177305.231:72): avc: denied { execmem } for pid=3185 comm="eclipse" scontext=system_u:system_r:unconfined_t:s0 tcontext=system_u:system_r:unconfined_t:s0 tclass=process type=SYSCALL msg=audit(1188177305.231:72): arch=40000003 syscall=192 success=no exit=-13 a0=0 a1=2000 a2=7 a3=22 items=0 ppid=1 pid=3185 auid=500 uid=500 gid=500 euid=500 suid=500 fsuid=500 egid=500 sgid=500 fsgid=500 tty=(none) comm="eclipse" exe="/usr/lib/eclipse/eclipse" subj=system_u:system_r:unconfined_t:s0 key=(null) Has eclipse always needed execmem? Is this caused by java? If you execute the following eclipse should work semanage fcontext -a -t java_exec_t /usr/lib/eclipse/eclipse restorecon -v /usr/lib/eclipse/eclipse (In reply to comment #17) > Has eclipse always needed execmem? Is this caused by java? There were changes made to the launcher in Eclipse 3.3.0 so that's probably causing the problem. (In reply to comment #18) > If you execute the following eclipse should work > > semanage fcontext -a -t java_exec_t /usr/lib/eclipse/eclipse > restorecon -v /usr/lib/eclipse/eclipse Is there something that I should do to get this changed on the system. I have to admit to knowing very little about selinux but I'm willing to learn. If you have a URL that I should checkout, just let me know. Thanks, Ben Not sure what you are asking Ben? As far as intro to SELinux danwalsh.livejournal.com is my blog for "SELinux for dummies", If you want to know about execmem/execmod. http://people.redhat.com/~drepper/selinux-mem.html Thanks for the links. I just want to know if I need to do anything to make eclipse work when selinux is turned on. Or will users always need to run these commands?: semanage fcontext -a -t java_exec_t /usr/lib/eclipse/eclipse restorecon -v /usr/lib/eclipse/eclipse Can that be done in eclipse.spec or should it be added to selinux-policy? No I have added labeling of eclipse as a java_exec_t in the latest rawhide policy. So if execmem is really necessary, I will leave the label. Eclipse seems to work in the test3 live CD with selinux enabled. I don't know who changed this to rawhide but right now it's expected that it won't start on a fresh rawhide installation. I'm trying to get Eclipse 3.4 in and should hopefully have a build on at least x86, x86_64, and ppc by tomorrow. |