http://bugs.winehq.org/show_bug.cgi?id=18805
Summary: World of Warcraft crashes after Launcher using 1.1.23 Product: Wine Version: 1.1.23 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: matthewm@boedicker.org
Under 1.1.23, World of Warcraft crashes into Blizzard WowError after Play is clicked from the Launcher with the attached dump.
Switching to Wine 1.1.22 fixes the issue.
ATI Catalyst 9.5 driver Ubuntu 9.04 amd64
http://bugs.winehq.org/show_bug.cgi?id=18805
--- Comment #1 from Matthew M. Boedicker matthewm@boedicker.org 2009-06-05 23:43:08 --- Created an attachment (id=21591) --> (http://bugs.winehq.org/attachment.cgi?id=21591) WowError dump after crash
http://bugs.winehq.org/show_bug.cgi?id=18805
Matthew M. Boedicker matthewm@boedicker.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #21591|application/octet-stream |text/plain mime type| |
http://bugs.winehq.org/show_bug.cgi?id=18805
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #2 from joaopa jeremielapuree@yahoo.fr 2009-06-06 00:51:00 --- You must attach the backtrace given by wine, not this one given by the game debugger.
http://bugs.winehq.org/show_bug.cgi?id=18805
--- Comment #3 from Matthew M. Boedicker matthewm@boedicker.org 2009-06-06 01:11:01 --- Is some part of the output of this what you mean?
WINEDEBUG=+relay wine Launcher.exe > /tmp/wow_wine_out 2>&1
http://bugs.winehq.org/show_bug.cgi?id=18805
--- Comment #4 from joaopa jeremielapuree@yahoo.fr 2009-06-06 01:36:02 --- wine Launcher.exe > /tmp/wow_wine_out 2>&1 is enough to begin.
http://bugs.winehq.org/show_bug.cgi?id=18805
--- Comment #5 from Henri Verbeet hverbeet@gmail.com 2009-06-06 03:32:10 --- (In reply to comment #1)
The instruction at "0x7A9BFB02" referenced memory at "0x00000018". The memory could not be "read".
That's a duplicate of bug 18794, which is essentially a driver bug.
http://bugs.winehq.org/show_bug.cgi?id=18805
Ken Sharp kennybobs@o2.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |DUPLICATE
--- Comment #6 from Ken Sharp kennybobs@o2.co.uk 2009-06-06 05:03:50 --- Please search for duplicates, or look at the appdb before submitting a new bug.
*** This bug has been marked as a duplicate of bug 18794 ***
http://bugs.winehq.org/show_bug.cgi?id=18805
Ken Sharp kennybobs@o2.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #7 from Ken Sharp kennybobs@o2.co.uk 2009-06-06 05:05:45 --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=18805
--- Comment #8 from Matthew M. Boedicker matthewm@boedicker.org 2009-06-06 07:55:46 --- Is this the same issue even though I am using OpenGL and 18794 seems to be a problem with Direct3D?
http://bugs.winehq.org/show_bug.cgi?id=18805
--- Comment #9 from Henri Verbeet hverbeet@gmail.com 2009-06-06 10:39:15 --- (In reply to comment #8)
Is this the same issue even though I am using OpenGL and 18794 seems to be a problem with Direct3D?
I think so, yes. You can make a +d3d log to be sure, but going by the "Loaded Modules" from that log I think WoW will initialize d3d9 even when it isn't going to use it for rendering.
http://bugs.winehq.org/show_bug.cgi?id=18805
--- Comment #10 from Matthew M. Boedicker matthewm@boedicker.org 2009-06-06 11:19:03 --- Created an attachment (id=21606) --> (http://bugs.winehq.org/attachment.cgi?id=21606) output of wine Launcher.exe
http://bugs.winehq.org/show_bug.cgi?id=18805
--- Comment #11 from Matthew M. Boedicker matthewm@boedicker.org 2009-06-06 11:20:00 --- Created an attachment (id=21607) --> (http://bugs.winehq.org/attachment.cgi?id=21607) output of WINEDEBUG=+d3d wine Launcher.exe
http://bugs.winehq.org/show_bug.cgi?id=18805
--- Comment #12 from Henri Verbeet hverbeet@gmail.com 2009-06-06 11:37:05 --- Yeah, that's the same bug.