Bug 454660 - Cursor has wrong contrast
Summary: Cursor has wrong contrast
Status: RESOLVED UPSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 5.24.5
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-05-31 12:59 UTC by Akseli Lahtinen
Modified: 2022-06-04 15:09 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Photo of screen. The cursor is darker than in the preview image. (499.29 KB, image/png)
2022-05-31 12:59 UTC, Akseli Lahtinen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Akseli Lahtinen 2022-05-31 12:59:31 UTC
Created attachment 149358 [details]
Photo of screen. The cursor is darker than in the preview image.

SUMMARY
Mouse cursor has weird contrast both on X11 and Wayland.
I have no idea when this started exactly, I think I was installing bunch of KDE frameworks to build something and after reboot it just changed.

I had to take an actual photo to show it. If I try to take a screenshot of it, the mouse resets to normal color during screenshot (Using spectacle).

STEPS TO REPRODUCE
Unfortunately I do not know what started this.

1. Change cursor look
2. Cursor has darker contrast than it should

OBSERVED RESULT
Cursor is darker than it should be.

EXPECTED RESULT
Cursor looks like it does in the preview.

SOFTWARE/OS VERSIONS

Operating System: Fedora Linux 36
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3
Kernel Version: 5.17.11-300.fc36.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 15,6 GiB of RAM
Graphics Processor: AMD DIMGREY_CAVEFISH

ADDITIONAL INFORMATION
-
Comment 1 Zamundaaa 2022-06-04 08:40:00 UTC
This is a driver bug: https://gitlab.freedesktop.org/drm/amd/-/issues/1513
Comment 2 Akseli Lahtinen 2022-06-04 15:09:01 UTC
(In reply to Zamundaaa from comment #1)
> This is a driver bug: https://gitlab.freedesktop.org/drm/amd/-/issues/1513

Thank you, reported it there