From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 31613] New: UI Fonts in Blender are not visible with recent Mesa.
Date: Sat, 13 Nov 2010 22:32:31 -0800 (PST) [thread overview]
Message-ID: <bug-31613-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=31613
Summary: UI Fonts in Blender are not visible with recent Mesa.
Product: Mesa
Version: git
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: FJ.Whittle@gmail.com
All user interface text in Blender 2.55(alpha) and smooth fonts variations of
Blender 2.49 is rendered invisible by recent build of Mesa on the r600 gallium
driver.
Prerequisites: Mesa current git, any blender 2.55 alpha version including
latest svn
Steps to reproduce: Run blender
Expected outcome: Full user interface with fonts correctly rendered.
Actual outcome: No user interface text visible.
git bisect identifies
commit 63c3e3a3dc73f8a72e0d08ac4453df57bccdfdb9
Author: Keith Whitwell <keithw@vmware.com>
Date: Tue Nov 9 20:08:45 2010 +0000
r600: fix my pessimism about PIPE_TRANSFER_x flags
as the culprit. Rebasing to latest mesa git (master) with this commit reverted
works as expected.
--
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-11-14 6:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-14 6:32 bugzilla-daemon [this message]
2010-11-14 10:58 ` [Bug 31613] UI Fonts in Blender are not visible with recent Mesa bugzilla-daemon
2010-11-16 7:58 ` bugzilla-daemon
2010-11-22 19:43 ` bugzilla-daemon
2010-11-22 20:14 ` bugzilla-daemon
2010-11-22 23:16 ` 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-31613-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.