From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109370] [Runelite GPU plugin] Enabling GPU plugin produces incorrect rendering
Date: Tue, 15 Jan 2019 19:11:47 +0000 [thread overview]
Message-ID: <bug-109370-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 900 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=109370
Bug ID: 109370
Summary: [Runelite GPU plugin] Enabling GPU plugin produces
incorrect rendering
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: mika3hot@hotmail.com
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 143135
--> https://bugs.freedesktop.org/attachment.cgi?id=143135&action=edit
Garbled polygons and some missing texture with GPU plugin enabled
More info https://github.com/runelite/runelite/issues/6841
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2559 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-01-15 19:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 19:11 bugzilla-daemon [this message]
2019-01-15 19:18 ` [Bug 109370] [Runelite GPU plugin] Enabling GPU plugin produces incorrect rendering bugzilla-daemon
2019-01-16 14:47 ` bugzilla-daemon
2019-01-19 21:12 ` bugzilla-daemon
2019-01-21 23:07 ` bugzilla-daemon
2019-02-22 14:18 ` bugzilla-daemon
2019-02-22 18:32 ` bugzilla-daemon
2019-03-19 0:15 ` bugzilla-daemon
2019-09-25 18:48 ` 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-109370-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.