From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 31250] New: Unigine Sanctuary v2.2: menus are broken
Date: Sun, 31 Oct 2010 01:45:18 -0700 (PDT) [thread overview]
Message-ID: <bug-31250-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=31250
Summary: Unigine Sanctuary v2.2: menus are broken
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r300
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: drakkk@centrum.cz
Created an attachment (id=39918)
--> (https://bugs.freedesktop.org/attachment.cgi?id=39918)
broken menu
Menus are broken hard in Unigine Sanctuary v2.2. Background rendering is all
black and there is corruption all over the screen, only some text is rendered
correctly. I did try different debug options and I did found out it works fine
with RADEON_NO_TCL=1 set.
This is with RV530, mesa: a15cf3cd0b21d593033a3abd2b1788de292001bd and 2.6.36
kernel. This problem was already mentioned in bug 28294, however that bug was
getting really long and main problem there is fixed.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2010-10-31 8:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-31 8:45 bugzilla-daemon [this message]
2010-10-31 8:45 ` [Bug 31250] Unigine Sanctuary v2.2: menus are broken bugzilla-daemon
2010-11-01 19:01 ` bugzilla-daemon
2010-11-01 22:06 ` bugzilla-daemon
2011-01-05 10:54 ` [Bug 31250] Unigine Sanctuary: " bugzilla-daemon
2011-02-11 2:02 ` bugzilla-daemon
2011-02-11 8:48 ` 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-31250-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.