Tried to install Kodi, but it's not starting

Support
,
1

Hey everyone,
I installed Kodi via dnf (v. 21.2.0), but running it fails with /usr/lib64/kodi/kodi.bin: symbol lookup error: /usr/lib64/kodi/kodi.bin: undefined symbol: _ZN13GuidGenerator7newGuidEv

After a bit of searching this thread seems related (mentions the exact error):

That’s the issue, Kodi has been build against the libcrossguid from libcrossguid0_0.0+git200150803-6+b2_amd64.deb

So, I checked that lib64crossguid.znver1 and lib64crossguid0.znver1 are installed. Not sure what else I can try. (I mean as a last resort I could just install the Flatpak version of Kodi)

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:

ROME 25.04

Desktop environment (KDE, LXQT…):

KDE

1 Like
2

Welcome! We are glad to see you and hope you decide to make this your home.

3

Are they installed?

It appears crossguid was built in April, but the last build of kodi was in February. I triggered another build to see if it produces an incremented Release. We already have the latest Release of kodi.

4

Thanks for the responses.

Are they installed?

At least yesterday I thought it was. If I run sudo dnf install lib64crossguid0.znver1 today, I get

Problem: problem with installed package lib64crossguid-0.2.3~20190529-1.znver1
  - installed package lib64crossguid-0.2.3~20190529-1.znver1 obsoletes lib64crossguid0 < 0.2.3~20190529-1 provided by lib64crossguid0-0-0.20150804.1.znver1 from rolling-znver1
  - package lib64crossguid-0.2.3~20190529-1.znver1 from rolling-znver1 obsoletes lib64crossguid0 < 0.2.3~20190529-1 provided by lib64crossguid0-0-0.20150804.1.znver1 from rolling-znver1
  - conflicting requests

Curiously sudo dnf install lib64crossguid0 (without the znver1) just says lib64crossguid-0.2.3~20190529-1.znver1 is already installed.

5

We have identified that it may be related to a long standing issue they have upstream regarding a provided (and probably) older version of that library. There may be a build option that could fix it but we will have to test it. I would say to just use the one in Flatpak until we can investigate.

1 Like
6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.