STM32CubeIDE and Segger JLink cannot be simultaneously installed! (conflicts with Segger JLink due to udev rules conflict)

[GStap]

If Segger JLink is installed, STM32CubeIDE cannot be installed. See here: https://community.st.com/s/question/0D50X0000AmhtsLSQQ/stmcubeide-installer-failed-on-ubuntu-1804-with-a-dependency-error

If STM32CubeIDE is installed, Segger JLink cannot be installed. See here: https://forum.segger.com/index.php/Thread/6318-Unable-to-install-Segger-JLink-on-Linux-udev-rules-error-possible-conflict-with/#post23198

Please fix this conflict so that we can have *both* installed, as I really would like to work with both. Thank you.

[Markus GIRDLAND]

There's a ticket for this and I know a colleague of mine has been in contact with Segger to try and work out a solution. I'm uncertain if it will be in the very next release, though.

[GStap]

Thanks for the follow-up! For anyone wondering, meanwhile, a work-around is to simply install STM32CubeIDE and then just add its JLink binaries found in "/opt/st/stm32cubeide_1.0.0/plugins/com.st.stm32cube.ide.mcu.externaltools.jlink.linux64_1.0.0.201904160814/tools/bin" to your PATH environment variable. Now, you can use all JLink executables which are provided by the STM32CubeIDE install right at the command-line like normal. This doesn't allow you to arbitrarily upgrade to any JLink version, but it at least allows you to utilize the ST-provided JLink version that came with the STM32CubeIDE.

See here for details: https://forum.segger.com/index.php/Thread/6318-Unable-to-install-Segger-JLink-on-Linux-udev-rules-error-possible-conflict-with/?postID=23209#post23209