https://bugs.kde.org/show_bug.cgi?id=486391
Bug ID: 486391
Summary: QMplay2 crashes when using Vaapi on Wayland
Classification: Plasma
Product: kwin
Version: master
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: m...@fireburn.co.uk
Target Milestone: ---
This is using Plasma 6.1 git, KF6 git, Mesa git and QMplay2 from git
QMPlay2
libva info: VA-API version 1.21.0
libva info: Trying to open /usr/lib64/va/drivers/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_21
libva info: va_openDriver() returns 0
VA-API :: Initialized device: renderD129
wp_linux_drm_syncobj_surface_v1@107: error 4: explicit sync is used, but no
acquire point is set
[01 May 2024 11:04:45.448] The Wayland connection experienced a fatal error:
Protocol error
This appears to be triggered by the landing of
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/28874
The error message about the no acquire point I think is from the much older
https://invent.kde.org/plasma/kwin/-/merge_requests/4693
I'm raising a bug with the Mesa folk too, but I'm not 100% sure if this is a
Mesa, Kwin or QMplay2 bug
--
You are receiving this mail because:
You are watching all bug changes.
