Open SeeleVolleri opened 3 weeks ago
This is unfortunately a side effect of how libva driver versioning works. The version of libva.so must be >= the version of the VA drivers. We use the latest libva version at the time of each Moonlight release, but it will break when your distro's VA drivers are updated to build against a newer libva than Moonlight was.
I recommend avoiding the AppImages if you're on bleeding edge distros, and instead use the Flatpak (which includes compatible libva and VA drivers in the runtime) or another package format that is specific to your distro (like AUR for Arch).
Describe the bug Moonlight unable to call
va_openDriver
when Host machine has a different versionlibva
andintel-media-va-driver
ori965-va-driver-shaders
. tldr: failed to use hardware decodeSteps to reproduce 1, download latest release moonlight-qt AppImage 2, update host
libva
andintel-media-va-driver
and/ori965-va-driver-shaders
3, start streaming and observed a warning shows unable to use hardware decodeOther Moonlight clients
Moonlight settings (please complete the following information)
Client PC details (please complete the following information)
Server PC details (please complete the following information)
Moonlight Logs (please attach)
Moonlight-###.log
files can be found in%TEMP%
. Simply type that into the File Explorer path field to navigate there.Moonlight-###.log
files can be found in/tmp
. In Finder, press Cmd+Shift+G, then type/tmp
to navigate there.flatpak run com.moonlight_stream.Moonlight
moonlight
Additional context Anything else you think may be relevant to the issue