Bug#683930: eclipse: 3.8.0~rc4-1 exits with log error: Unable to acquire application

Sat Aug 11 03:18:27 UTC 2012

Jakub,

I retried your suggestion but never got the console to look for the output you suggested. Below is all I saw

(also tried adding the -clean option, with the same result).

Oracle/Sun java is needed for some applications I use as unfortunately they don't work well with open-jdk-7,

so I will have to live with eclipse-3.7.2.

thanks,

--jack

jack at berkeley:~ => eclipse -console -consoleLog -noExit
!SESSION 2012-08-10 23:05:56.732 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.7.0_05
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments:  -os linux -ws gtk -arch x86 -console -consoleLog

!ENTRY org.eclipse.osgi 4 0 2012-08-10 23:05:56.964
!MESSAGE Could not find bundle: org.eclipse.equinox.console
!STACK 0
org.osgi.framework.BundleException: Could not find bundle: org.eclipse.equinox.console
at org.eclipse.osgi.framework.internal.core.ConsoleManager.checkForConsoleBundle(ConsoleManager.java:211)
at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:297)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
at org.eclipse.equinox.launcher.Main.run(Main.java:1438)

!ENTRY org.eclipse.osgi 4 0 2012-08-10 23:05:56.972
!MESSAGE Application error
!STACK 1
java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini).
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:74)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
at org.eclipse.equinox.launcher.Main.run(Main.java:1438)

________________________________
 From: Jakub Adam <jakub.adam at ktknet.cz>
To: JS <jshaio at yahoo.com> 
Cc: "683930 at bugs.debian.org" <683930 at bugs.debian.org> 
Sent: Monday, August 6, 2012 7:14 AM
Subject: Re: eclipse: 3.8.0~rc4-1 exits with log error: Unable to acquire application

Hi,

On 6.8.2012 04:41, JS wrote:
> I ran the eclipse 3.8.0 gotten straight from eclipse.org, without any change to my existing configuration or
> selection of java alternatives (of Oracle jre) and it ran perfectly fine. Further, I did not run eclipse as root.

Tarball from Eclipse.org is quite different in some aspects, it can write to any file in its installation
and because it carries all required libraries inside, it will work almost anywhere independent on the system.
It won't help much in investigating of this issue.

But you said Eclipse won't start even without your ~/.eclipse, so the problem is not there but somewhere else.

One test that can say us something more is running Eclipse with enabled OSGi console. Execute from the shell:

  eclipse -console -consoleLog -noExit

After a while you should be presented with the console, it should keep running even after Eclipse terminates
with error. Type 'ss' in the shell. Then you will see a list of loaded plugins like this:

id      State       Bundle
0       ACTIVE      org.eclipse.osgi_3.8.0.dist
1       ACTIVE      org.eclipse.equinox.simpleconfigurator_1.0.300.dist
2       ACTIVE      com.ibm.icu_4.4.2.v20110823
3       RESOLVED    com.jcraft.jsch_0.1.42
4       RESOLVED    javax.el_2.2.0
5       RESOLVED    javax.servlet_3.0.0.v201103241327
6       RESOLVED    javax.servlet.jsp_2.2.0.v201103241327
7       RESOLVED    org.apache.ant_1.8.3.v20120321-1730
8       RESOLVED    org.apache.commons.codec_1.4.0
9       RESOLVED    org.apache.commons.httpclient_3.1.0
10      RESOLVED    org.apache.commons.logging_1.0.4.v20080605-1930
...

Look if there are any bundles in INSTALLED State. Those are the ones that had some problem in initialization.
Run 'diag <bundle numeric id>' to see more information on that plugin, like any unresolved dependencies.

You can read some more information about OSGi console in this article [1].

> If the same upstream source works fine on my system but the debian package does not, isn't this more
> likely to be a packaging issue?

Maybe, I can't say for sure right now, as I don't have enough information yet. Post here an output from your
OSGi console session, perhaps try to answer some questions from my previous mail. Can you run distribution
Eclipse with OpenJDK? Is a different user (with clean $HOME) able to run it?

> A similar issue arose with 3.7.2 in the earlier bug referenced in my email.

This was a problem with Oracle Java and its hardcoded search path for JNI libraries that doesn't include
/usr/lib/jni, where JNI libraries are placed according to Debian guidelines. Eventually we decided to put a
workaround patch into SWT package because many people are still using Oracle Java [2].

Nevertheless, with SWT 3.8.0 this should be fixed and there is no mention of ~/.swt/lib/linux/x86 in your error
logs, so your problem seems to have a different cause.

Regards,

Jakub

[1] http://www.eclipsezone.com/eclipse/forums/t99010.html
[2] http://anonscm.debian.org/gitweb/?p=pkg-java/swt-gtk.git;a=commit;h=c4fe7237fef825b2643993a7cf5e4b8cc1dc0285
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/attachments/20120810/c5a72065/attachment-0001.html>