https://bugs.winehq.org/show_bug.cgi?id=49798
Bug ID: 49798 Summary: StarCraft 2 hangs on startup since 5.12 Product: Wine Version: 5.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: kolAflash@kolahilft.de Distribution: ---
Created attachment 68111 --> https://bugs.winehq.org/attachment.cgi?id=68111 log: wine-5.16 -> SC2 broken
Can't start StarCraft II with Wine >= 5.12. Wine 5.11 works fine.
The SC2_x64.exe process uses a full cpu core for some seconds and then simply stalls with this message. Any graphical window can be seen before this happens.
(wine-staging-5.13 on AMD Phenom II X4 955) 00e8:err:virtual:virtual_setup_exception stack overflow 1808 bytes in thread 00e8 addr 0x7bc8200d stack 0x9fc08f0 (0x9fc0000-0x9fc1000-0xa7c0000)
(wine-5.16 on AMD Ryzen-3500U) 00d0:err:virtual:virtual_setup_exception stack overflow 1776 bytes in thread 00d0 addr 0x7f833152cddc stack 0xa0a0910 (0xa0a0000-0xa0a1000-0xa8a0000)
Until from this message, the stdout/stderr only has very minor differences. The attached logs have been created running: C:\Program Files (x86)\StarCraft II\Support64\SC2Switcher_x64.exe Results are the same when running from Blizzard launcher.
Tested with: - wine-staging-5.11 (works) - wine-staging 5.12 + 5.13 + 5.14 + 5.16 (broken) - wine-5.16 (broken) Prefix: Windows 7 - 64 bit Same results on two Debian-11 (Beta/Testing) machines with different AMD Phenom II and Ryzen-3500U processors.
These bugs look similar. But their Wine versions simply don't match up.
https://bugs.winehq.org/show_bug.cgi?id=49476 Overwatch doesn't start on 5.10, 5.11
https://bugs.winehq.org/show_bug.cgi?id=49436 64-bit Diablo III hangs on startup since 5.11 (fixed in 5.13 / 5.14, so that also doesn't match up)
Maybe related: https://forum.winehq.org/viewtopic.php?t=34099
https://bugs.winehq.org/show_bug.cgi?id=49798
--- Comment #1 from kolAflash kolAflash@kolahilft.de --- Created attachment 68112 --> https://bugs.winehq.org/attachment.cgi?id=68112 log: wine-staging-5.12 -> SC2 broken
https://bugs.winehq.org/show_bug.cgi?id=49798
--- Comment #2 from kolAflash kolAflash@kolahilft.de --- Created attachment 68113 --> https://bugs.winehq.org/attachment.cgi?id=68113 log: wine-staging-5.11 -> SC2 works
https://bugs.winehq.org/show_bug.cgi?id=49798
kolAflash kolAflash@kolahilft.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |leslie_alistair@hotmail.com | |, z.figura12@gmail.com Product|Wine |Wine-staging Component|-unknown |-unknown
--- Comment #3 from kolAflash kolAflash@kolahilft.de --- I did some more research and the result was something didn't expected.
Looks like wine-5.11 is affected by the problem too. Just wine-staging-5.11 isn't affected. (wine-5.9 is also affected/broken - didn't test wine-staging-5.9)
So it looks like staging prevented the bug before version 5.12. Maybe it's more appropriately seen as a regression in staging.
https://bugs.winehq.org/show_bug.cgi?id=49798
--- Comment #4 from kolAflash kolAflash@kolahilft.de --- I bisected the problem down to the following wine-staging commit: https://github.com/wine-staging/wine-staging/commit/60074b960facf130e681f531...
It's a rebase against wine commit: https://source.winehq.org/git/wine.git/commit/1f6423f778f7036a3875613e10b9c8...
So it looks like this rebase lost an previously existing achievement of wine-staging which kept SC2 from crashing.
I used wine-staging-60074b960 to patch exactly wine-1f6423f77 when isolating the bug via bisect. And this is how I did patching: ./wine-staging/patches/patchinstall.sh DESTDIR=wine --all -W uxtheme-CloseThemeClass -W uxtheme-GTK_Theming -W fonts-Missing_Fonts -W shell32-ACE_Viewer -W shell32-Toolbar_Bitmaps -W xactengine-initial
One thing the 60074b960 rebase commit does is deleting the directory patches/directmanipulation-new-dll This caught my attention and I tested running patchinstall.sh with additional -W directmanipulation-new-dll on 60074b960^ (predecessor of wine-staging-60074b960, patching wine-bc282905d). Result: SC2 still works. So it's not simply the removal of the directmanipulation-new-dll patchset :-/ (I tested 60074b960^ before when bisecting, but without -W directmanipulation-new-dll and SC2 worked fine)
https://bugs.winehq.org/show_bug.cgi?id=49798
kolAflash kolAflash@kolahilft.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED
--- Comment #5 from kolAflash kolAflash@kolahilft.de --- OK, looks like stuff needed to tun SC2 got switched to PE executables. And I compiled Wine without ensuring gcc-mingw was available for compiling those PE executables.
Instead Wine was simply build without that PE stuff and SC2 couldn't run anymore in more PE based Wine versions > wine-staging-5.11.
Solution: Run when preparing compilation, use mingw option to ensure it's used. ./configure with --with-mingw On Debian-11 (testing) this will need: apt install gcc-mingw-w64-x86-64-win32 gcc-mingw-w64-i686-win32
So it actually seems to be the same problem which has been solved in the Diablo bug. Except I just compiled without gcc-mingw.
https://bugs.winehq.org/show_bug.cgi?id=49436 64-bit Diablo III hangs on startup since 5.11
https://bugs.winehq.org/show_bug.cgi?id=49798
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be Resolution|INVALID |DUPLICATE
--- Comment #6 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- (In reply to kolAflash from comment #5)
So it actually seems to be the same problem which has been solved in the Diablo bug. Except I just compiled without gcc-mingw.
https://bugs.winehq.org/show_bug.cgi?id=49436 64-bit Diablo III hangs on startup since 5.11
*** This bug has been marked as a duplicate of bug 49436 ***
https://bugs.winehq.org/show_bug.cgi?id=49798
Maciej Stanczew maciej.stanczew+b@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |maciej.stanczew+b@gmail.com
--- Comment #7 from Maciej Stanczew maciej.stanczew+b@gmail.com --- Small clarification: bug 49436 was Diablo-specific, and it was fixed in mainstream 5.12: https://bugs.winehq.org/show_bug.cgi?id=49436#c30
This bug is a duplicate of bug 45349, which requires Staging and a PE build.
https://bugs.winehq.org/show_bug.cgi?id=49798
--- Comment #8 from Olivier F. R. Dierick o.dierick@piezo-forte.be ---
*** This bug has been marked as a duplicate of bug 45349 ***
https://bugs.winehq.org/show_bug.cgi?id=49798
--- Comment #9 from Austin English austinenglish@gmail.com --- Closing.
https://bugs.winehq.org/show_bug.cgi?id=49798
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #10 from Austin English austinenglish@gmail.com --- Closing.
-
WineHQ Bugzilla