Posts by sunlollyking

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.

Hi All,

So i'm running a 10th Gen Intel NUC i3 and i'm trying to upgrade to the latest nightly from one of the retroplayer 13 builds. However when i try to upgrade i see this message on the terminal.

ERROR: LibreElec-Generic.x86-64-13.nightly-20250725-f0482de.img.gz is not compatible with Generic-gl.x86.64 hardware - Update cancelled

So i know the builds now include the full switch to GL but i thought this should be compatible with my NUC? I'm downloading the usual Generic build and not sure if i should now switch to Generic-Legacy?

Any help is much appreciated

Fab - it's not a dealbreaker i can have a little longer before it's merged to main - but cheers for the help here.

That looks like the one!

Just to highlight for anyone else who's wanting to fix this. I managed to fix by removing the Universal Remote settings from the AVR in my LG G4 - Weird but now the remote controls everything its great.

Hi, not sure if this is a Kodi issue, a CEC driver issue or an issue with LE.

However - in testing out my new receiver. I keep trying to change the CEC settings in the input menu to knowing it's connected to the receiver and not the TV.
The setting seems to stick however when i reset my Intel NUC (w/ Pulse-Eight adapter) it keeps resetting the setting back to 'connected via TV' and my previous setting has been overruled.

I've still not managed to get CEC working yet via my Denon X1800H despite on Kodi boot i see a Pulse Eight Notification highlighting connected to TV - DenonX1800 but i'm thinking that this issue is currently happening because of the setting problems.

This too happens on the LE 12 branch too.

Any help is much appreciated.

Just wondering if people can clarify some settings for me. Im about to invest in a surround set up but want to make sure that i can successfully pass audio through from my device.

I'm using an Intel NUC 10th gen.

My TV connects to it via HDMI 1 and the soundbar is connected via eARC to HDMI 2. I've enabled passthrough but have no audio. In my settings what should audio output device be ? Should it be HDMI 1, 2? I'm a little unsure and dipping my toe into the expensive world of audio is daunting. Any support would be much appreciated.

I'm hestiant to connect the tv directly to the soundbar because i've already got a device plugged into it. My PS5 is successfully able to trigger things like atmos despite being plugged into HDMI 4.