Summary: | Mouse Cursor is rendered too dark | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | utzu |
Component: | general | Assignee: | David Edmundson <kde> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | nate, nf.pereira, plasma-bugs |
Priority: | NOR | ||
Version: | master | ||
Target Milestone: | 1.0 | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
Screenshot of the cursor on the left, real hardware cursor on the right
For the record: This was the screenshot I took the example picture from |
Description
utzu
2021-05-30 07:21:20 UTC
Created attachment 138877 [details]
Screenshot of the cursor on the left, real hardware cursor on the right
Created attachment 138878 [details]
For the record: This was the screenshot I took the example picture from
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 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.
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. 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. You can just put it in the URL field. 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. |