From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100534] Mouse cursors have abnormally dark pixels around edges
Date: Sun, 02 Apr 2017 16:16:18 +0000 [thread overview]
Message-ID: <bug-100534-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1090 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100534
Bug ID: 100534
Summary: Mouse cursors have abnormally dark pixels around edges
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: libdrm
Assignee: dri-devel@lists.freedesktop.org
Reporter: vermette@gmail.com
Created attachment 130646
--> https://bugs.freedesktop.org/attachment.cgi?id=130646&action=edit
Samples as seen by placing the cursor next to the preview in KDE System
Settings.
Most visible when viewing cursors with a white or light outline on a white or
light background. Light pixels which are semitransparent will appear darkened,
even pixels with no significant gray value will appear much darker than they
should.
For testing cursor sets which illustrate this; KDE Breeze and El Capitan show
this effect extremely well.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2646 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2017-04-02 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-02 16:16 bugzilla-daemon [this message]
2017-04-03 14:55 ` [Bug 100534] Mouse cursors have abnormally dark pixels around edges bugzilla-daemon
2017-04-30 9:01 ` bugzilla-daemon
2017-04-30 9:09 ` bugzilla-daemon
2017-04-30 9:19 ` bugzilla-daemon
2017-05-01 8:50 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-100534-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.