All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 34708] New: running piglit on r600 causes gkrellm to lose text color
Date: Fri, 25 Feb 2011 03:31:46 -0800 (PST)	[thread overview]
Message-ID: <bug-34708-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: running piglit on r600 causes gkrellm to lose text
                    color
           Product: Mesa
           Version: 7.10
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r600
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: hramrach@gmail.com


Created an attachment (id=43790)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=43790)
screenshot of part of the gkrellm window

After running some 3d apps (eg. piglit) parts of gkrellm lose text color.
Firefox does not seem affected, nor are terminals.

While taking the screenshot the Lock and Shoot buttons which were previously OK
lost color while they were redrawn.

As all the text that loses color is the value text (as opposed to the label
text) it looks like any newly drawn text is not colored (black).

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2011-02-25 11:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-25 11:31 bugzilla-daemon [this message]
2014-01-15 14:54 ` [Bug 34708] running piglit on r600 causes gkrellm to lose text color bugzilla-daemon
2019-09-18 18:58 ` 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-34708-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.