Arch Linux User Repository

STM32CubeIDE is now run by executing stm32cubeide_wayland official script. If you have issues related to run environment, try to edit /usr/share/applications/stm32cubeide.desktop file and uncomment one of commented out Exec=... lines and comment out currently used one. After making changes to stm32cubeide.desktop run update-desktop-database as root to apply changes.

Discussion about this Eclipse issues is here: https://github.com/eclipse-platform/eclipse.platform.swt/issues/158

I Exactly do same but same error

I create an empty folder $HOME/Desktop/Workspace, then I open STM32CubeIDE for Flatpak. In the workspace dialog I point the workspace creation to $HOME/Desktop/Workspace. Finally under X11 I launch the native version «stm32cubeide» (not «stm32cubeide_wayland» which is now the default in the .desktop file) and point the IDE to the workspace folder created with the Flatpak version.

dario, Not work for me ;-(

Maziar, I am not using the Flatpak version. I have just stated that as a workaround I have created an empty workspace using the Flatpak version. Native version works when loading from an empty workspace created with the Flatpak version.

@drio

Flatpak's tools have own problem because has separate environments need many configs for access file system ….

For example, I use system utility such as ninja, toolchain or same tools, give incompatibility error (for me glibc error for ninja) because I think Flatpak work similar to docker !

Another thing that worked for me: I have created an empty workspace with the Flatpak version of STM32CubeIDE. Loading this empty workspace with the AUR version of STM32CubeIDE is a workaround for the issue with SWT WebKit first reported by Maziar.

Have any way use one patch for stm32cubeide use local glibc version ... ?

In fact, there are two common problems.
- The first is long lasting good X11 vs poor Wayland support. This is fixed by running STM32CubeIDE on Wayland with exporting GDK_BACKEND=x11 -> stm32cubeide_wayland. This issue mainly causes problems with integrated STM32CubeMX stuff.
- The second problem is with current version of webkit2gtk package.

Seems problem Not fix with run stm32cubeide_wayland

I use X11

SWT WebKitGDBus: error creating DBus server Error binding to address (GUnixSocketAddress): No such file or directory
SWT WebKit: error initializing DBus server, dBusServer == 0

(STM32CubeIDE:221155): GLib-GIO-CRITICAL **: 15:53:54.589: g_dbus_server_get_client_address: assertion 'G_IS_DBUS_SERVER (server)' failed
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f6c52a3ed16, pid=221155, tid=221156
#
# JRE version: OpenJDK Runtime Environment Temurin-11.0.17+8 (11.0.17+8) (build 11.0.17+8)
# Java VM: OpenJDK 64-Bit Server VM Temurin-11.0.17+8 (11.0.17+8, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
# Problematic frame:
# C  [libswt-gtk-4950r5.so+0x3ed16]  Java_org_eclipse_swt_internal_C_strlen+0xf
#
# Core dump will be written. Default location: Core dumps may be processed with "/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h" (or dumping to /opt/stm32cubeide/core.221155)
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid221155.log
Compiled method (nm)   13579 3046     n 0       org.eclipse.swt.internal.C::strlen (native)
 total in heap  [0x00007f6d0bce2c10,0x00007f6d0bce2fb0] = 928
 relocation     [0x00007f6d0bce2d88,0x00007f6d0bce2db8] = 48
 main code      [0x00007f6d0bce2dc0,0x00007f6d0bce2fa8] = 488
 oops           [0x00007f6d0bce2fa8,0x00007f6d0bce2fb0] = 8
Compiled method (nm)   13579 3046     n 0       org.eclipse.swt.internal.C::strlen (native)
 total in heap  [0x00007f6d0bce2c10,0x00007f6d0bce2fb0] = 928
 relocation     [0x00007f6d0bce2d88,0x00007f6d0bce2db8] = 48
 main code      [0x00007f6d0bce2dc0,0x00007f6d0bce2fa8] = 488
 oops           [0x00007f6d0bce2fa8,0x00007f6d0bce2fb0] = 8
#
# If you would like to submit a bug report, please visit:
#   https://github.com/adoptium/adoptium-support/issues
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.

That's correct, it probably should install both variants. Thanks for hint.