All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 99400] New: [nouveau] garbled rending with glamor on G71
Date: Fri, 13 Jan 2017 15:21:00 +0000	[thread overview]
Message-ID: <bug-99400-8800@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2343 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=99400

            Bug ID: 99400
           Summary: [nouveau] garbled rending with glamor on G71
           Product: Mesa
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/nouveau
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
          Reporter: fourdan-eaOCjQ5FDoY@public.gmane.org
        QA Contact: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org

Created attachment 128933
  --> https://bugs.freedesktop.org/attachment.cgi?id=128933&action=edit
Screenshot of the issue

Description:

While investigating rendering bugs on Xwayland with nouveau specifically ([1]
and [2]) I realized that some gtk2 output (this Xwayland) is completely
garbled.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1411447
[2] https://bugzilla.gnome.org/show_bug.cgi?id=776255

How reproducible:

Always

Steps to reproduce:

1. Log in a Wayland session (either Weston or GNOME shell) on a Dell M1710 with
a GeForce Go 7950 GTX 
2. Run gtk-demo (the one from gtk2, i.e. not Wayland native but relying on
Xwayland)
3. Start the "Assistant" demo (second starting from the top)

Actual result:

The window is black with random content

Expected result:

The rendering is correct

Additional data:

This issue does not occur when using "shm" and CPU rendering instead of glamor
in Xwayland.

I am not aware of any other hardware where glamor produces such garbled output,
so I suspect an issue with nouveau, but if you reckon it's an issue with glamor
instead, please flip this bug back to xserver/glamor

I have seen other issue with black icons being reported with glamor and nouveau
as well and these do not occur when using the CPU render in weston for example
(https://bugzilla.redhat.com/show_bug.cgi?id=1411447#c12)

In my case, hardware is VGA compatible controller: NVIDIA Corporation G71M
[GeForce Go 7950 GTX] (rev a1) (prog-if 00 [VGA controller])

01:00.0 0300: 10de:0297 (rev a1) (prog-if 00 [VGA controller])
        Subsystem: 1028:019b

-- 
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: 4013 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

             reply	other threads:[~2017-01-13 15:21 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-13 15:21 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-99400-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-01-13 15:26   ` [Bug 99400] [nouveau] garbled rending with glamor on G71 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
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@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.