STMCUBEIDE: installer failed on Ubuntu 18.04 with a dependency error

[JCorm]

Tried installing the stm32cubeide on ubuntu 18.04 but installer failed

 $ sudo bash st-stm32cubeide_1.0.0_2872_20190423_2022_amd64.deb_bundle.sh 
Creating directory st-stm32cubeide_1.0.0_2872_20190423_2022_amd64.deb_bundle.sh.root
Verifying archive integrity... All good.
Uncompressing STM32CubeIDE installer  100%  
Selecting previously unselected package segger-jlink-udev-rules.
(Reading database ... 318526 files and directories currently installed.)
Preparing to unpack segger-jlink-udev-rules-6.44c-3-linux-all.deb ...
Unpacking segger-jlink-udev-rules (6.44c-3) ...
dpkg: error processing archive segger-jlink-udev-rules-6.44c-3-linux-all.deb (--install):
 trying to overwrite '/etc/udev/rules.d/99-jlink.rules', which is also in package jlink 6.422
Preparing to unpack st-stlink-server-1.2.0-1.2.g88ba147-linux-amd64.deb ...
stlink-server: no process found
Unpacking st-stlink-server (1.2.0-1.2.g88ba147) over (1.1.1-2) ...
Selecting previously unselected package st-stlink-udev-rules.
Preparing to unpack st-stlink-udev-rules-1.0.0-linux-all.deb ...
Unpacking st-stlink-udev-rules (1.0.0) ...
Selecting previously unselected package st-stm32cubeide-1.0.0.
Preparing to unpack st-stm32cubeide_1.0.0_2872_20190423_2022_amd64.deb ...
STMicroelectronics Software License Agreement
 
SLA0048 Rev4/March 2018
 
Please indicate your acceptance or NON-acceptance by selecting "I ACCEPT" or "I 
DO NOT ACCEPT" as indicated below in the media.
 
...
 
I ACCEPT (y) / I DO NOT ACCEPT (N) [N/y]              y
License accepted.
Unpacking st-stm32cubeide-1.0.0 (1.0.0-2872-20190423-2022-1) ...
Setting up st-stlink-server (1.2.0-1.2.g88ba147) ...
Setting up st-stlink-udev-rules (1.0.0) ...
dpkg: dependency problems prevent configuration of st-stm32cubeide-1.0.0:
 st-stm32cubeide-1.0.0 depends on segger-jlink-udev-rules; however:
  Package segger-jlink-udev-rules is not installed.
 
dpkg: error processing package st-stm32cubeide-1.0.0 (--install):
 dependency problems - leaving unconfigured
Processing triggers for desktop-file-utils (0.23-1ubuntu3.18.04.2) ...
Processing triggers for gnome-menus (3.13.3-11ubuntu1.1) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Errors were encountered while processing:
 segger-jlink-udev-rules-6.44c-3-linux-all.deb
 st-stm32cubeide-1.0.0

[DLeko]

My case little different.

There no jlink package in my system.

I've just extract content of install package (by adding --noexec option).

Then I tryed to install st-stlink-udev-rules package and I've received following output:

(Reading database ... 392348 files and directories currently installed.)

Preparing to unpack st-stlink-udev-rules-1.0.0-linux-all.deb ...

Unpacking st-stlink-udev-rules (1.0.0) ...

dpkg: error processing archive st-stlink-udev-rules-1.0.0-linux-all.deb (--install):

 trying to overwrite '/etc/udev/rules.d/49-stlinkv2.rules', which is also in package qstlink2 1.2.3~0~wily

Errors were encountered while processing:

 st-stlink-udev-rules-1.0.0-linux-all.deb

So there was conflict with package qstlink2 (ST-Link V2 Client based on QT) in my system.

[Legacy member]

Thank you, I had the same issue and this helped. (Kubuntu 19.04, x64 with the latest updates.)

[PVyle.1202]

Any idea when we might receive a fix?

[Markus GIRDLAND]

Can't say for sure. It's a whole legal process as well with the right to distribute J-Link packages etc.

I know we have a developer that's looking at it but I don't think a solution is ready any time soon.

[PVyle.1202]

I mean, would it be sufficient to just automatically perform the removal of the "conflicting" Segger tools, as proposed in the workaround (which definitely worked for me), if this error is detected? Or prompt user to do so at least. It seems like a rather simple solution which might save quite a few people some headeache. STM32CubeIDE is a great step forward, and I am affraid little things like this (not able to install without hassle) will unnecesarily steer people away from switching to it..

[DLeko]

In Ubuntu for example there no way to support prompting removal of conflicting package at dpkg level. Only at apt-get level.

So again if you installing package like this:

apt-get install conflicting-package

then system prompt user to remove package which conflicting with another.

But if you install package using

dpkg -i package-version-1.2.3-amd64.deb

then you receive message describing with which your package conflicting but no prompt to remove that package.

So in Ubuntu case as I already suggested you have to extract STM32CubeIDE's content using

./st-stm32cubeide_1.1.0_4551_20191014_1140_amd64.deb_bundle.sh --noexec

And then install all four packages within extracted folder

[Markus GIRDLAND]

Getting a message to make it more clear to the user what has gone wrong and what needs to be done should probably not be too hard, I'll add a request to do so in the ticket.

[Stephan Luik]

Same issue on Mint. Since I am using a small Nucleo board with on-board ST-Link, I do not need the Segger stuff. I used your tips to remove the Segger drivers and clean up the mess. Then the STM32CubeIDE install went smoothly. I agree it would be better to give the user a clear indication of what is happening and how it can be solved. For new users wanting to try out STM32 as a hardware platform, it is this software install crap that steers away possible customers from STM32 - or steers them away to MS Windows...