From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 99400] [nouveau] garbled rendering with glamor on G71
Date: Mon, 20 Mar 2017 08:29:20 +0000 [thread overview]
Message-ID: <bug-99400-8800-3vxGeG2WvS@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99400-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 709 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99400
--- Comment #24 from Olivier Fourdan <fourdan-eaOCjQ5FDoY@public.gmane.org> ---
One possibility would be to run a live image of Fedora 25 (which comes with
Wayland by default), at least it would allow for a quick test (no need for you
to install everything if it's not reproducible on your hardware setup...)
However, gtk-demo (which is the simple way to reproduce) comes with the devel
packages, which won't be on a live image... But this should be installable,
even on a live image, as long as a network connection is available.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1484 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2017-03-20 8:29 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 15:21 [Bug 99400] New: [nouveau] garbled rending with glamor on G71 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-99400-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-01-13 15:26 ` [Bug 99400] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-13 15:26 ` [Bug 99400] [nouveau] garbled rendering " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-13 15:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-13 15:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-13 15:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-13 16:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-13 18:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-13 19:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-14 0:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-16 16:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-16 16:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-17 11:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-27 15:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-28 15:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-28 16:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-30 9:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-30 12:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-30 12:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-30 19:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-30 19:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-31 9:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-31 12:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-02-02 6:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-18 22:06 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-20 8:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2017-03-20 11:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-20 18:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-20 18:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-26 2:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-27 13:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-27 14:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-18 20:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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-99400-8800-3vxGeG2WvS@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.