[Bug 32058] New: Guild Wars 2 launcher freezes/hangs (unable to launch game)

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=32058

             Bug #: 32058
           Summary: Guild Wars 2 launcher freezes/hangs (unable to launch
                    game)
           Product: Wine
           Version: 1.5.15
          Platform: x86-64
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
        AssignedTo: wine-bugs at winehq.org
        ReportedBy: x.egam.wodahs.x at gmail.com
                CC: julliard at winehq.org
    Classification: Unclassified


Once I updated wine to version 1.5.15, the Guild Wars 2 launcher can no longer
launch the game because it just freezes/hangs. This was not an issue in 1.5.14,
and in order to run the game for now I'm using wine 1.5.14 compiled from
source.

In wine 1.5.14, the launcher is black (can't see UI at all, but it's still
functional) unless using the -dx9single flag. Using -dx9single, the background
is black instead of transparent but the UI inside is properly rendered. This
information is important because, before submitting this bug report, I
performed two separate git bisects between 1.5.14 and 1.5.15: one without any
command-line parameters, and one using -dx9single.

Technical details follow:

=======================================================================

1) git bisect for running the game without any parameters:
In the last good commit (8dcbeff760115834656f3f1fc85922e3a9af14d0), the
launcher is still black but it still works. You cannot see the UI but by
blindly logging in, the game does launch. In the first bad commit
(f12c1c6630f0bf842dde9af10da4ab188ff16e94), the behavior is different from the
wine 1.5.15 release and the other commits tested: here, instead of locking up,
the window just disappears. It's still there, but I guess it's fully
transparent. Because this leaves us even more "blind", I considered this "bad"
in the git bisect, yielding the following result:

---
f12c1c6630f0bf842dde9af10da4ab188ff16e94 is the first bad commit
commit f12c1c6630f0bf842dde9af10da4ab188ff16e94
Author: Alexandre Julliard <julliard at winehq.org>
Date:   Wed Sep 26 13:12:17 2012 +0200

    winex11: Switch to an ARGB visual for layered windows with per-pixel alpha.

:040000 040000 e9933c28f3e50c52d2cee37a43b06a2f5cb5a497
3870099a31a68a69cd7c022857794700c2343aa9 M    dlls
---

If, however, we consider f12c1c6630f0bf842dde9af10da4ab188ff16e94 "good" in the
git bisect, we get:

---
d8247efd5ecb8c4604624eb2bbf47e194ce59e7e is the first bad commit
commit d8247efd5ecb8c4604624eb2bbf47e194ce59e7e
Author: Alexandre Julliard <julliard at winehq.org>
Date:   Thu Sep 27 20:47:08 2012 +0200

    winex11: Take the alpha channel into account to compute the region of
layered windows.

:040000 040000 3870099a31a68a69cd7c022857794700c2343aa9
d9ec62b63405f910db90b095145a7910cc124eef M    dlls
---

In this case, the launcher does indeed lock up in the first bad commit
(d8247efd5ecb8c4604624eb2bbf47e194ce59e7e).


2) git bisect for running the game using -dx9single:
Using the -dx9single flag, we seem to be able to get to a later commit before
it stops working (but does not work in the 1.5.15 release). In the last good
commit (dbff4f422c943a837f0098e921f831eb4a94ac11), everything seems to be fine
(when using the -dx9single flag) and even the transparency seems to be working.
However, in the first bad commit (6f3b097a203d9ca248732cb45eed462599ca3af1),
things start to lock up. This yields the following git bisect result:

---
6f3b097a203d9ca248732cb45eed462599ca3af1 is the first bad commit
commit 6f3b097a203d9ca248732cb45eed462599ca3af1
Author: Alexandre Julliard <julliard at winehq.org>
Date:   Wed Oct 3 00:09:01 2012 +0200

    winex11: Fix a typo in the surface region computation with an alpha
channel.

:040000 040000 fa11ac3c80763b81911ba999d8302029d2c6d147
566c9c06b11f8785c870a1e09ec53d42e13d1524 M    dlls
---

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.