error <general>: CVideoPlayerVideo::OpenStream - Invalid framerate 300, using forced 25fps and just trust timestampsI doubt this ^ is enough to cause problems, but it's a simple task to run the file through "handbrake" and fix the file. You can also bump to a current LE13 nightly and see if that magically solves anything? - otherwise I don't see anything unusual in the log (no obvious freeze, no crashes).
SMB connections to the local Samba server (incoming) = Settings > LibreELEC > Services > Samba
SMB connections to another SMB/Samba server (outgoing) = Settings > Services > SMB Client
To make Kodi connect to an older SMBv1 share you need to set min/max = SMBv1. If you set it for min = SMBv1, max = SMBv3 it will default to connecting at SMBv2 and will never attempt SMBv1.
The kernel UAPI's for DRM/KMS/V4L2 are maintained and regularly evolve. If they were not they would be deprecated as dead code and removed from the kernel. There is documentation in the kernel source and since this is a fundamental and core part of the Linux kernel, there is extensive prior-art in kernel code.
Kodi uses mesa for 2D capabilities GLES/GL and opening the EGL context that video/gui are rendered into. Kodi is largely a big fancy wrapper around libavcodec (FFMpeg) which for an RPi4/5 uses the uses the v4l2_request (stateless) UAPI for HEVC and on RPi4 (but not RPi5) the v4l2_m2m (stateful) UAPI for H264 support. FFMpeg also supports fallback to software decoding, e.g. how H264/VP9/AV1 etc. are handled on RPi5. If implementing changes you'd also need to consider VAAPI too, and in the near future NVDEC.
I'm not sure what thoughts you're having, but IMHO anyone who needs to ask where documentation is and how it's done will not be successful in coming up with meaningful changes themselves. Even working with Claude Opus and similar AI tools requires a baseline level of domain knowledge to generate prompts that achieve anything.
Any thoughts based on your experience?
Offtopic: is there any specific SSD brand / model /series that you can recommend from your experience in terms of a) reliability and b) low power consumption?
I've never considered power consumption with SSD's in LE installs as the hardware it runs on has far more impact than the choice of drive and because LE runs in RAM on anything with more than 1GB so there's negligible read/write on the drive.
I've always picked name branded SSD's on the debatable assumption they won't use low-bin chips. Thus the only drives I've ever had die (not a frequent occurence) were name-brand ones. I pull things apart, move things around, and reinstall the OS on a much higher frequency than any normal user though.
It's unusual and something to monitor. If it occurs again it might be the first signs of the memory device inside the SSD starting to have problems. It's the kind of panic that you see when there are faulty cells resulting in bad sectors on the block device; causing a failure to read partition data or preventing successful reading/decompression of the SYSTEM file from the boot partition.
Someone eventually replied on the mailing list and the patch is fixing something else.
Does the new Linux exploit affect settop boxes running Libreelec or OSMC?
LE = technically no because we don't have sudo so the exploit chain is incomplete, but as stated above, everything already and intentionally runs as root so there's no need to use the exploit in the first place.
OSMC = someone else's distro, go ask them in their forum.
There's an RPi4 build in my test share too; probably not as current as the RPi5 one but close enough. I find the OSD tonemapping to be a little off on RPi5 hardware compared to e.g. RK3588, e.g. the OSD panels that are normally ~85% transparent are more like ~65% and need to be darker, but everything is still work in progress. I didn't specifically check for the leak in a while but that's because things have been behaving so that's probably been resolved. Go test and report back.
In the current state with audio working SSH into the box and run getedit create .. and this will rig the box to believe this specific TV is always connected; thus allowing the audio to be detected even when the TV hasn't been turned on yet or is still starting up.
Is anyone else running into an issue where the screensaver kicks while playing a video, and it's not possible to get out of it?
I've not seen this on any of the platforms that I use regularly. I'd stop and rename /storage/.kodi out of the way and then start over with a clean Kodi instance. Stop/copy/move config and bits back until you find the offending change.
AFAIK the EmuELEC distro uses the Amlogic legacy boot process so if the box is currently booting LE then the u-boot environment is adapted to LE boot files and you'd need to (re)trigger recovery boot so that Amlogic u-boot reads their bootscripts from an SD card, which will modify the u-boot environment to work with their boot files/names. Beyond that, it's best you contact EmuELEC devs for support (I'd assume it has a forum somewhere) because I've never downloaded it or booted it on anything.
So the GUI plane is active (as expected) and in AR24. So hopefully XRGB8888 can be handled.
So the GUI plane supports XR24, but the Video plane does not (YUV things only) so next step is to run kmsprint | paste when the emulator is playing (and screen is dark) to see whether the plane is AR24 (default for Kodi) or XR24 .. or what. At that point we need to ping garbear for guidance on what's normal or correct.
debug <general>: bool KODI::WINDOWING::GBM::CDRMUtils::FindPlanes(): Using video plane 41
debug <general>: bool KODI::WINDOWING::GBM::CDRMUtils::FindPlanes(): Using gui plane 38
...
debug <general>: GameClient: Loading game.libretro.uae2021 in standalone mode
debug <game.libretro.uae2021>: Setting libretro pixel format "XRGB8888"Run modetest | paste and share the URL. I'm not familiar with retroplayer internals but let's see if plane 38/41 are supporting that format (IIRC, XRGB8888 = XR24). I'm blind guessing at the problem though.
NB: Do other emulators, e.g. something simple like a SNES one, work or show the same issue?
PR is merged 
[Unit]
Description=nfs-y-script
Requires=network-online.service
After=network-online.service
Before=kodi.service
[Mount]
What=192.168.1.2:/y
Where=/storage/y
Options=nolock
Type=nfs
[Install]
WantedBy=multi-user.targetThe Either use '-o nolock' to keep locks local, or start statd message comes from the underlying NFS libs but systemd knows whatever follows Options= is an option so you don't need to provide the -o prefix to nolock.
rozpruwacz please retest using an image built from the amlogic branch in my GitHub LE repo or add the hbiyik/reardonia Kodi patchset that you find in that branch to the test image.