From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 71887] Garbled output when rendering to a framebuffer object
Date: Tue, 24 Dec 2013 19:47:01 +0000 [thread overview]
Message-ID: <bug-71887-502-vJ2rfqWqUP@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-71887-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 728 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=71887
Victor Luchits <vluchits@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |NOTABUG
--- Comment #8 from Victor Luchits <vluchits@gmail.com> ---
Turns out the issue was related to how glGenRenderbuffersEXT generated id
numbers for framebuffers. Apparently some kernel change affected the outcome
and in combination with bug in the game code caused the reported issue.
Resolving as NOTABUG.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2209 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
prev parent reply other threads:[~2013-12-24 19:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 19:07 [Bug 71887] New: Garbled output when rendering to a framebuffer object bugzilla-daemon
2013-11-21 19:07 ` [Bug 71887] " bugzilla-daemon
2013-11-21 19:08 ` bugzilla-daemon
2013-11-21 19:08 ` bugzilla-daemon
2013-11-21 20:01 ` bugzilla-daemon
2013-11-22 7:09 ` bugzilla-daemon
2013-11-22 7:27 ` bugzilla-daemon
2013-11-22 7:36 ` bugzilla-daemon
2013-11-22 7:38 ` bugzilla-daemon
2013-11-23 10:22 ` bugzilla-daemon
2013-12-24 19:47 ` bugzilla-daemon [this message]
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-71887-502-vJ2rfqWqUP@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).