We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running ENABLE_HDR_WSI=1 mpv --no-config --vo=gpu-next --gpu-context=waylandvk <file> on kwin 6.3.2
ENABLE_HDR_WSI=1 mpv --no-config --vo=gpu-next --gpu-context=waylandvk <file>
[HDR Layer] Creating swapchain for id: 5 - format: VK_FORMAT_R16G16B16A16_UNORM - colorspace: VK_COLOR_SPACE_PASS_THROUGH_EXT [HDR Layer] Unknown color space, assuming untaggedwp_color_manager_v1#47: error 1: there's already a color management surface for this wl_surface [vo/gpu-next/wayland] Error occurred on the display fd V: 00:00:00 / 00:23:41 (0%) Exiting... (Quit) warning: queue "mesa vk display queue" 0x7584d8001be0 destroyed while proxies still attached: wp_image_description_v1#88 still attached
It persists even after rebooting.
The text was updated successfully, but these errors were encountered:
If you're using new enough Mesa, you don't have to, and shouldn't use the Vulkan layer anymore
Sorry, something went wrong.
7c0553d
No branches or pull requests
Running
ENABLE_HDR_WSI=1 mpv --no-config --vo=gpu-next --gpu-context=waylandvk <file>
on kwin 6.3.2It persists even after rebooting.
The text was updated successfully, but these errors were encountered: