From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 26076] New: Transparent GNOME panel corruption on R600 KMS
Date: Sat, 16 Jan 2010 06:26:05 -0800 (PST) [thread overview]
Message-ID: <bug-26076-502@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=26076
Summary: Transparent GNOME panel corruption on R600 KMS
Product: DRI
Version: DRI CVS
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: minor
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.sourceforge.net
ReportedBy: pseudomatty@mailinator.com
R600, using today's git HEAD of x.org, DRI, radeon etc on kernel 2.6.33rc4-git2
with KMS enabled.
The areas of my GNOME panel which are normally transparent are drawn mostly
black, with small amounts of apparently random garbage in them.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
--
next reply other threads:[~2010-01-16 14:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-16 14:26 bugzilla-daemon [this message]
2010-01-16 14:30 ` [Bug 26076] Transparent GNOME panel corruption on R600 KMS bugzilla-daemon
2010-01-16 17:27 ` bugzilla-daemon
2010-01-16 23:46 ` bugzilla-daemon
2010-01-17 0:24 ` bugzilla-daemon
2010-01-17 0:28 ` bugzilla-daemon
2010-01-17 0:28 ` 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-26076-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.sourceforge.net \
/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.