2017-10-29, 20:42
I just pulled master. It builds fine but when it runs, there is absolutely no text anywhere. I'm using Confluence. Is there something broken, or did I do something wrong? I've never seen anything like this with Kodi before.
2017-10-29, 20:42
2017-11-02, 06:34
Just to be sure, I cloned the repo anew, configured and built. Again, the code builds and runs, but I have no text anywhere. Only icons are visible. It is not usable in this state.
I'm using Fedora, pulling dependencies from rpmfusion. Is nobody else seeing this behavior?
I'm using Fedora, pulling dependencies from rpmfusion. Is nobody else seeing this behavior?
2017-11-04, 07:23
Of course, sorry about that. I am not sure that debug is enabled -- I can't see ANY text labels. If not, I will need to go back to a prior revision where text is visible and enable it, then run the latest code again.
Here's the output: https://pastebin.com/3kx77zsn
Debug log was not enabled. I built the code from August 30 and the text is present, making it much easier to enable debug logging. Here's the resulting log:
https://pastebin.com/7T67YhN5
Here's the output: https://pastebin.com/3kx77zsn
Debug log was not enabled. I built the code from August 30 and the text is present, making it much easier to enable debug logging. Here's the resulting log:
https://pastebin.com/7T67YhN5
2017-11-05, 21:32
I ran again with the August 30 code, so I could compare the output to the later master branch (pulled a few days ago). The same action was performed: Start Kodi, look for presence/absence of text labels on the main screen, and exit. I removed the timestamps from both files with 'cut' and ran a diff -u. Here is the diff output:
https://pastebin.com/eQGFr4xr
Nothing really stands out, other than the version of skin.estuary going from v2.0.4 to v2.0.6.
https://pastebin.com/eQGFr4xr
Nothing really stands out, other than the version of skin.estuary going from v2.0.4 to v2.0.6.
2017-11-12, 06:27
I was figuring that it was something with my setup that was doing this, because otherwise it would have been noticed by someone else (and fixed!). I configured another machine to build Kodi, and I do not see the problem.
The offending machine is a Dell D620 which uses Intel integrated graphics. "lspci" reports "945GM/GMS/GME, 943/940GML" as the display controller. I may try to do a binary search to see when the labels went away, if I get the time. Problem is, it takes an hour to build Kodi on this old machine. The newer machine builds from scratch in five minutes, but it needs a newer graphics card to actually run properly (it has an ancient GTS 250). That's coming in the mail.
The offending machine is a Dell D620 which uses Intel integrated graphics. "lspci" reports "945GM/GMS/GME, 943/940GML" as the display controller. I may try to do a binary search to see when the labels went away, if I get the time. Problem is, it takes an hour to build Kodi on this old machine. The newer machine builds from scratch in five minutes, but it needs a newer graphics card to actually run properly (it has an ancient GTS 250). That's coming in the mail.