Posts by sunlollyking

Cool so the branch now contains all the code for GL and GLES - i've been using the GLES generic build now since Friday quite heavily and have worked through some bugs, but it's all looking quite good now. Again - appreciate any reviews or pointers you may have. We've cherry picked a few commits to go into master to try get the diff down and will hopefully get some proper retroplayer test builds with this in soon but feel free to test and ask any questions.

I've got a build with full Retroachievement support, GLES with working Dolphin, Flycast others, as well as a few other feature QOL improvements e.g Default emulator with per game override for a folder. Also fully supports filters, and scaling.

I've managed to get GLES all up running and it's running all cores. It does seem to have broken shaders (Video filters) so just working through some kinks on this.

In terms of merge strategy i'm thinking i'll try and get the OpenGL branch in first allowing regular linux folks to use OpenGL and then it's only a small diff ++ to get GLES working so i'll then work on getting that merged. I'll share the branch and a PR hopefully next week - but as always keen on any reviews.

Cool no worries - i'm nearly finished down this path currently - this build is just for my personal use I just thought i'd open and share the work.

If GLES is the strategic route - i think once i've got OpenGL working great on my instance i'll see how easy it is to port to GLES and hopefully once working we can then see how to get it merged in.

[EXPERIMENTAL] RetroPlayer: OpenGL hardware rendering for game clients by sunlollyking · Pull Request #151 · garbear/xbmc

Paired with kodi-game/game.libretro#164, which must land alongside this one — the Game API version moves to 7.0.0. How strictly Kodi should refuse older…

github.com

I've managed to get OpenGl support built into garbears retroplayer repo and now have successfully built a libreelec image generic image.

I'm after some good critique and testing from you all if possible. Aware this is fairly thrown together but if it all works I'd love to keep chipping away and get it into Kodi and LE.

Please test review and give me all feedback

Hi All,

Wondering if i can get some support from someone on the LE team. Currently trying to implement RetroAchievements which alongside new dialogs are fully working for NES roms. It looks like Garbears test builds show the functionality as all working across Ubuntu, Windows etc. However when popping an achievement on LibreElec the game seems to crash - It looks like this also could affect Mac but given i'm vibe coding the heck out of this i'm keen on getting any support to might make this go a little quicker.

RetroAchievements: Full integration and in-game OSD dialogs for achievements and leaderboards by sunlollyking · Pull Request #147 · garbear/xbmc

Happy to answer any questions or help diagnose. The build is here https://github.com/garbear/xbmc/r…c8715365.img.gz

Currently got the screen res maxed to 4k in the GUI - everything seems to be working again. Strange quirk.

Is there any plans to i guess make 4K GUI support more stable within Kodi - feels odd for it to have so much jank.

Cheers for the support!

Hey just set up an old Samsung galaxy book 2 as a libreelec machine. I'm also using a pulse eight adapter.

I've just been trying to play a few 4k videos but they all play like the image I've added here in the top left corner only. It's odd. Any idea how to fix this ?

Renaming my guisettings as to trigger a new one being generated on restart seemed to fix it. But... i'm wanting to keep my old settings without having to go through all the menus and recreate it ? Is there a way to do this? There must be something in the new GUI settings that has fixed it without taking all the other bits ?

All help is appreciated,

Just for closure here - Its looking v likely this is the error and it's now being fixed - thank god - A nightmare to triage

It appears to - I'm out of safe mode (weirdly still have the red colour on estuary) but going to start copying over addons tranche by tranch tomorrow and see if i can find out which one is the issue.

Yes so in my kodi.FAILED i renamed my addons folder to addons_DISABLED in the hope then kodi would recreate the folder and one by one i could reintroduce them. It's just such a tough one to debug if it is race condition caused because i could reenable an addon and it boot successfully then the next boot it fails and i wouldn't know which addon caused the crash.

The segfault error is interesting - it's been that repeated error in my logs for months it doesn't look like there's a fix in sight ?

I renamed my addons folder to addons_old. Deleted .kodi folder and renamed kodi.FAILED to .kodi. However it has still somehow booted into safe mode and the failed folder has regenerated?

Again thanks for the replies

OK thanks for the reply - I think the problem i'm facing is that it seems like my error could be a race condition so once i start reenabling, sometimes i get the boot issue, sometimes it'll work fine.

Hi - i can't fully remember when this error started to occur - whether it is addon related of LE related. But about a month ago - i'll get a crash on Kodi initialisation and it'll then go into a boot loop 4/5 times before hitting the safe mode.

I've tried disabling different addons and can't pinpoint it. I've put lots of logs into ChatGPT to help triage the issue and it thinks it could be some kind of python addon compatibility issue but doesn't specify / a race condition / something to do with loading up fonts. It's killing me trying to diagnose this so thought i'd see if i could draft in the pros.

ChatGPT analysing the log said the following:

Crash log (kodi_crashlog_20250914204731.log)

kodi_crashlog_20250914204731

• Kodi crashes with a SIGSEGV (segmentation fault).

• The core dump trace shows the main crash is in:

  Code

  /usr/lib/libpython3.13.so.1.0

  → This is Kodi’s Python interpreter (used for add-ons).

• Just before the crash:
  • Thread 48 shows HarfBuzz font shaping (text rendering).
  • Stack trace: CGUIFontTTF → CGUIFont → CGUITextLayout → CGUILabel → GUI rendering.
  • At the same time, Python invokers (addons/scripts) are running in other threads.
• This suggests Kodi is dying when trying to render some text from an addon (or skin element) while Python is executing.

Why it’s crashing

• The crash is happening at the intersection of:
  • Python 3.13 integration (newer Python, nightly build).
  • Font rendering via HarfBuzz when labels/text are updated.
• This is very likely a bug in the nightly LibreELEC/Kodi build, not your configuration.
• Addons/skins that trigger heavy GUI updates (labels, list items, metadata fetches) increase the chance of hitting it.

Here is my log

gist:3b209840a1f4132810dfbe65b2fb19b2

GitHub Gist: instantly share code, notes, and snippets.

gist.github.com

P.S I've been trying to use Arctic fuse 2 as my skin but this may be where the issues are? I'll happily enable any debug logging etc. I've also been messing with CEC settings recently as that's been throwing a wobbler so happy to show you any of that if needed to eliminate it being an error.

I've been having this issue too on 13.0 nightlies. Essentially mapping my settings via the GUI and then on a restart all would be reset and overruled. My solution was to ssh in and chmod 444 my CEC settings so they became read only once i'd set them to what i wanted.

Thanks yep - command worked - i shouldn't have tried to make the directory first.

Yes this didn't work - I SSHd in - ran the command and placed the update the .update folder itself and i still get the same error.

Placing an update in the .nocompat folder gets ignored and kodi still boots

So i've created the directory .nocompat

Does the update file go in that directory or in the normal update directory ? Both aren't seeming to work.

In update is says it's not comaptible

The update is just ignored when in the nocompat directory

Sorry you will already know this but i did see that message where it says if i

Create /storage/.update/.nocompat to disable compatibility checks and risk a non-booting system.

So this should solve my issue and hopefully not risk a non booting system.