Saulo Moraes changed bug 1202444
What Removed Added
CC   saulo.a.moraes@gmail.com
Priority P5 - None P4 - Low

Comment # 2 on bug 1202444 from Saulo Moraes
I can confirm it still a problem, the eclipse-swt is not working properly as it
is missing deps. SWT depends from 'libgthread-2.0.so' that is not been
installed with eclipse-swt, and it is causing the problem, unfortunately the
error output is not clear.

Currently eclipse-swt is useless without correct deps, and most of people are
probably installing 'libgthread' as a dep from other packages...

Reference for the fix:
https://forums.opensuse.org/t/latest-eclipse-crashing-in-opensuse-tumbleweed/175396/21

LOGS:
!SESSION 2024-07-31 20:37:46.460
-----------------------------------------------
eclipse.buildId=4.32.0.20240606-1231
java.version=21.0.3
java.vendor=Eclipse Adoptium
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments:  -product org.eclipse.epp.package.java.product
Command-line arguments:  -os linux -ws gtk -arch x86_64 -product
org.eclipse.epp.package.java.product

!ENTRY ch.qos.logback.classic 1 0 2024-07-31 20:37:49.706
!MESSAGE Activated before the state location was initialized. Retry after the
state location is initialized.

!ENTRY org.eclipse.osgi 4 0 2024-07-31 20:37:50.162
!MESSAGE Application error
!STACK 1
java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons: 
        no swt-pi4-gtk-4965r11 in java.library.path:
/usr/java/packages/lib:/usr/lib64:/lib64:/lib:/usr/lib
        no swt-pi4-gtk in java.library.path:
/usr/java/packages/lib:/usr/lib64:/lib64:/lib:/usr/lib
        no swt-pi4 in java.library.path:
/usr/java/packages/lib:/usr/lib64:/lib64:/lib:/usr/lib
        Can't load library:
/home/saulo/.swt/lib/linux/x86_64/libswt-pi4-gtk-4965r11.so
        Can't load library: /home/saulo/.swt/lib/linux/x86_64/libswt-pi4-gtk.so
        Can't load library: /home/saulo/.swt/lib/linux/x86_64/libswt-pi4.so

        at org.eclipse.swt.internal.Library.loadLibrary(Library.java:345)
        at org.eclipse.swt.internal.Library.loadLibrary(Library.java:254)
        at org.eclipse.swt.internal.gtk.OS.<clinit>(OS.java:97)
        at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:209)
        at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:155)
        at org.eclipse.swt.widgets.Display.<clinit>(Display.java:170)
        at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:721)
        at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:185)
        at
org.eclipse.ui.internal.ide.application.IDEApplication.createDisplay(IDEApplication.java:182)
        at
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125)
        at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:208)
        at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:143)
        at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:109)
        at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:439)
        at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:271)
        at
java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
        at java.base/java.lang.reflect.Method.invoke(Method.java:580)
        at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:668)
        at org.eclipse.equinox.launcher.Main.basicRun(Main.java:605)
        at org.eclipse.equinox.launcher.Main.run(Main.java:1481)
        at org.eclipse.equinox.launcher.Main.main(Main.java:1454)


You are receiving this mail because: