https://bugs.winehq.org/show_bug.cgi?id=45443
Bug ID: 45443 Summary: Diablo 3: Starting the game causes a black screen softlock on the X-environment Product: Wine Version: 3.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: sworddragon2@aol.com Distribution: ---
Created attachment 61776 --> https://bugs.winehq.org/attachment.cgi?id=61776 Terminal output
On starting Diablo 3 I usually see a gray fullscreen before the game loads its ingame-login screen. But with Wine 3.12 it stops at the gray screen (which turns black if switched to the console and back). There are a few symptoms:
- Terminating all applications in Wine does not prevent the black screen to go away or Wine to exit. - The winedevices.exe does not respond to a SIGTERM and needs to be terminated with a SIGKILL. - Wine still refuses to exit automatically even if only the wineserver64 remains. - After terminating all processes and switching from the console to the X-environment again the screen is still black (not sure if this is caused by Wine or if this is a bug in the X-Server).
In the attachments is the terminal output which I had to log to disk (the game was started via "sworddragon@ubuntu:/wine/drive_c/Program Files (x86)/Diablo III$ setarch i386 -3 './Diablo III.exe' -launch -opengl").
https://bugs.winehq.org/show_bug.cgi?id=45443
--- Comment #1 from sworddragon2@aol.com --- Edit: "prevent" should be "cause" in the previous comment.
https://bugs.winehq.org/show_bug.cgi?id=45443
Maciej Stanczew maciej.stanczew+b@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |maciej.stanczew+b@gmail.com
--- Comment #2 from Maciej Stanczew maciej.stanczew+b@gmail.com --- This could be related to bug #44585, as the message is similar ("setup_exception_record stack overflow"). I attached logs from Wine 3.11, Wine 3.12 and Wine Staging 3.12. One log that is present in Vanilla but not in Staging is "EnumDisplayDevicesW" stub -- maybe it's related to this bug.
https://bugs.winehq.org/show_bug.cgi?id=45443
--- Comment #3 from Maciej Stanczew maciej.stanczew+b@gmail.com --- Created attachment 61780 --> https://bugs.winehq.org/attachment.cgi?id=61780 Wine 3.11 -- not launching at all
https://bugs.winehq.org/show_bug.cgi?id=45443
--- Comment #4 from Maciej Stanczew maciej.stanczew+b@gmail.com --- Created attachment 61781 --> https://bugs.winehq.org/attachment.cgi?id=61781 Wine 3.12 -- hanging on grey screen
https://bugs.winehq.org/show_bug.cgi?id=45443
--- Comment #5 from Maciej Stanczew maciej.stanczew+b@gmail.com --- Created attachment 61782 --> https://bugs.winehq.org/attachment.cgi?id=61782 Wine Staging 3.12 -- everything loading and working correctly
https://bugs.winehq.org/show_bug.cgi?id=45443
--- Comment #6 from Maciej Stanczew maciej.stanczew+b@gmail.com --- I compiled vanilla Wine with gdi32-MultiMonitor patch, and this bug still reproduces in the same form -- so it's not related to EnumDisplayDevicesW.
https://bugs.winehq.org/show_bug.cgi?id=45443
Krack krack3rz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |krack3rz@gmail.com
--- Comment #7 from Krack krack3rz@gmail.com --- The issue persists in wine-3.15. I installed Diablo-III on my ArchLinux today into a vanilla 32bit prefix. I only installed fonts since it wouldn't work without them.
https://bugs.winehq.org/show_bug.cgi?id=45443
Acridwax acridwax@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |acridwax@gmail.com
--- Comment #8 from Acridwax acridwax@gmail.com --- With WINE 4.0-staging this bug does not appear.
https://bugs.winehq.org/show_bug.cgi?id=45443
--- Comment #9 from Maciej Stanczew maciej.stanczew+b@gmail.com --- Still happening with vanilla Wine 4.3. Works without problems on Staging.
https://bugs.winehq.org/show_bug.cgi?id=45443
--- Comment #10 from Acridwax acridwax@gmail.com --- (In reply to Maciej Stanczew from comment #9)
Still happening with vanilla Wine 4.3. Works without problems on Staging.
Confirming that this is indeed still true. Works in 4.4 staging but any non-staging WINE still has this bug.
https://bugs.winehq.org/show_bug.cgi?id=45443
--- Comment #11 from Maciej Stanczew maciej.stanczew+b@gmail.com --- It looks like reproduction changed (?). On Wine 5.10 and 5.11 I can successfully launch 32-bit Diablo III client. But 64-bit doesn't launch, it hits "seh:setup_exception stack overflow" and exits.
The message is similar to bug #49436, but it's probably a separate issue; 49436 appeared in 5.11, whereas here we get the error even on 5.10, plus behavior is different (hang vs exit).
https://bugs.winehq.org/show_bug.cgi?id=45443
--- Comment #12 from Maciej Stanczew maciej.stanczew+b@gmail.com --- Created attachment 67528 --> https://bugs.winehq.org/attachment.cgi?id=67528 64-bit client on Wine 5.11 - doesn't work
https://bugs.winehq.org/show_bug.cgi?id=45443
--- Comment #13 from Maciej Stanczew maciej.stanczew+b@gmail.com --- Created attachment 67529 --> https://bugs.winehq.org/attachment.cgi?id=67529 32-bit client on Wine 5.11 - works
https://bugs.winehq.org/show_bug.cgi?id=45443
--- Comment #14 from Maciej Stanczew maciej.stanczew+b@gmail.com --- About the original issue, X softlock on 32-bit client: for me it's fixed as of Wine 5.9. With 5.8 I get a softlock with the last log being "0128:fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0EF6FF1C): stub" and with 5.9 I'm able to successfully launch the game.
Situation with 64-bit client is more complicated, but I think it should be treated as a separate issue (or: issues). I'll be posting any relevant info in bug #49436.
https://bugs.winehq.org/show_bug.cgi?id=45443
--- Comment #15 from Maciej Stanczew maciej.stanczew+b@gmail.com --- I'm able to start 64-bit game client using Wine 6.12 (non-Staging). With 6.11 I was getting a blank screen and a lot of wined3d_deferred_context_map logs, probably pointing to bug #42191 (which was fixed in 6.12).
Performance is still very bad (7-8 fps in game, 17 fps in menu), but the game doesn't lock/crash, so I think this bug should be treated as either fixed or no longer reproducible.
https://bugs.winehq.org/show_bug.cgi?id=45443
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #16 from joaopa jeremielapuree@yahoo.fr --- Reported fixed by the last comment. Can an administrator close this bug as FIXED?
https://bugs.winehq.org/show_bug.cgi?id=45443
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED
--- Comment #17 from Austin English austinenglish@gmail.com --- (In reply to Maciej Stanczew from comment #15)
I'm able to start 64-bit game client using Wine 6.12 (non-Staging). With 6.11 I was getting a blank screen and a lot of wined3d_deferred_context_map logs, probably pointing to bug #42191 (which was fixed in 6.12).
Performance is still very bad (7-8 fps in game, 17 fps in menu), but the game doesn't lock/crash, so I think this bug should be treated as either fixed or no longer reproducible.
Fixed.
https://bugs.winehq.org/show_bug.cgi?id=45443
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #18 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 6.22.