Bug#683930: eclipse: 3.8.0~rc4-1 exits with log error: Unable to acquire application
Hi, On 11.8.2012 05:18, JS wrote: 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). jack@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) Hmm no wonder you couldn't get the console when Eclipse is unable to load even the console support bundle. Looking at the dependencies of org.eclipse.equinox.console, could you please check that you have installed the latest versions of these packages available in Debian testing? libfelix-gogo-command-java libfelix-gogo-shell-java libservlet3.0-java libtomcat7-java Eclipse is not declaring a dependency on any particular version of these packages so you might have an old, incompatible one. Our list of required packages should be updated in this case. !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) Looks only as a consequence of previous error(s). Regards, Jakub __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#683930: eclipse: 3.8.0~rc4-1 exits with log error: Unable to acquire application
Jakub, I tried your suggestion and got exactly the same error, details below. This isn't surprising since the eclipse 3.8 blob from eclipse.org runs perfectly on my system, so any packages needed for eclipse 3.8 had to be already present. Here are the details: +++--- ii libfelix-gogo-command-java 0.12.0-1 Apache Felix Gogo Command bundle un libfelix-gogo-command-java-doc none (no description available) ii libfelix-gogo-runtime-java 0.10.0-1 Apache Felix Gogo Runtime bundle un libfelix-gogo-runtime-java-doc none (no description available) ii libfelix-gogo-shell-java 0.10.0-1 Apache Felix Gogo Shell bundle un libfelix-gogo-shell-java-doc none (no description available) ii libservlet3.0-java 7.0.28-2 Servlet 3.0 and JSP 2.2 Java API classes ii libtomcat7-java 7.0.28-2 Servlet and JSP engine -- core libraries ii eclipse 3.8.0~rc4-1 Extensible Tool Platform and Java IDE jack@berkeley:~ = eclipse -console -consoleLog -noExit !SESSION 2012-08-11 19:34:09.365 --- 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-11 19:34:09.633 !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-11 19:34:09.639 !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) thanks, --jack From: Jakub Adam jakub.a...@ktknet.cz To: JS jsh...@yahoo.com Cc: 683...@bugs.debian.org 683...@bugs.debian.org Sent: Saturday, August 11, 2012 8:06 AM Subject: Re: eclipse: 3.8.0~rc4-1 exits with log error: Unable to acquire application Hi, On 11.8.2012 05:18, JS wrote: 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). jack@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
Bug#683930: eclipse: 3.8.0~rc4-1 exits with log error: Unable to acquire application
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@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.a...@ktknet.cz To: JS jsh...@yahoo.com Cc: 683...@bugs.debian.org 683...@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
Bug#683930: 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 RESOLVEDcom.jcraft.jsch_0.1.42 4 RESOLVEDjavax.el_2.2.0 5 RESOLVEDjavax.servlet_3.0.0.v201103241327 6 RESOLVEDjavax.servlet.jsp_2.2.0.v201103241327 7 RESOLVEDorg.apache.ant_1.8.3.v20120321-1730 8 RESOLVEDorg.apache.commons.codec_1.4.0 9 RESOLVEDorg.apache.commons.httpclient_3.1.0 10 RESOLVEDorg.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 __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#683930: eclipse: 3.8.0~rc4-1 exits with log error: Unable to acquire application
Jakub, Thanks for the info. It will take me some time to setup the test with the OSGi console as I'll have to rollback my system when it's done, won't get to that before this weekend. However what I cannot do is run without the latest Oracle java: that's the only one thatreally works properly with some important apps I need, like Citrix. The tarball fromeclipse, as well as the packaged 3.7.2-1, work fine with it. thanks,--jack --- On Mon, 8/6/12, Jakub Adam jakub.a...@ktknet.cz wrote: From: Jakub Adam jakub.a...@ktknet.cz Subject: Re: eclipse: 3.8.0~rc4-1 exits with log error: Unable to acquire application To: JS jsh...@yahoo.com Cc: 683...@bugs.debian.org 683...@bugs.debian.org Date: Monday, August 6, 2012, 7:14 AM 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 __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#683930: eclipse: 3.8.0~rc4-1 exits with log error: Unable to acquire application service
Package: eclipse Version: 3.7.2-1 Severity: important Dear Maintainer, After upgrading from eclipse 3.7.2-1 to 3.8.0~rc4-1, eclipse no longer starts. One sees the initial splash screen, followed by a error dialog that the configuration is wrong, although the same config worked with 3.7.2-1. This error had appeared in 3.7.2-1 in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663734 but using the work-around mentioned in that bug does not fix the problem in 3.8.0. [That workaround was to link all /usr/lib/jni/libswt* to ~/.swt/lib/linux/x86] Bug 663734 has been closed. I tried removing my config and restarting but still got the same error. The error log generated says: java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini). I have verified that the downloaded 3.8 tar file from eclipse.org works without problem and with my existing config, so suspect this is a packaging issue. Here are some additional packages that are relevant (I rolled back to 3.7.2-1 to use eclipse after this failure): ii libswt-gtk-3-java3.7.2-1 Standard Widget Toolkit for GTK+ Java library ii libswt-gtk-3-java-gcj3.7.2-1 Standard Widget Toolkit for GTK+ native library ii libswt-gtk-3-jni 3.7.2-1 Standard Widget Toolkit for GTK+ JNI library un libswt-gtk-3.4-java none (no description available) un libswt-gtk-3.4-jni none (no description available) un libswt-gtk-3.5-jni none (no description available) I am using the current Oracle java (as my java alternative) and eclipse 3.7.2 (and 3.8.0 from the eclipse.org blob) work find with it. Here is the complete eclipse log generated: !SESSION 2012-07-29 00:36:34.565 --- 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 -debug !ENTRY org.eclipse.osgi 4 0 2012-07-29 00:36:34.812 !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) -- System Information: Debian Release: wheezy/sid Architecture: i386 (i686) Kernel: Linux 3.1.0-1-686-pae (SMP w/6 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages eclipse depends on: ii eclipse-jdt 3.7.2-1 ii eclipse-pde 3.7.2-1 eclipse recommends no packages. eclipse suggests no packages. Versions of packages eclipse-platform depends on: ii ant1.8.2-4 ii ant-optional 1.8.2-4 ii default-jre [java6-runtime]1:1.6-46 ii eclipse-platform-data 3.7.2-1 ii eclipse-rcp3.7.2-1 ii gcj-4.6-jre [java5-runtime]4.6.2-2 ii gcj-jre [java5-runtime]4:4.6.1-3 ii java-common0.46 ii libc6 2.13-24 ii libcommons-codec-java 1.5-1 ii libcommons-el-java 1.0-7 ii libcommons-httpclient-java 3.1-10 ii libcommons-logging-java1.1.1-9 ii libjasper-java 5.5.33-2 ii libjetty-java 6.1.24-6 ii libjsch-java 0.1.42-2 ii liblucene2-java2.9.4+ds1-4 ii libservlet2.5-java 6.0.35-1 ii openjdk-6-jre [java6-runtime] 6b24-1.11.1-6 ii openjdk-7-jre [java6-runtime] 7~u3-2.1.1~pre1-2 ii perl 5.14.2-12 ii sat4j 2.3.0-3 ii sun-java6-jre [java6-runtime] 6.26-3 Versions of packages eclipse-platform recommends: ii eclipse-pde 3.7.2-1 Versions of packages eclipse-platform suggests: ii eclipse-jdt 3.7.2-1
Bug#683930: eclipse: 3.8.0~rc4-1 exits with log error: Unable to acquire application
Hi, installation of Eclipse into a clean sid system works for me. As you say you got an error even when config is removed, I think it's a different local issue. Here are some tips for further investigation: 1. Try to run Eclipse with OpenJDK 6 to make sure it's not a problem specific to Oracle JRE. ~/.swt/lib/linux/x86 symlinks are not needed with 3.8.0, that was a different issue. 2. If possible, try to launch with a new clean user account, find out if there isn't still any configuration in your $HOME that prevents Eclipse from starting. 3. There might be some modified files in the installation, left by an (accidental) attempt to run Eclipse as root. Try purging the installation (removing libequinox-osgi-java should uninstall also all the eclipse packages). Make sure that /usr/lib/eclipse and /usr/share/eclipse are empty, delete any files still there. Then install everything back again. Regards, Jakub __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#683930: eclipse: 3.8.0~rc4-1 exits with log error: Unable to acquire application
Jakub, 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. 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? A similar issue arose with 3.7.2 in the earlier bug referenced in my email. thanks, --jack From: Jakub Adam jakub.a...@ktknet.cz To: 683...@bugs.debian.org; jsh...@yahoo.com Sent: Sunday, August 5, 2012 7:43 PM Subject: Re: eclipse: 3.8.0~rc4-1 exits with log error: Unable to acquire application Hi, installation of Eclipse into a clean sid system works for me. As you say you got an error even when config is removed, I think it's a different local issue. Here are some tips for further investigation: 1. Try to run Eclipse with OpenJDK 6 to make sure it's not a problem specific to Oracle JRE. ~/.swt/lib/linux/x86 symlinks are not needed with 3.8.0, that was a different issue. 2. If possible, try to launch with a new clean user account, find out if there isn't still any configuration in your $HOME that prevents Eclipse from starting. 3. There might be some modified files in the installation, left by an (accidental) attempt to run Eclipse as root. Try purging the installation (removing libequinox-osgi-java should uninstall also all the eclipse packages). Make sure that /usr/lib/eclipse and /usr/share/eclipse are empty, delete any files still there. Then install everything back again. Regards, Jakub__ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
