[deivid2]

Hi
I've recently bought a Radxa X2L which is based on the Intel J4125.
I'm facing segmentation faults playing certain livestreams, which are h264 in a ts container, and streamed through m3u8 playlists.
The error log I get from Kodi is

:
2024-04-17 18:49:12.939 T:100079 error : VAAPI/vpp vaCreateConfig error: the requested VAProfile is not supported (12)

(from my research, 12 means JPEG and I don't understand why it's being used here)

along with a kernel message

Code:

[87451.740568] VideoPlayer[100060]: segfault at 7f5460eb004d ip 00007f548aafed49 sp 00007f53eb7fb4c8 error 4 in libc.so.6[7f548aa82000+155000] likely on CPU 2 (core 2, socket 0)
[87451.740597] Code: 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 2e 0f 1f 84 00 00 00 00 00 48 89 f8 48 83 fa 10 72 17 <0f> 10 06 48 83 fa 20 77 6e 0f 10 4c 16 f0 0f 11 07 0f 11 4c 17 f0


On startup, Kodi logs that it can successfully open libva:

Code:

libva info: VA-API version 1.17.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_17
libva info: va_openDriver() returns 0


If I disable 'Enable Hardware acceleration' in Settings -> Player, then the segfault no longer occurs.
If I leave 'Enable hardware acceleration' enabled and disable every codec (MP2, MP4, VP8, ..) I still get a segmentation fault.
If I play the same URL via `mpv --hwdec=vaapi` the playback works fine.
If I download the .ts files manually, I can play them fine (!!)

My Kodi version is 2:20.1+dfsg-1, gotten from `apt` on Debian Bookworm.

Debug logs are here.

What can I do about this? Can I somehow disable libva usage for JPEGs?

[Neo1973]

I remember one VAAPI related fix that could help here, though it's only in Kodi 21 Omega: https://github.com/xbmc/xbmc/pull/23996

I suggest you try the flatpak and see if that fixes the issue. To start the flatpak on GBM use flatpak run --filesystem=/run/udev:ro tv.kodi.Kodi

[deivid2]

The flatpak version works! I think this was indeed my issue - the stream that was causing the segfault has two types of media with different encoding (m3u8 points to .ts files of different resolution) -- maybe that's what was causing it.