cancel
Showing results for 
Search instead for 
Did you mean: 

Can Not Launch STM32CubeMX2 in Debian with wayland

AHah
Associate

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

1 ACCEPTED SOLUTION

Accepted Solutions
Sara BEN HADJ YAHYA
ST Employee

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


In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.

View solution in original post

5 REPLIES 5
Ozone
Principal III

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.

Sara BEN HADJ YAHYA
ST Employee

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.


In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
 
Sara BEN HADJ YAHYA
ST Employee

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.


In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
Sara BEN HADJ YAHYA
ST Employee

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


In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.