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 91526] New: World of Warcraft (on Wine) has UI corruption with nouveau
Date: Sat, 01 Aug 2015 19:27:28 +0000	[thread overview]
Message-ID: <bug-91526-8800@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 91526
           Summary: World of Warcraft (on Wine) has UI corruption with
                    nouveau
           Product: Mesa
           Version: git
          Hardware: Other
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/nouveau
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
          Reporter: gediminas-1NU85dn7e2ownf/OCUKchA@public.gmane.org
        QA Contact: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org

Created attachment 117482
  --> https://bugs.freedesktop.org/attachment.cgi?id=117482&action=edit
example of UI corruption

When I run World of Warcraft under Wine with Nouveau, the game has UI
corruption ranging from very mild (e.g. bits of text garbled here and there) to
severe (complete lack of UI whatsoever).
I recorded an apitrace trace[2] and when replaying on Nouveau, the corruptions
still do happen, complete with variations[1]. The same trace replayed on LLVM
(i.e. with LIBGL_ALWAYS_SOFTWARE=1) results with the UI being rendered 100%
fine.
Running on the binary blob also does result in the UI being rendered 100% fine.

I tested with two WoW versions: the [at the time of writing] latest 6.20 and an
old 3.3.5a client – both have the same kind of corruptions.

Do note that in some cases, the initial game "login screen" appears to look
perfectly fine; until one tries to e.g. enter one's login credentials or open
the settings menu. So in order to tell if there are corruptions or not, simply
launching the game might not be enough.

[1] the corruptions seem to be consistent between runs (on both actual game and
trace replay) as long as I don't change anything window-wise. e.g. opening a
some program or moving some random window around results in different
corruptions each time while not touching anything and just re-starting the game
(or replay) results in very consistent corruptions.
I also noticed that when it comes to typed-in text (e.g. field to enter the
account name), the typed in letters seem to most of the time contain bits from
other portions of the screen outside of game's window.

[2] https://seriouss.am/wow-nouveau-2015-08-01T2052.trace.xz filesize: 20.4MiB

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

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

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

             reply	other threads:[~2015-08-01 19:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-01 19:27 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-91526-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2015-08-01 19:30   ` [Bug 91526] World of Warcraft (on Wine) has UI corruption with nouveau bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-08-01 19:38   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-08-01 19:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-08-01 20:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-08-01 20:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-09-09 22:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-09-10  1:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-30 15:50   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-02-04 17:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-03-25  7:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-03-25 23:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-03-25 23:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-03-27  2:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-03-28 12:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-03-28 12:41   ` 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-91526-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.