Bug#663734: eclipse-3.7.2-1 does not start on wheezy

[Felix Natter]

Niels Thykier <niels at thykier.net> writes:

> On 2012-03-13 17:31, Felix Natter wrote:
>> Package: eclipse
>> Version: 3.7.2-1
>> 
>> After failing to build eclipse-3.7.2-1 on wheezy (see other bug report),
>> I simply pulled the packages from unstable. 3.7.1 does not work for me as it
>> freezes on any breakpoint, and thankfully this is fixed in 3.7.2 :-)
>> 
>> I am using wheezy with a 32bit kernel (on a 64bit system):
>> felix at bitburger:~$ uname -a
>> Linux bitburger 3.0.0-1-686-pae #1 SMP Sat Aug 27 16:41:03 UTC 2011 i686 GNU/Linux
>> 
>
> Hi,

hello Niels,

> From your output, it looks you have a 32bit userspace with a 32bit
> kernel.  I guess you meant you had a CPU able to run in 64bit?

Yes, I was referring to a "hardware system".

> Anyhow, usually what matters is that the JVM and eclipse are compiled
> for the same architecture (or "same number of bits" if you will).
>
>> When starting the newly-upgraded eclipse, I get:
>> !SESSION 2012-03-13 16:40:43.292 -----------------------------------------------
>> eclipse.buildId=I20110613-1736
>> java.version=1.6.0_26
>> java.vendor=Sun Microsystems Inc.
>> BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=de_DE
>> Command-line arguments:  -os linux -ws gtk -arch x86
>> 
>> !ENTRY org.eclipse.osgi 4 0 2012-03-13 16:40:57.645
>> !MESSAGE Application error
>> !STACK 1
>> java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons: 
>> 	no swt-gtk-3740 in java.library.path
>> 	no swt-gtk in java.library.path
>> 	Can't load library: /home/felix/.swt/lib/linux/x86/libswt-gtk-3740.so
>> 	Can't load library: /home/felix/.swt/lib/linux/x86/libswt-gtk.so
>                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> That is not a path eclipse (from Debian) should look at.  Have you set
> java.library.path to a non-standard value (or possibly have
> LD_LIBRARY_PATH etc. set)?

Not that I know of :-/

> In the past eclipse has extracted SWT into ~/.eclipse, which has been
> known to cause issues when upgrading eclipse.  Long story short, the
> libraries in ~/.eclipse were used even when they were output date and
> that ultimately lead to crashes.

Yes, I had another problem:
!MESSAGE Unable to create editor ID org.eclipse.jdt.ui.CompilationUnitEditor: No editor descriptor for id org.eclipse.jdt.ui.CompilationUnitEditor
!STACK 1
org.eclipse.ui.PartInitException: No editor descriptor for id org.eclipse.jdt.ui.CompilationUnitEditor
	at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:601)
	at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:465)
	at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595)
	at org.eclipse.ui.internal.EditorAreaHelper.setVisibleEditor(EditorAreaHelper.java:271)

... which was fixed by removing ~/.eclipse.

>
>> 	[...]
>> 
>> These libswt* packages are installed:
>> felix at bitburger:~$ dpkg -l libswt\*
>> [...]
>> I was able to "fix" this by copying /usr/lib/jni/libswt-*3740.so
>> to ~/.swt/lib/linux/x86.
>> 
>> Thanks!
>
> Personally, I would recommend trying to remove/rename ~/.swt and see if
> that fixes it.

No, this does not work. But the workaround is ok for me.

Thanks and Best Regards,
-- 
Felix Natter