|
|
|
Re: Eclipse Luna RC1 shows blank window after start. [message #1450517 is a reply to message #1384651] |
Wed, 22 October 2014 14:22 |
|
Martin R Messages: 1 Registered: October 2014 |
Junior Member |
|
|
I just downloaded the latest version of Eclipse IDE for Java Developers version 4.4.1 Luna x64.
Eclipse IDE for Java Developers
Version: Luna Service Release 1 (4.4.1)
Build id: 20140925-1800
I installed it on Ubuntu 12.04 LTS x64 running on an Intel i5 platform and created a new and empty Workspace directory. When I try running Eclipse using Oracle JDK 1.8.0_25 from the command line with the following options:
eclipse -data ~/Workspace -vm /usr/jdk/jdk1.8.0_25/jre/bin/java
I get the error:
org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized.
Here's an example of what exactly happens from user space, from the command line:
$ /opt/eclipse441-luna/eclipse -data /home/fred/Workspace -vm /usr/jdk/jdk1.8.0_25/jre/bin/java -vmargs -Xmx512m
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized.
Then the eclipse Luna splash screen is shown
During that a new window titled "Internal Error" opens and displays the message: /home/fred/Workspace/.metadata/.lock (Permission denied)
After pressing "Ok" all the windows close again and nothing happens. The command line returns.
After deleting the entire Workspace directory, recreating it and trying it again, the same thing happens. There is no .metadata dir and no .lock file.
Eclipse won't run.
This seems like the problem described above, judging from the log message:
org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized.
Are more people experiencing this problem after a clean install on a similar platform? Was a broken product released? The git repository referenced in bug 436002 is of little help to an end user.
Is there a way to easily fix it myself?
[Updated on: Thu, 23 October 2014 14:11] Report message to a moderator
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04114 seconds