2026-04-29 3:09 AM - edited 2026-05-05 6:54 PM
In Debian unstable (forky/sid), I tried to launch STM32CubeMX2 by launcher or command "cube mx start", but noting happened, thought there were process with command "~/.local/share/STMicroelectronics/STM32CubeMX2/resources/stm32cubemx-application/1.0.0/dist/stm32cubemx2 ~/.local/share/STMicroelectronics/STM32CubeMX2/resources/stm32cubemx-application/1.0.0/dist/resources/app/lib/backend/main.js --no-sandbox --allow-multiple-windows --backendTimeout=30000" and process with command "~/.local/share/STMicroelectronics/STM32CubeMX2/resources/stm32cubemx-application/1.0.0/dist/stm32cubemx2 --type=zygote --no-zygote-sandbox --no-sandbox".
Solved! Go to Solution.
2026-05-04 7:26 AM
Hi @AHah ,
After discussion with the dev team, the issue appears to be related to Electron running on Wayland.
As a workaround, please set the following environment variable before launching the app:
ELECTRON_OZONE_PLATFORM_HINT=x11
This forces Electron to use XWayland instead of native Wayland.
As an alternative fallback, you can also try launching with:
--disable-gpu
Please note that this workaround may no longer be needed in future versions, as Electron introduced a fix in versions >= 38.0.
STM32CubeMX2 currently runs on Electron 37.2.1, which is why this limitation applies today. We will keep you posted once the fix is available.
Please let me know if the issue persists or if you need further assistance.
Regards,
Sara
2026-04-29 3:17 AM
Have you tried to run the application from a commandline, and check for error outputs ?
You can try to run the ldd command on the CubeMX2 application, to check for missing libraries and dependencies.
2026-04-29 6:46 AM
Hi @AHah and welcome to ST Community,
Thank you for reporting this issue and for sharing the process details.
Could you please try launching STM32CubeMX2 from the command line in debug mode with the following command:
cube mx start --log-level debug
After that, please share the relevant log files with us so we can investigate further. You can find them under:
/home/<USER>/.local/share/stm32cube/logs
Best regards,
Sara.
2026-04-29 5:52 PM
2026-05-04 2:19 AM - edited 2026-05-04 2:36 AM
Thanks for sharing the logs @AHah,
I'm currently working on this issue, I'll get back to you asap.
Internal ticket number: CDM0062331 (This is an internal tracking number and is not accessible or usable by customers).
Regards,
Sara.
2026-05-04 7:26 AM
Hi @AHah ,
After discussion with the dev team, the issue appears to be related to Electron running on Wayland.
As a workaround, please set the following environment variable before launching the app:
ELECTRON_OZONE_PLATFORM_HINT=x11
This forces Electron to use XWayland instead of native Wayland.
As an alternative fallback, you can also try launching with:
--disable-gpu
Please note that this workaround may no longer be needed in future versions, as Electron introduced a fix in versions >= 38.0.
STM32CubeMX2 currently runs on Electron 37.2.1, which is why this limitation applies today. We will keep you posted once the fix is available.
Please let me know if the issue persists or if you need further assistance.
Regards,
Sara