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

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.

Unless I'm missing something, it appears the PKGBUILD doesn't install the "stm32cubeide_wayland" script, only the stm32cubeide binary?

The stm32cubeide_wayland only export GDK_BACKEND=x11, this solve issue with "board selector" not displayed but this particular crash.

Posted the error on the stm32 forums: https://community.st.com/s/question/0D53W00002ByOp1SAF/error-trying-to-launch-stm32cubeide-on-linux

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 have the exact same issue, as a workarround, i have installed/update the flatpack version wich works fine.

@auguzanellato I'm experiencing the same issue. Downgrading glib2 to version 2.74.6 fixes the issue with STM32CubeIDE, but seems to cause other issues with other packages, at least in my setup.

I have a fully updated system (as of 16/03/23 ~21 UTC) but launching Cube IDE fails with the strlen error. Full error below. Does anybody have any advice? I even tried installing both 1.12.0 and 1.11.2 directly from ST and it still crashes

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:13836): GLib-GIO-CRITICAL **: 22:01:18.195: 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=0x00007f9e55a3ed16, pid=13836, tid=13837
#
# 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 ~/core.13836)
#
# An error report file with more information is saved as:
# ~/hs_err_pid13836.log
Compiled method (nm)   18428 3889     n 0       org.eclipse.swt.internal.C::strlen (native)
 total in heap  [0x00007f9f07ccab90,0x00007f9f07ccaf30] = 928
 relocation     [0x00007f9f07ccad08,0x00007f9f07ccad38] = 48
 main code      [0x00007f9f07ccad40,0x00007f9f07ccaf28] = 488
 oops           [0x00007f9f07ccaf28,0x00007f9f07ccaf30] = 8
Compiled method (nm)   18436 3889     n 0       org.eclipse.swt.internal.C::strlen (native)
 total in heap  [0x00007f9f07ccab90,0x00007f9f07ccaf30] = 928
 relocation     [0x00007f9f07ccad08,0x00007f9f07ccad38] = 48
 main code      [0x00007f9f07ccad40,0x00007f9f07ccaf28] = 488
 oops           [0x00007f9f07ccaf28,0x00007f9f07ccaf30] = 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.