STM32CubeMX 6.9.0 keyboard entry no response frozen, freeze, stuck (Linux)

[debugging]

Using the latest CubeMX 6.9.0 on Ubuntu  23.04  The following has happened quite a few times in the past years , also on  previous Linux and CubeMX versions. Now would like to raise this  issue as it's becoming very annoying now doing more work in CubeMX. There are now more situations where the keyboard just does not respond anymore. The mouse does.

1. When creating a new project and entering an partnumber, the dialog box  sometimes get stuck. Mostly after entering a partnumber that does not exists.  You can continue by  selecting from the drop down list and then creating the project,  but when trying to save you are out of luck, you cannot enter a filename so you have to start all over again. a lot of wasted time.

2. When entering a pin number in the dialog box. sometimes this text box get stuck. Luckily you can save the project, but need to close CubeMX and restart it gain. A lot of time wasted.

 

This happens no matter it is an MCU or MPU project

 

 

 

 

[Issamos]

Hello @debugging 

I suggest you to update to CubeMX 6.9.1 and look if the problem persist. Else I suggest you to uninstall all the ST tools, files, directorys,.. and reinstall them. That may solve the problem.

Best regards.

II

[debugging]

Is that because of a release note for 6.9.1 that would address this problem or just a wild guess / trial and error attempt ?

[AScha.3]

no need to update, because this editor hang-up still there...

i have ide 1.13.1 (with cube  6.9.1-RC1) installed on Linux MX18, some days ago.

Problem is in text boxes, to make some input, ie giving user defined name to a pin.

i had named a pin with LED on it : led-red . ok, but then i decided to write it more nice: to LED-red ->

open the dialog box on pin, click mouse -> cursor to "-" position, then backspace to delete the "red" .

error.box pops up : >> names must begin with a character or number << (or similar) -> OK. 

but from now on cannot edit anything useful any more ! even close and open MX view : problem remains!

only close and restart full IDE makes edit possible again.

Always some fun with STM /or java (?) software . :)

[debugging]

Yup, and I have  feeling it's related to backspace. It happens often when trying to correct the entry in text boxes. Interesting no one reported this and I experienced this freeze for many years ! Not sure, but I believe CubeIDE is based on Eclipse., perhaps related to the core eclipse code.

 

[AScha.3]

--- dont believe ...just look:

+ edit box:

and problem may be : destroy start of string , using backspace.

+

 

this eclipse/java sh.t can make some surprise:

- on my laptop with Win10 , IDE 1.13.1 open never again, after creating a project. only >> error occured. see log. <<

surprise...

and here, on my Linux PC, had to install IDE new, after i made a big mistake: i install additional color scheme in eclipse, from eclipse marketplace. then i got new colors for Java - BUT cannot edit C-files anymore. IDE destroyed.

big surprise.... 

[debugging]

Cannot reproduce on latest 6.12.0

[cyclebot]

This is totally, 100%, completely reproducible on 6.12.0. Sometimes I can only type a single character before the entry field becomes unresponsive. At the moment, this is stopping me dead in my tracks and has a become a major show stopper for me.

I was using an older version of CubeMX (6.10.0) that I'd been using for a while, when this suddenly started happening earlier this week. Prior to this week I was using an F4 processor, and then I created a new project, switching to a G4 processor. I don't know if that's the cause of this bug, but I'd been using that older version of CubeMX for at least 6 months with the F4 project and never seen this bug until switching processors. I'm not sure that it's related or not - all I know is I'd been using 6.10.0 since it came out late last year without any issues. 

 

 

 

[debugging]

Weird, What java your are using ? i haven't bumped into this issue anymore recently.

[cyclebot]

Apparently I'm running the java version that's distributed with CubeMX:

jdosher@feynman:~/STM32CubeMX$ ./STM32CubeMX  
Check exe path on linux
FullExe path1 is: /home/jdosher/STM32CubeMX/STM32CubeMX
Exe path is: /home/jdosher/STM32CubeMX
Search java from relative path ----
Checking java in /home/jdosher/STM32CubeMX/./jre/bin/java
current working dir : /home/jdosher/STM32CubeMX
av[0] ./STM32CubeMX
chdir to :/home/jdosher/STM32CubeMX/.
New current working dir /home/jdosher/STM32CubeMX
Full command: /home/jdosher/STM32CubeMX/./jre/bin/java
-args[0] java
-args[1] -jar
-args[2] STM32CubeMX

Which appears to be 17.0.11 (I believe 23 is the most recent)

jdosher@feynman:~/STM32CubeMX/jre/bin$ ./java -version openjdk version "17.0.11" 2024-04-16 OpenJDK Runtime Environment Temurin-17.0.11+9 (build 17.0.11+9) OpenJDK 64-Bit Server VM Temurin-17.0.11+9 (build 17.0.11+9, mixed mode)

 

Also, 'which java' returns nothing, and 'java -version' and 'javac -version' returns "command not found". Frankly, I'm a bit confused, because I'm sure my system has java installed...right? Does CubeMX come with a version of java it falls back to in the event that it can't find a system-wide install? I'm going to install java from apt and see what version CubeMX runs after that. 

[cyclebot]

Post java install:

It appears that jre 17 is the stock version for Debian 12. After an apt install this is what I get

java -version
openjdk version "17.0.12" 2024-07-16
OpenJDK Runtime Environment (build 17.0.12+7-Debian-2deb12u1)
OpenJDK 64-Bit Server VM (build 17.0.12+7-Debian-2deb12u1, mixed mode, sharing)

And when running CubeMX it appears to still use the version of java in the CubeMX directory

jdosher@feynman:~/STM32CubeMX$ ./STM32CubeMX  
Check exe path on linux
FullExe path1 is: /home/jdosher/STM32CubeMX/STM32CubeMX
Exe path is: /home/jdosher/STM32CubeMX
Search java from relative path ----
Checking java in /home/jdosher/STM32CubeMX/./jre/bin/java
current working dir : /home/jdosher/STM32CubeMX
av[0] ./STM32CubeMX
chdir to :/home/jdosher/STM32CubeMX/.
New current working dir /home/jdosher/STM32CubeMX
Full command: /home/jdosher/STM32CubeMX/./jre/bin/java
-args[0] java
-args[1] -jar
-args[2] STM32CubeMX

So, not much difference in versions. 17.0.11 for the one in the CubeMX directory, and 17.0.12 for the apt installed version. 

 

The rest of my system is pretty stock Debian 12, with updates applied frequently.

I've had to resort to making project modifications in CubeMX on my Macbook, check it into git, then going back to my Linux box, pulling the update, then moving on. It gets a bit tedious doing that!