Linux [SOLVED] Kodi Isengard beta2 - Text is not displayed
#1
Hi,

I'm building Kodi 15 Isengard rpms for openSUSE, the build finished successfully but the boxes text is not displayed.

The debug log showed that the strings files were loaded :
Code:
19:23:00 T:140399589910848    INFO: load language info file: special://xbmc/language/English/langinfo.xml
19:23:00 T:140399589910848   DEBUG: trying to set locale to en_US.UTF-8
19:23:00 T:140399589910848    INFO: global locale set to en_US.UTF-8
19:23:00 T:140399589910848    INFO: load English language file, from path: special://xbmc/language/
19:23:00 T:140399589910848   DEBUG: POParser: loaded 3267 strings from file /usr/share/kodi/language/English/strings.po
...
19:23:10 T:140399589910848    INFO:   load skin from: /usr/share/kodi/addons/skin.confluence (version: 2.5.12)
19:23:10 T:140399589910848    INFO:   load fonts for skin...
19:23:10 T:140399589910848    INFO: Loading fonts from /usr/share/kodi/addons/skin.confluence/720p/Font.xml
19:23:10 T:140399589910848   DEBUG: POParser: loaded 149 strings from file /usr/share/kodi/addons/skin.confluence/language/English/strings.po
19:23:10 T:140399589910848    INFO: Loading skin includes from /usr/share/kodi/addons/skin.confluence/720p/includes.xml
19:23:10 T:140399589910848    INFO:   load new skin...
19:23:10 T:140399589910848    INFO: Loading user windows, path /usr/share/kodi/addons/skin.confluence/720p

Image


Before running Kodi I've removed ~/.kodi subdirectory

Did I missed something when running configure ?
Maybe I missed some files in the rpm ?

Thanks,
Sagi.
Reply
#2
Debug Log and by that a full complete debug log into a pastebin (please dont post the whole thing inline) What you posted is useless.

Also a config log from your kodi build into a pastebin.
Reply
#3
log can be found here : http://pastebin.com/FMzaUapp

build log :
https://pmbs.links2linux.de/build/home:s...trunk/_log

one more thing, I get the following warnings from libpng in the console :
Code:
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: cHRM chunk does not match sRGB
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
Reply
#4
building Texturepacker fails:
[ 370s] checking for gif_lib.h... no
[ 370s] configure: error: "gif_lib.h not found"
[ 370s] Makefile:36: recipe for target 'native' failed
[ 370s] make: *** [native] Error 1
[ 370s] make: Leaving directory '/home/abuild/rpmbuild/BUILD/kodi-1433925383.658e700/tools/depends/native/TexturePacker'
[ 370s] configure: "Texturepacker not found"
Reply
#5
That png is just a warning you can ignore. If you search google it will explain it.

At the time I was looking the build was still going but the texturepacker error was there. else it was slightly early to tell and wasn't getting any great information from the ongoing build log.

I would look at setup as well, did you add user permissions (policykit or systemd) to the user running Kodi and does it belong to the correct user groups?
Reply
#6
I've added the missing gif lib, but now TexturePacker is failing on linking because it is unable to resolve libraries dependencies.
I'm looking into it.

Regarding the user and group permissions, the server is obs (Open Build Server) for openSUSE 3rd parties rpms.
It uses a user named abuild which is set with the right permissions, all opensuse packages are being built using obs (it is just like launchpad for ubuntu)
Reply
#7
I mean the system where you installed it and are running it.
Reply
#8
Yes, the user that I'm using is the main user for this PC (not root) , this is not the first time that I'm building Kodi, I'm maintaining kodi rpms for openSUSE for quite some time, but this is the first time I had such an issue.

To make the story even more strange, I've built kodi locally on my pc, outside obs build environment.
In this build I got the same gif_lib and TexturePacker errors :
Code:
checking gif_lib.h usability... no
checking gif_lib.h presence... no
checking for gif_lib.h... no
configure: error: "gif_lib.h not found"
Makefile:36: recipe for target 'native' failed
make: *** [native] Error 1
make: Leaving directory '/tmp/kodi-1433789533.00f3170/tools/depends/native/TexturePacker'
configure: "Texturepacker not found"
but build finished successfully, I then installed it using :
# sudo make install
it was installed to /usr/local/....
and when running kodi from /usr/local/bin/kodi
the text appeared as it should and I didn't get those libpng warnings

but then, when running kodi from /usr/bin/kodi (which was installed using the rpm from obs)
the text did not render and the libpng warnings reappeared
Reply
#9
Sure, had to ask.

No idea personally, this sort of thing happened once or twice with bad drivers a long time ago from ATI I wonder if there's anything like that going on on your nvidia drivers now. Just a thought in any case.

The png errors can be ignored (never had them myself) its the libpng 1.6 doest accept wrong icc profiles in the pngs and you can actually fix the pngs, google the error and you get a fix.
Neither the pngs warnings or the texturepacker failing would affect this in any manner.

Upgrade your drivers...
Reply
#10
I went over the build logs and the startup logs and found that the one running from obs rpm
is linked against :
Code:
# ldd /usr/lib64/kodi/kodi.bin | grep libGL
        libGLU.so.1 => /usr/lib64/libGLU.so.1 (0x00007fcacb13f000)
        libGLEW.so.1.10 => /usr/lib64/libGLEW.so.1.10 (0x00007fcacaeae000)
        libGL.so.1 => /usr/lib64/libGL.so.1 (0x00007fcacac1e000)
# ls -la /usr/lib64/libGL.so.1
lrwxrwxrwx 1 root root 14 Feb  4 21:32 /usr/lib64/libGL.so.1 -> libGL.so.1.2.0
# rpm -qf /usr/lib64/libGL.so.1.2.0
Mesa-libGL1-10.3.7-91.6.1.x86_64

and the one that I complied locally on my PC is linked against the one coming from nvidia driver :
Code:
# ldd /usr/local/lib64/kodi/kodi.bin | grep libGL
        libGLU.so.1 => /usr/lib64/libGLU.so.1 (0x00007fb288460000)
        libGLEW.so.1.12 => /usr/lib64/libGLEW.so.1.12 (0x00007fb2881c3000)
        libGL.so.1 => /usr/X11R6/lib64/libGL.so.1 (0x00007fb287e76000)
# ls -al /usr/X11R6/lib64/libGL.so.1
lrwxrwxrwx 1 root root 15 Jun 12 20:50 /usr/X11R6/lib64/libGL.so.1 -> libGL.so.340.76
# rpm -qf /usr/X11R6/lib64/libGL.so.340.76
nvidia-glG03-340.76-40.1.x86_64

Setting LD_LIBRARY_PATH correctly solved this issue.

I then found the following thread :
opensuse with nvidia displays no text in menu
Reply
#11
Yea, I thought it smelled driver related.

If you can please full edit main post and mark thread as solved maybe it will help others reach the same solution a little faster next time.
Reply

Logout Mark Read Team Forum Stats Members Help
[SOLVED] Kodi Isengard beta2 - Text is not displayed0