2026-04-29 3:09 AM - edited 2026-04-29 3:10 AM
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".
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