Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 236407 - dev-util/eclipse-sdk-3.4 won't run, complaining about config file
Summary: dev-util/eclipse-sdk-3.4 won't run, complaining about config file
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: AMD64 Linux
: High critical (vote)
Assignee: Java team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-02 01:05 UTC by Adam Nielsen
Modified: 2008-09-09 22:12 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Nielsen 2008-09-02 01:05:33 UTC
I've upgraded to Eclipse 3.4 through Portage, but I have been unable to get it working.  It keeps crashing complaining that it can't create a configuration file, but I've got no idea why - if I remove the whole ~/.eclipse directory it gets recreated, so it's definitely not a permissions issue.

I thought it may be because I was running Java 1.6 (the latest in Portage) but I tried rebuilding Eclipse with USE="java6" but it didn't make a difference.  Eclipse 3.3 still works.  Here are the first few relevant lines from the log file:

!SESSION 2008-09-02 10:54:48.398 -----------------------------------------------
eclipse.buildId=I20080617-2000
java.version=1.6.0_07
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_AU
Framework arguments:  
Command-line arguments:  -os linux -ws gtk -arch x86_64 

!ENTRY org.eclipse.update.configurator 4 0 2008-09-02 10:54:48.928
!MESSAGE 
!STACK 0
org.osgi.framework.BundleException: Exception in org.eclipse.update.internal.configurator.ConfigurationActivator.start() of bundle org.eclipse.update.configurator.
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:1028)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:984)
        at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346)
        at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:355)
        at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1074)
        at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:616)
        at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:508)
        at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:299)
        at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:489)
        at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:211)
        at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:321)
Caused by: org.eclipse.core.runtime.CoreException: Cannot create configuration in file:/home/adam/.eclipse/org.eclipse.platform_3.4.0_272132067/configuration/
        at org.eclipse.update.internal.configurator.Utils.newCoreException(Utils.java:96)
        at org.eclipse.update.internal.configurator.ConfigurationActivator.initialize(ConfigurationActivator.java:113)
        at org.eclipse.update.internal.configurator.ConfigurationActivator.start(ConfigurationActivator.java:69)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:1009)
        at java.security.AccessController.doPrivileged(Native Method)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:1003)
        ... 10 more
Root exception:
org.eclipse.core.runtime.CoreException: Cannot create configuration in file:/home/adam/.eclipse/org.eclipse.platform_3.4.0_272132067/configuration/
        at org.eclipse.update.internal.configurator.Utils.newCoreException(Utils.java:96)
        at org.eclipse.update.internal.configurator.ConfigurationActivator.initialize(ConfigurationActivator.java:113)
        at org.eclipse.update.internal.configurator.ConfigurationActivator.start(ConfigurationActivator.java:69)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:1009)
        at java.security.AccessController.doPrivileged(Native Method)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:1003)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:984)
        at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346)
        at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:355)
        at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1074)
        at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:616)
        at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:508)
        at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:299)
        at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:489)
        at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:211)
        at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:321)

!ENTRY org.eclipse.core.runtime 4 0 2008-09-02 10:54:48.931
!MESSAGE 
!STACK 0
org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Missing Constraint: Require-Bundle: org.eclipse.core.jobs; bundle-version="[3.2.0,4.0.0)"
        at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:305)
...
Comment 1 Hanno Zysik (geki) 2008-09-09 10:26:14 UTC
I had this issue at some point. But not anymore, though.
Sync portage tree and re-emerge java dependent packages of eclipse-sdk.
Then check again, please.

Maybe this was some osgi/manifest issue of a java package.
Comment 2 Adam Nielsen 2008-09-09 22:10:12 UTC
Oh you're right - I re-emerged dev-java/swt and the problem went away!  Thanks for the solution!
Comment 3 Adam Nielsen 2008-09-09 22:11:10 UTC
Oh you're right - I re-emerged dev-java/swt and the problem went away!  Thanks for the solution!
Comment 4 Adam Nielsen 2008-09-09 22:12:17 UTC
(Apologies for the double post - I tried to set it to INVALID but the box jumped to UPSTREAM before I noticed...)