Can't install KiCAD

Support
1

Hello,

Requirements:

I have Searched the forum for my issue and found nothing related or helpful
I have checked the Resources category (Resources Index)
I have reviewed the Wiki for relevant information
I have read the the Release Notes and Errata

OpenMandriva Lx version:

OpenMandriva Lx release 25.11 (ROME) Rolling for znver1

Desktop environment (KDE, LXQT…):

KDE plasma X11

Description of the issue (screenshots if relevant):

After system update KiCAD was removed by the update. I get the following when trying to install KiCAD. (I tried sudo dnf install kicad and sudo dnf install kicad --refresh)

Updating and loading repositories:
Repositories loaded.
Failed to resolve the transaction:
Problem: conflicting requests
  - nothing provides libabsl_log_internal_check_op.so.2501.0.0()(64bit) needed by kicad-9.0.2-1.znver1 from rolling-znver1-extra
  - nothing provides libabsl_log_internal_message.so.2501.0.0()(64bit) needed by kicad-9.0.2-1.znver1 from rolling-znver1-extra
  - nothing provides libabsl_log_internal_nullguard.so.2501.0.0()(64bit) needed by kicad-9.0.2-1.znver1 from rolling-znver1-extra
  - nothing provides libabsl_flags_marshalling.so.2501.0.0()(64bit) needed by kicad-9.0.2-1.znver1 from rolling-znver1-extra
  - nothing provides libabsl_hash.so.2501.0.0()(64bit) needed by kicad-9.0.2-1.znver1 from rolling-znver1-extra
  - nothing provides libabsl_time_zone.so.2501.0.0()(64bit) needed by kicad-9.0.2-1.znver1 from rolling-znver1-extra
  - nothing provides libprotobuf.so.30()(64bit) needed by kicad-9.0.2-1.znver1 from rolling-znver1-extra
You can try to add to command line:
  --skip-broken to skip uninstallable packages
1 Like
2

@Heikki
welcome1

Please remember to post your console content as code.
Thank you.

3

Sorry about that. I’ll edit the post.

4

Thanks :wink:
Looking at kicad, maybe it just needs a rebuild.

5

It’s broken because one of the deps is also broken. The package is also still using Qt5 which is EoL. It will need to be fixed.

1 Like
6

Hello @Heikki , I have updated the KiCAD package to latest 9.0.6 point release in Cooker, it will make its way down to ROME/Rolling soon™.

A longer explanation is that aside from KiCAD requiring to be rebuild against the newer abseil-cpp and protobuf packages as noted by your transaction log output above, some of KiCAD’s other dependencies also required updating (python-wxpython) following a wxwidget release that introduced an unintentional ABI change that upstream then issued a subsequent bugfix release to rectify.

We already had that release as our wxwidgets package but the python-wxpython package which is built using wxwidgets also required updating to its latest upstream release which is built against the corresponding wxwidgets version that carried the ABI fix, all of that is fixed up in Cooker and KiCAD 9.0.6 is built/packaged.

Unfortunately I don’t think there is much you can do but wait for the next UM from Cooker to ROME which I am told will be coming soon™ as it would require you rolling back update history via dnf to get your system back to its pre-update state, it is do-able but I do not know what else might break (or not) in doing that given the large number of updated packages involved and any configuration changes they may have brought with them - in any case I would definitely recommend creating a backup before even attempting to do that.

If you are super stuck/desperate for KiCAD then a much safer route IMO would be running Cooker in a VM and installing KiCAD in there (KiCAD works perfectly fine with software rendering, even its 3D rendering is decent). You can setup a VM using qemu/VMM or virtualbox which would keep your ROME system intact its current state until those package updates arrive through the repos.

I was almost caught by this same issue too but held off on hitting the Y key on my Rome machine when I spotted the KiCAD packages were marked for removal as I have PCBs arriving this week which I need KiCAD in order to access my project files to verify them with.

1 Like
7

KiCAD uses wxWidgets, wxPython and wxGTK under the hood and not Qt.

I really wish they would move to Qt as I much prefer its UI styling in general but they began using wxWidgets for cross platform reasons way back when no single toolkit really offered that support other than wxWidgets.

8

I can wait until it makes its way down to ROME, since I still have Debian on my other computer. Thanks for the quick action to make the package work again.

1 Like