2021-05-16, 02:15
Please post the output of the groups command run by the user you use to run kodi. Are you in the video and render groups?
2021-05-16, 06:03
(2021-05-16, 02:15)yasij Wrote: Please post the output of the groups command run by the user you use to run kodi. Are you in the video and render groups?
Holy crap i was away for a day and this exploded. This is mildly above my head so I will research tonight and get back to you tomrrow with the output of the commands you requested @yol
2021-05-16, 07:49
it looks like vaapi in flatpak is ancient (1.8): https://github.com/flathub/org.freedeskt...AAPI.Intel
2021-05-16, 14:16
@yol Here are requested logs:
WAYLAND_DEBUG=1 kodi
https://paste.kodi.tv/lirawimila
Crash Log
https://paste.kodi.tv/hosuremuba.kodi
I am not sure how to enable debugging if I cannot access program though.
WAYLAND_DEBUG=1 kodi
https://paste.kodi.tv/lirawimila
Crash Log
https://paste.kodi.tv/hosuremuba.kodi
I am not sure how to enable debugging if I cannot access program though.
2021-05-16, 14:26
(2021-05-16, 02:15)yasij Wrote: Please post the output of the groups command run by the user you use to run kodi. Are you in the video and render groups?
Outside flatpak (where kodi runs) I'm on both the "video" and "render" groups.
Inside flatpak (where the vaapi auth error happens) I'm only in the "nfsnobody" group but it looks like inside the docker the "/dev/dri/*" devices are all owned by "nfsnobody", thus this shouldn't be a problem.
Am I the only one which can not run the flatpak version? Or is this happening to everyone?
2021-05-17, 22:41
So... the flatpak issue is definitely related to my setup: I tried with another laptop and "vainfo" (and "kodi") work without problems inside flatpak.
Both laptops are running an updated Arch, the only difference being that the new laptop uses an Intel GPU with "intel-media-driver" and the old one (where the error happens) uses a Vega GPU with "libva-mesa-driver".
In any case this has nothing to do with Kodi. Sorry for all the noise.
Both laptops are running an updated Arch, the only difference being that the new laptop uses an Intel GPU with "intel-media-driver" and the old one (where the error happens) uses a Vega GPU with "libva-mesa-driver".
In any case this has nothing to do with Kodi. Sorry for all the noise.
2021-05-30, 17:41
For anyone still following this: It is most likely caused by an incompatibility between certain versions of mesa and VA-API. The VA-API fix is https://github.com/intel/libva/pull/476 . Flatpak has a backport merged and lined up for the next release, I believe. If you are not using Flatpak, make sure your mesa and VA-API are both (very) recent.
