Closed holle closed 2 years ago
You're most likely facing https://github.com/eclipse-platform/eclipse.platform.swt/issues/281 . Please make sure you fully update your Suse and tell us the webkitgtk version you have installed.
Hi @akurtakov,
thanks for the quick reply. It looks as if in fact I am running the affected webkitgtk version:
libwebkit2gtk-4_1-0-2.36.5-150400.4.9.1.x86_64
libwebkit2gtk-4_0-37-2.36.5-150400.4.9.1.x86_64
I will attempt to downgrade the rpms manually.
Cheers, Holger
Howto/Tip: This "Hack" worked for me (thanks again to @akurtakov for pointing out the real problem):
Downloaded the "old" rpms (ymmv):
Then unpacked all those RPMs "next" to my eclipse installation folder (mine is /workspace/eclipse-binaries):
cd /workspace/eclipse-binaries
rpm2cpio <RPM> | cpio -id
# rinse and repeat for each rpm
The above created the "normal" file structure usr/lib usr/lib64 usr/share etc... Then I added the .../usr/lib64 path as an ld preload to my startup script:
#!/bin/sh
export GIT_SSH=/usr/bin/ssh
export LD_LIBRARY_PATH=/workspace/eclipse-binaries/usr/lib64
cd /workspace/eclipse-binaries/eclipse-jee-2022-06-R
./eclipse $* &
And now everything seems to work properly :-)
Hope this helps others until we have a fixed version available. Cheers, Holger
Make sure you report this to suse devs.
The openSUSE Team is already aware and working on a solution: https://bugzilla.opensuse.org/show_bug.cgi?id=1202169
Eclipse 2022-03 (updated to 2022-06) as well as a fresh 2022-06 install with an empty working directory crashes under Linux openSUSE 15.4 (KDE Plasma/X11). No (meaningful) logmessages are being generated. Happens with the default JRE/Xmx and adopted: JDK11 (Oracle) 8GB JDK1.8 (Oracle) 6GB
The (a) crash can be directly forced by simply accessing the Eclipse Marketplace and waiting a moment. It is also impossible to install any extension from the Marketplace using Drag and Drop (Install Button).
It also crashes when using the Java editor. Suddenly the editor becomes unresponsive, followed by a crash.
The crash does not open a "crashed app" window, it simply disappears.
setting these variables:
or not does not seem to have any (apart from the file open dialog L&F) effects.
Attempting to use the SpringToolSuite4.15.3 shows the same behavior regarding the Marketplace access. No further tests have been made with STS.