All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99078] Desktop icons oversaturated with red after December 11 2016 update
Date: Tue, 20 Dec 2016 23:15:11 +0000	[thread overview]
Message-ID: <bug-99078-502-gXTzNKUBnM@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99078-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 550 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=99078

--- Comment #12 from Furkan <falaca@gmail.com> ---
I'm experiencing a similar issue after updating to the same packages. I ran
some tests last night, with Michel's suggestions on IRC. The problem goes away
when I build Mesa against LLVM 3.8. So the bug was most likely introduced
between with the LLVM update, going from 3.9.0 to 3.9.1rc3. Hopefully I'll get
around to bisecting it to find the offending commit.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1357 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

  parent reply	other threads:[~2016-12-20 23:15 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-99078-502@http.bugs.freedesktop.org/>
2016-12-15  7:13 ` [Bug 99078] Desktop icons oversaturated with red after December 11 2016 update bugzilla-daemon
2016-12-15 10:01 ` bugzilla-daemon
2016-12-20 23:15 ` bugzilla-daemon [this message]
2016-12-21  2:51 ` bugzilla-daemon
2016-12-21  6:58 ` bugzilla-daemon
2016-12-21  7:00 ` bugzilla-daemon
2016-12-21 11:01 ` bugzilla-daemon
2016-12-21 22:23 ` bugzilla-daemon
2016-12-24  0:25 ` bugzilla-daemon
2016-12-28 21:25 ` bugzilla-daemon
2016-12-31 10:58 ` bugzilla-daemon
2017-01-09 23:11 ` bugzilla-daemon
2017-01-20 17:40 ` bugzilla-daemon
2017-01-20 20:28 ` bugzilla-daemon
2017-01-20 20:31 ` bugzilla-daemon
2017-01-21  0:28 ` bugzilla-daemon
2017-01-21  0:29 ` bugzilla-daemon
2017-01-21  4:29 ` bugzilla-daemon
2017-01-21  7:25 ` bugzilla-daemon
2017-01-23 14:24 ` bugzilla-daemon
2017-01-23 14:27 ` bugzilla-daemon
2017-01-23 14:44 ` bugzilla-daemon
2017-01-23 14:45 ` bugzilla-daemon
2017-01-23 15:03 ` bugzilla-daemon
2017-01-23 16:58 ` bugzilla-daemon
2017-01-24  1:15 ` bugzilla-daemon
2017-02-07  8:27 ` bugzilla-daemon
2017-02-07  9:00 ` bugzilla-daemon
2018-04-11  6:00 ` 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-99078-502-gXTzNKUBnM@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.