From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 85526] New: Screen corruptions in OpenGL reliant applications
Date: Mon, 27 Oct 2014 21:51:20 +0000 [thread overview]
Message-ID: <bug-85526-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2107 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=85526
Bug ID: 85526
Summary: Screen corruptions in OpenGL reliant applications
Product: Mesa
Version: unspecified
Hardware: x86 (IA32)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel@lists.freedesktop.org
Reporter: hamish@icculus.org
Created attachment 108536
--> https://bugs.freedesktop.org/attachment.cgi?id=108536&action=edit
Image corruptions in Chromium, Blood II: The Chosen through WINE, and Quake III
Arena
I have been having a very confusing problem with the version of Mesa packaged
with Arch Linux. I am using a Diamond Radeon HD 4670 with R600g.
Yesterday I updated the various Mesa packages from 10.3.1-1 to 10.3.2-1 and
upon doing so I started to encounter screen corruptions in all of the games I
tested as well as the browser Chromium.
Reverting to the previous version packaged by Arch Linux fixes the issue:
cd /var/cache/pacman/pkg/
pacman -U mesa-10.3.1-1-i686.pkg.tar.xz mesa-dri-10.3.1-1-i686.pkg.tar.xz
mesa-libgl-10.3.1-1-i686.pkg.tar.xz mesa-vdpau-10.3.1-1-i686.pkg.tar.xz
While the bug itself is of course distressing, the main thing that is confusing
me is that I am even having trouble finding mention of Mesa 10.3.2 release as
the website does not mention it and I can not even find an entry for Mesa 10.3
in the Version field of this very submission form.
Games seem to run without any stated errors in spite of the corruptions,
something which is making it difficult for me to find any additional
information. I have attached screenshots showing off some of the problems I am
talking about.
I apologize if this report is too vague or if I am missing something with
regards to the Mesa version information, but this is the best I can figure out
for the moment. Any suggestions as to deriving more useful information would of
course be appreciated.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3599 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2014-10-27 21:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 21:51 bugzilla-daemon [this message]
2014-10-27 21:53 ` [Bug 85526] Screen corruptions in OpenGL reliant applications bugzilla-daemon
2014-10-27 22:11 ` bugzilla-daemon
2014-10-27 22:19 ` bugzilla-daemon
2014-10-28 1:25 ` bugzilla-daemon
2014-10-28 1:30 ` bugzilla-daemon
2014-10-28 1:32 ` bugzilla-daemon
2014-10-28 1:37 ` bugzilla-daemon
2014-10-28 1:44 ` bugzilla-daemon
2014-10-28 2:26 ` bugzilla-daemon
2014-10-28 2:38 ` bugzilla-daemon
2014-10-28 2:49 ` bugzilla-daemon
2014-10-28 2:54 ` bugzilla-daemon
2014-10-28 3:04 ` bugzilla-daemon
2014-10-28 3:07 ` bugzilla-daemon
2014-10-28 3:17 ` bugzilla-daemon
2014-10-28 3:19 ` bugzilla-daemon
2014-10-28 3:27 ` bugzilla-daemon
2014-10-28 23:28 ` bugzilla-daemon
2014-10-29 2:08 ` 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-85526-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.