From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 35622] New: [i915g] 6358e6371b31671acbfa7c00336673f62ee928c5 result in a black screen in the main menu of portal in wine
Date: Thu, 24 Mar 2011 06:03:39 -0700 (PDT) [thread overview]
Message-ID: <bug-35622-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=35622
Summary: [i915g] 6358e6371b31671acbfa7c00336673f62ee928c5
result in a black screen in the main menu of portal in
wine
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/i915g
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: cme3000@gmail.com
Created an attachment (id=44781)
--> (https://bugs.freedesktop.org/attachment.cgi?id=44781)
batchbuffer dumps of portal
Commit 6358e6371b31671acbfa7c00336673f62ee928c5 breaks portal in wine. If you
start it with -console -novid it fails to render the main menu (it's just
black).
With I915_USE_BLITTER=yes it's rendered correctly again.
In the portal_batchbuffer.tar.gz is the dump of 'I915_DUMP_RAW_FILE=',
good.batchbuffer with I915_USE_BLITTER=yes and bad.batchbuffer without.
--
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:[~2011-03-24 13:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 13:03 bugzilla-daemon [this message]
2011-03-26 20:48 ` [Bug 35622] [i915g] 6358e6371b31671acbfa7c00336673f62ee928c5 result in a black screen in the main menu of portal in wine bugzilla-daemon
2011-03-26 20:48 ` [Bug 35622] [i945gme] " bugzilla-daemon
2011-03-28 20:43 ` bugzilla-daemon
2011-09-25 13:02 ` bugzilla-daemon
2011-09-25 14:32 ` bugzilla-daemon
2011-09-25 14:49 ` bugzilla-daemon
2012-06-10 14:37 ` 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-35622-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.