From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106355] Strange artifacts when using Chromium with hardware acceleration
Date: Mon, 07 May 2018 10:28:38 +0000 [thread overview]
Message-ID: <bug-106355-502-V3WXD6RSAS@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106355-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 533 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106355
--- Comment #5 from Timothy Arceri <t_arceri@yahoo.com.au> ---
(In reply to Norbert Klar from comment #4)
> Care to tell me what's going on? 'Cause if it's duplicate of that bug, then
> it wasn't fixed since then.
No it's not fixed which is why the other bug is still open. It can take a while
for these type of bugs are resolved. I'm not aware of anyone currently looking
into the problem.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1484 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 prev parent reply other threads:[~2018-05-07 10:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-106355-502@http.bugs.freedesktop.org/>
2018-05-02 14:48 ` [Bug 106355] Strange artifacts when using Chromium with hardware acceleration bugzilla-daemon
2018-05-02 15:07 ` bugzilla-daemon
2018-05-02 15:09 ` bugzilla-daemon
2018-05-02 23:31 ` bugzilla-daemon
2018-05-03 5:48 ` bugzilla-daemon
2018-05-07 10:28 ` bugzilla-daemon [this message]
2018-07-08 15:26 ` 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-106355-502-V3WXD6RSAS@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).