From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 72195] New: Sea in Crusader Kings II rendered in green colour with grey dots
Date: Sun, 01 Dec 2013 14:23:30 +0000 [thread overview]
Message-ID: <bug-72195-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1086 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=72195
Priority: medium
Bug ID: 72195
Assignee: dri-devel@lists.freedesktop.org
Summary: Sea in Crusader Kings II rendered in green colour with
grey dots
Severity: major
Classification: Unclassified
OS: Linux (All)
Reporter: pilarski777@gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: 9.2
Component: Drivers/DRI/R600
Product: Mesa
GLX version: 1.4
GLX extensions:
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD TURKS
OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.4
OpenGL core profile shading language version string: 1.40
OpenGL core profile context flags: (none)
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 9.2.4
OpenGL shading language version string: 1.30
My graphics card is AMD hd7670m, kernel 3.12, dpm on, running on Arch Linux.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2386 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:[~2013-12-01 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-01 14:23 bugzilla-daemon [this message]
2013-12-01 14:29 ` [Bug 72195] Sea in Crusader Kings II rendered in green colour with grey dots bugzilla-daemon
2013-12-01 15:31 ` bugzilla-daemon
2013-12-01 16:20 ` bugzilla-daemon
2013-12-02 18:51 ` 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-72195-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.