SUMMARY Mouse cursor is pitch black in HDR mode since i upgraded to Mesa 25.0.1 (was needed for my 9070 XT) This does not happen in SDR mode. It does not matter which pointer style you choose for the mouse cursor, it is simply pitch black. STEPS TO REPRODUCE 1. Use Mesa 25.0.1 2. Switch from SDR to HDR in Kde 3. See mouse curosr is pitch black OBSERVED RESULT Mouse cursor is pitch black EXPECTED RESULT Mouse cursor looks like in SDR Mode SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 6.3.2 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.6-273-tkg-eevdf (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon Graphics ADDITIONAL INFORMATION This makes the mouse cursor very hard to use with dark themes or apps which have a black background. Tried to capture the pitch black mouse cursor with spectacle, but in the screenshot the mouse cursor has the white surrounding like it does on sdr mode ?!
Doesn't happen here, on a rx 7900XTX. This is definitely a driver bug, not sure if it's in Mesa or the display driver, but you can report it to Mesa and it'll be moved if necessary: https://gitlab.freedesktop.org/mesa/mesa/-/issues Until it's fixed, you can work around it by setting https://invent.kde.org/plasma/kwin/-/wikis/Environment-Variables#kwin_force_sw_cursor
(In reply to Zamundaaa from comment #1) > Doesn't happen here, on a rx 7900XTX. This is definitely a driver bug, not > sure if it's in Mesa or the display driver, but you can report it to Mesa > and it'll be moved if necessary: > https://gitlab.freedesktop.org/mesa/mesa/-/issues > > Until it's fixed, you can work around it by setting > https://invent.kde.org/plasma/kwin/-/wikis/Environment- > Variables#kwin_force_sw_cursor Hi, thx a lot, your mentioned workaround indeed helps. Also in the game menu in Dead Island 2 the mouse cursor is red again now instead of being black. I will open an mesa issue like you proposed. Br !
*** Bug 501417 has been marked as a duplicate of this bug. ***