STM32CubeProgrammer proper jlink error handling

[Tom_pm]

It would be great if the STM32CubeProgrammer would do proper error handling for J-Link debug probes instead of crashing.

Issue:
Every times I try to the connect to a STM32 target that is not powered, or not properly connected the GUI pops up three error messages that need to be close separately and on the next connect it pops up another error message and gets stuck. So that the program needs to be completely restarted.

Preferred behavior:
STM32Cubeprogrammer show only a single pop up or only log a warning message and recovers from this situation in a way that that allows it to connect to a STM32 target again.

This is no regression and has been observed since j-link probes are supported.
The last time it has been observed is on a Windows 11 PC with intel CPU, targeting a STM32G4 MCU with STM32Cubeprogrammer v2.21.0, J-Link HW version V11.00(latest FW Apr 1 2025)

[Tom_pm]

And a screenshot from the log, as I could only attach three images to the first post.

The image show the log, of connecting once to a STM32G4 that is not supplied with power, followed by a second attempt to connect once the STM32G4 is properly powered up. The second attempt fails as well rendendering STM32CubeProgrammer unfunctional until the process is ended and newly executed.