STM32 Cube IDE - after initial successfull launch and use now remains idle during splash screen launch stage (Linux)

Question

I am using Ubuntu 22.04 with the official Debian installer of STM32 Cube IDE (latest version), downloaded directly from STM's website.

After installing everything (default installation, which is in /opt/st/ ) I launched the IDE and started playing with it. I managed to quickly find my way (even with my poor skills both with my board and ARM in general) to creating, building and launching a simply blinky test program (blinking the two LEDs) for my STM32L-Discovery board.

The issue now is that on the next day I could no longer launch the IDE. And it has been like that ever since. Once started (both from the launcher created by the installation in the menu (I have XFCE) and via terminal) the IDE remains idle after the progress bar in the splash screen fills up:

The weird thing is that in htop I see no activity whatsoever:

[

It remains like this forever. Well, forever here means 20-30 minutes until my patience runs out. :D

I see that the launcher starts the Wayland version. I tried the other one just in case although that should not be an issue (even with my old laptop) since the first time after the installation it started.

Anyone know a solution? I can try reinstalling and also removing my workspace, although the latter is something the IDE doesn't seem to even go for at this point.

Answer 1

Workaround

To fix this, just remove this file inside your workspace:

.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi

Hope this solves the issue.

(this file is the responsible of saving your workbench layout)

Where to look for fixes and issues

STM32CubeIDE 1.11.x

STM32CubeIDE 1.10.x

Updates

As of 1.11.x I believe its fixed, not encountered this issue again. For me it happened when I forgot to charge my laptop and it shutdown while having STM32cubeIDE open.

Good luck.

Answer 2

It appears that the workspace I have initially created was somehow causing the issue. I decided to start two STM32 Cube IDE instances in parallel. From my Eclipse experience I know that the second instance will complain about the workspace being locked (I normally configure Eclipse to automatically load a specific workspace).

After the second instance started it (as expected) complained about the workspace locked by the first one. I created a new one and the second IDE launched.

I guess this solves my problem unless the issue happens again in which case I would have to point a finger at the IDE not being capable to not corrupt the workspaces it has created itself.