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 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.

@j0b314: STM32CubeIde is based on Eclipse, which doesn't support Wayland well.

In the /usr/share/applications/stm32cubeide.desktop application file, there is a commented out entry for running STM32CubeIDE in x11. Comment out the enabled exec, and uncomment the entry that contains "GDK_BACKEND=x11". Then update the application entries with "update-desktop-database". It should then work.

@kumen: Thanks for packaging. Unfortunately I have the following issue:

After starting and trying to create a new STM32 Project, the Target selection box pops up but stays empty. In this dialog you can usually select your desired CPU or eval board. But the only thing I can see is the headline "Target selection" and "STM32 target or STM32Cube example selection is required".

indecisive, you're welcome. I noticed this issue after upgrading my system. By looking at the few packages that were upgraded, the only package that seemed even distantly relevant was glib2 upon which basically the whole system depends. Other packages such as gst-plugins-base, sudo, mpv and ffmpeg are so unrelated to STM32CubeIDE that I excluded them from being the culprits. As of now the downgrade is not needed anymore because the issue with glib2 was fixed upstream. A full upgrade is all that is needed.

@dario, that worked, thank you! Confirmed as working on both of my systems.

Out of curiosity, how did you know to do that?

indecisive, you may downgrade glib2 to version 2.74.6-1 as a workaround. EDIT: try with a full upgrade of your system. Now it should work out of the box.

@kumen: Thank you for packaging.

As of now, the current version of this package (1.12.0-1) does not launch. Instead, it crashes, and a coredump is created blaming the function "Java_org_eclipse_swt_internal_C_strlen".

Can you verify if this behavior is the same on your system?

Thank you all for advice. I tried to implement them.
GDK_BACKEND=x11 in .desktop file is now commented out.
Wayland related issues and crashes tips: https://github.com/eclipse-platform/eclipse.platform.swt/issues/158

@kumen: First, thank u for packaging. Why not preventing the 99-jilink.rules.patch from downloading (already skipped udev rules)? BTW typos of "installation" with only one "l" in the PKGBUILD.

That's correct. The PKGBUILD must not run any programs outside of the provided functions, since the execution environment is undefined.