From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 90264] [Regression, bisected] Tooltip corruption in Chrome
Date: Wed, 10 Jun 2015 23:34:09 +0000 [thread overview]
Message-ID: <bug-90264-502-1YC0KoW600@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-90264-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1123 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=90264
Furkan <falaca@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |brianp@vmware.com
Component|Drivers/Gallium/radeonsi |Mesa core
Assignee|dri-devel@lists.freedesktop |mesa-dev@lists.freedesktop.
|.org |org
QA Contact|dri-devel@lists.freedesktop |mesa-dev@lists.freedesktop.
|.org |org
--- Comment #19 from Furkan <falaca@gmail.com> ---
I booted up a Haswell box from an Ubuntu 15.04 live USB, and was able to
reproduce the same glitch.
It looks like we can reproduce this on radeon, nouveau, and i965, but not
llvmpipe. What does that mean? I am re-classifying this under Mesa core for
now. Would it fit better under any other category?
Can anybody confirm that this issue isn't present with the Nvidia proprietary
driver?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2718 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2015-06-10 23:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 3:08 [Bug 90264] [Regression, bisected] Tooltip corruption in Chrome bugzilla-daemon
2015-05-01 3:12 ` bugzilla-daemon
2015-05-01 3:26 ` bugzilla-daemon
2015-05-01 3:37 ` bugzilla-daemon
2015-05-01 3:55 ` bugzilla-daemon
2015-05-01 4:01 ` bugzilla-daemon
2015-05-01 19:08 ` bugzilla-daemon
2015-05-01 22:16 ` bugzilla-daemon
2015-05-25 18:45 ` bugzilla-daemon
2015-06-10 12:34 ` bugzilla-daemon
2015-06-10 12:58 ` bugzilla-daemon
2015-06-10 17:33 ` bugzilla-daemon
2015-06-10 17:37 ` bugzilla-daemon
2015-06-10 19:09 ` bugzilla-daemon
2015-06-10 19:44 ` bugzilla-daemon
2015-06-10 19:57 ` bugzilla-daemon
2015-06-10 20:58 ` bugzilla-daemon
2015-06-10 21:12 ` bugzilla-daemon
2015-06-10 21:36 ` bugzilla-daemon
2015-06-10 23:34 ` bugzilla-daemon [this message]
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-90264-502-1YC0KoW600@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.