https://bugs.kde.org/show_bug.cgi?id=500019
Harald Weissmueller <rro...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rro...@gmail.com
--- Comment #8 from Harald Weissmueller <rro...@gmail.com> ---
(In reply to Zamundaaa from comment #7)
> Git commit b97e1a374aa10e528fe361fd87a5df76b5e2017d by Xaver Hugl.
> Committed on 30/04/2025 at 16:04.
> Pushed by zamundaaa into branch 'Plasma/6.3'.
>
> core/colorpipeline: optimize out black point compensation
> (cherry picked from commit faac87b9642c47a2afe0228216c0ef9063c138eb)
>
> M +14 -0 autotests/test_colorspaces.cpp
> M +28 -0 src/core/colorpipeline.cpp
>
> https://invent.kde.org/plasma/kwin/-/commit/
> b97e1a374aa10e528fe361fd87a5df76b5e2017d
Is there something else required besides using a kwin with this patch? I tried
the Plasma/6.3 branch here and direct scanout doesn't seem to work with an ICC
profile or the "built-in" setting. It only works with color profile set to
"none". I'm using AMD graphics.
Something else I happened to notice because there's a bug with regards to
hardware cursor gamma right now on AMD RDNA 4: kwin seems to switch to a
software cursor in fullscreen windows (maybe only with VRR enabled?). The use
of a software cursor then also seems to break direct scanout. I tried
experimenting with environment variables and setting
KWIN_DRM_DONT_FORCE_AMD_SW_CURSOR=1 keeps the hardware cursor enabled for
fullscreen.
--
You are receiving this mail because:
You are watching all bug changes.
