Bug 437847 - Mouse Cursor is rendered too dark
Summary: Mouse Cursor is rendered too dark
Status: RESOLVED UPSTREAM
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: master
Platform: Debian testing Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-30 07:21 UTC by utzu
Modified: 2022-03-09 19:54 UTC (History)
3 users (show)

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


Attachments
Screenshot of the cursor on the left, real hardware cursor on the right (389.90 KB, image/png)
2021-05-30 08:30 UTC, utzu
Details
For the record: This was the screenshot I took the example picture from (2.93 KB, image/png)
2021-05-30 08:33 UTC, utzu
Details

Note You need to log in before you can comment on or make changes to this bug.
Description utzu 2021-05-30 07:21:20 UTC
Mouse Cursor is rendered too dark.
black is rendered black (ok)
gray is rendered black (wrong)
white is rendered white (ok)

x11 session
Might be related to amdgpu

One more thing to note: When creating a screenshot of the cursor, the error does not occur. Only the real hardware cursor is affected.

STEPS TO REPRODUCE
1. Use mouse cursor from Breeze Theme (or any other mouse cursor with grey body)
2. Make a screenshot of your mouse cursor
3. Put the real mouse cursor aside
4. See that the screenshot cursor is rendered grey (correct) while the real mouse cursor is rendered black (wrong).

SOFTWARE/OS VERSIONS
Windows: nah
macOS: ney
Linux/KDE Plasma: Debian Testing (= Debian 11)
(available in About System)
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.12.2

ADDITIONAL INFORMATION
I don't know if plasma is the right package to report against. Please move as appropriate.
Comment 1 utzu 2021-05-30 08:30:23 UTC
Created attachment 138877 [details]
Screenshot of the cursor on the left, real hardware cursor on the right
Comment 2 utzu 2021-05-30 08:33:58 UTC
Created attachment 138878 [details]
For the record: This was the screenshot I took the example picture from
Comment 3 Nate Graham 2021-06-08 20:50:45 UTC
If the screenshot looks right, this is an issue related to monitor/gamma calibration or graphics drivers. You would want to look here for next steps: https://docs.mesa3d.org/bugs.html
Comment 4 utzu 2021-06-09 20:04:31 UTC
Thanks for looking into this but no, this is definitely not a monitor/gamma calibration problem. I did not edit the picture in Attachment 1 [details]. This is one picture, no cutting, nothing. If it was monitor gamma or so then the whole picture would be affected and not just one of the two mouse cursors. It does not matter if I put the real mouse cursor to the right, to the left, above or below the screenshot cursor, the problem stays the same.
I hope this describes it better.
Comment 5 Nate Graham 2021-06-10 15:18:06 UTC
Hmm, in that case it's either a graphics driver issue, or an X issue. On X11, no KDE code is involved in drawing the cursor at all.
Comment 6 utzu 2021-06-10 18:27:17 UTC
I have reported this bug to mesa now:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/4905

btw: I get this error when trying to put that URL in this bug:
 https://gitlab.freedesktop.org/mesa/mesa/-/issues/4905 is not a valid URL to a bug. See Also URLs should point to one of:

    show_bug.cgi in a Bugzilla installation.
    A bug on launchpad.net
    An issue on code.google.com.
    A bug on bugs.debian.org.
    An issue in a JIRA installation.
    A ticket in a Trac installation.
    A bug in a MantisBT installation.
    A bug on sourceforge.net.
    An issue/pull request on github.com.
Comment 7 Nate Graham 2021-06-10 18:28:18 UTC
You can just put it in the URL field.
Comment 8 nf.pereira 2022-03-09 19:54:45 UTC
Xaver posted a workaround for this issue here:
https://gitlab.freedesktop.org/drm/amd/-/issues/1513#note_1290481

Basically, using KWIN_DRM_NO_AMS=1, for example in /etc/environment, forces the legacy driver API to be used, which fixes this problem.

A real fix will need to come from the amdgpu drivers though.