Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 670374 - media-plugins/kodi-* - addons will not work with kodi as installed, cannot load shared library
Summary: media-plugins/kodi-* - addons will not work with kodi as installed, cannot lo...
Status: CONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Craig Andrews
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-05 15:01 UTC by Ian Stakenvicius (RETIRED)
Modified: 2019-11-24 17:26 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ian Stakenvicius (RETIRED) gentoo-dev 2018-11-05 15:01:53 UTC
With media-tv/kodi-17.6-r6 and -r7 , compiled addons (those with shared libraries) will not load for me with the default library install paths.

Seen this issue with both =media-plugins/kodi-pvr-mythtv--4.15.3 and =media-plugins/kodi-visualization-projectm-1.2.1

AMD64 install, and so library install path is /usr/lib64/kodi/addons/[addon-name].

Other libraries in /usr/lib64/kodi/ (ie those belonging to kodi itself) seem to load just fine.

When I symlink the libraries in, say, /usr/lib64/kodi/addons/pvr.mythtv/ to /usr/share/kodi/addons/pvr.mythtv/ (alongside the addon.xml and related files), then the shared libraries load just fine and the addon will activate and work.

Steps to reproduce error:

1. emerge media-tv/kodi
2. emerge say, media-plugins/kodi-visualization-projectm
3. start kodi
4. go to addons, find projectm and enable the addon, then set it to be used
5. start playing music, and trigger the visualization to work (backspace until the menu disappears, or just wait)
6. An error will pop up reporting it cannot load (or find?) the shared library.


Theory:  perhaps all addon files need to be in the same directory, ie, those files currently in /usr/share/kodi/addons/[addon-name] should be installed alongside the libraries in /usr/lib/kodi/addons/[addon-name] instead?
Comment 1 Craig Andrews gentoo-dev 2018-11-05 18:41:53 UTC
I'm using Kodi 18 so I tested this combination:
media-tv/kodi-9999
media-plugins/kodi-visualization-projectm-9999

and I didn't encounter this problem (the visualization loaded and works fine, it looks pretty cool actually). So it shouldn't impact users once we move to Kodi 18.

Meanwhile, I'll try to find out what's up with Kodi 17 - any help with that would be greatly appreciated :)
Comment 2 Craig Andrews gentoo-dev 2018-11-06 16:06:50 UTC
Kodi 18 beta 5 is now in the Gentoo tree - can you please try with that and let me know if you still experience this issue?
Comment 3 Ian Stakenvicius (RETIRED) gentoo-dev 2019-11-24 17:23:35 UTC
I do.  This seems to occur with every compiled addon I try, which with 18.5 has been media-plugins/kodi-inputstream-adaptive and media-plugins/kodi-visualization-projectm


Similar to this thread https://github.com/xbmc/visualization.projectm/issues/19 , symlinking all of the libraries from /usr/lib/kodi/addons/... into /usr/share/kodi/addons/... allows kodi to load them fine.  I do not know why they don't load in the default library path.
Comment 4 Ian Stakenvicius (RETIRED) gentoo-dev 2019-11-24 17:26:39 UTC
(In reply to Ian Stakenvicius from comment #3)
> I do.  This seems to occur with every compiled addon I try, which with 18.5
> has been media-plugins/kodi-inputstream-adaptive and
> media-plugins/kodi-visualization-projectm
> 
> 
> Similar to this thread
> https://github.com/xbmc/visualization.projectm/issues/19 , symlinking all of
> the libraries from /usr/lib/kodi/addons/... into /usr/share/kodi/addons/...
> allows kodi to load them fine.  I do not know why they don't load in the
> default library path.

It's worth noting that the error is different in kodi-18.5 , now all i see is the log containing a line 'ERROR: IAddonInstanceHandler::CreateInstance: visualization.projectm returned bad status "Permanent failure" during instance creation' (and the plugin not working).