[Bug 49942] New: Games on Battle.net refuse to launch using either wine-5.18 or wine-staging-5.18
https://bugs.winehq.org/show_bug.cgi?id=49942
Bug ID: 49942 Summary: Games on Battle.net refuse to launch using either wine-5.18 or wine-staging-5.18 Product: Wine Version: 5.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: nvaert1986@hotmail.com Distribution: ---
After recently upgrading from wine-staging.5-0 to wine-staging-5.18 (tried wine-5.18 too) all of my Battle.net games fail to launch. When pressing the launch button, the games simply do nothing and sit there stating they're running or state they're running for a few seconds and the message is gone.
I've tried running Warcraft 3: Reforged from the terminal and all I receive is a failed to initialize ClientSdk.dll. Haven't tried this for other games.
I've tried a clean install but it gives the game result.
Whenever I revert back to wine-staging-5.0 the games start fine.
https://bugs.winehq.org/show_bug.cgi?id=49942
--- Comment #1 from nvaert1986 nvaert1986@hotmail.com --- Just tested it with wine-staging-5.16 and the exact same thing happens.
The exact error is the following.
0544:err:module:LdrInitializeThunk "ClientSdk.dll" failed to initialize, aborting 0544:err:module:LdrInitializeThunk Initializing dlls for L"D:\Games\Battle.net\Warcraft III\_retail_\x86_64\Warcraft III.exe" failed, status c0000094
https://bugs.winehq.org/show_bug.cgi?id=49942
--- Comment #2 from nvaert1986 nvaert1986@hotmail.com --- Same goes for wine-staging-5.15. Can't go back any further easily unfortunately due to the ebuilds not being available.
https://bugs.winehq.org/show_bug.cgi?id=49942
Sveinar Søpler cybermax@dexter.no changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |cybermax@dexter.no
--- Comment #3 from Sveinar Søpler cybermax@dexter.no --- Since you mentiones "ebuilds", does that indicate Gentoo? If so.. Are you compiling wine --with-mingw ? (Loads of PE dll work has been done as of late, that may break some games if NOT compiled with mingw-w64)
In the case of you actually using mingw-w64, wine-staging-5.0 is somewhat "old", so upgrading the wineprefix -> wine-staging-5.18++ might break stuff.
I think i had some problems needing me to redo my prefix when coming from wine-staging-4.x -> wine-staging-5.x due to some leftover crud on my wineprefix i run battle.net games from.
I am not sure what you mean by "clean install", but if that only means reinstalling the game from the Battle.net app itself, it probably will not do much if it is "old prefix crud" messing stuff up.
Battle.net works fairly well re-using your old game install if you just create a new wineprefix and moving the game folders over to the new wineprefix, and let the Battle.net client search for games.
https://bugs.winehq.org/show_bug.cgi?id=49942
--- Comment #4 from nvaert1986 nvaert1986@hotmail.com --- (In reply to Sveinar Søpler from comment #3)
Since you mentiones "ebuilds", does that indicate Gentoo? If so.. Are you compiling wine --with-mingw ? (Loads of PE dll work has been done as of late, that may break some games if NOT compiled with mingw-w64)
In the case of you actually using mingw-w64, wine-staging-5.0 is somewhat "old", so upgrading the wineprefix -> wine-staging-5.18++ might break stuff.
I think i had some problems needing me to redo my prefix when coming from wine-staging-4.x -> wine-staging-5.x due to some leftover crud on my wineprefix i run battle.net games from.
I am not sure what you mean by "clean install", but if that only means reinstalling the game from the Battle.net app itself, it probably will not do much if it is "old prefix crud" messing stuff up.
Battle.net works fairly well re-using your old game install if you just create a new wineprefix and moving the game folders over to the new wineprefix, and let the Battle.net client search for games.
With re-installing battle.net I mean removing my wine prefix using rm -rf .wine in my /home/username directory (which is the default prefix). There I completely re-installed everything twice. The installation of Battle.net and starting Battle.net works fine, but starting any of the games does not. Whenever I switch back to wine-staging.5.0 and start any of the games, they work flawlessly using the prefix created with wine-staging-5.18.
I'm using Gentoo indeed. I'm not compiling with mingw or mingw-w64. I'm using GCC 9.3.0 using -O2 and --march=znver1 those ore the only flags set.
I just started a compilation to double confirm if mingw is being called, but when watching the compilation, mingw is not being called at all.
The only difference as of recent is unwind support, which I disabled, which is set through a USE flag, but which I don't need.
https://bugs.winehq.org/show_bug.cgi?id=49942
nvaert1986 nvaert1986@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Gentoo
https://bugs.winehq.org/show_bug.cgi?id=49942
--- Comment #5 from nvaert1986 nvaert1986@hotmail.com --- UPDATE: I'm not sure whether mingw is being using, when I check the ebuild it states that when using multilib. I'm assuming they mean both 32-bit and 64-bit support, but if multilib means something different then it's not the case. If they define it as 32-bit and 64-bit support, then mingw is definitely turned off.
multilib_src_configure() { local myconf=(
--without-mingw # linux LDFLAGS leak in mingw32: bug #685172
)
https://bugs.winehq.org/show_bug.cgi?id=49942
--- Comment #6 from Sveinar Søpler cybermax@dexter.no --- I do not know how Gentoo uses the ebuilds and however that works.. But if it run wine's "configure" script, it will detect if you have mingw-w64 installed... unless specifically called to use --without-mingw some other place..
I think that is a distro question not suited for this particular bug.
I found this: https://bugs.winehq.org/show_bug.cgi?id=42741
I'm still having issues with wine-5.13-195-g0d42388095 (Staging) has that patch been enabled?
Are you running a PE build? 'winebuild-pe_syscall_thunks' patchset will not help >with non-PE builds; see bug 45349 for more info. The game launches for me successfully with a PE build of Staging 5.13.
When they mention "PE-build" it means built --with-mingw
It is basically the same issue i get with World of Warcraft PTR when running > wine-staging-5.10'ish (or thereabouts).
https://bugs.winehq.org/show_bug.cgi?id=49942
--- Comment #7 from nvaert1986 nvaert1986@hotmail.com --- (In reply to Sveinar Søpler from comment #6)
I do not know how Gentoo uses the ebuilds and however that works.. But if it run wine's "configure" script, it will detect if you have mingw-w64 installed... unless specifically called to use --without-mingw some other place..
I think that is a distro question not suited for this particular bug.
I found this: https://bugs.winehq.org/show_bug.cgi?id=42741
I'm still having issues with wine-5.13-195-g0d42388095 (Staging) has that patch been enabled?
Are you running a PE build? 'winebuild-pe_syscall_thunks' patchset will not help >with non-PE builds; see bug 45349 for more info. The game launches for me successfully with a PE build of Staging 5.13.
When they mention "PE-build" it means built --with-mingw
It is basically the same issue i get with World of Warcraft PTR when running
wine-staging-5.10'ish (or thereabouts).
I just double checked and it's definitely not compiled with mingw, as I do not have mingw nor crossdev on my system.
Do you know wheter it works with a more recent wine-staging version for you (like 5.17 or 5.18?) If so I'll file a bug at Gentoo, referencing to this bug here.
https://bugs.winehq.org/show_bug.cgi?id=49942
--- Comment #8 from Sveinar Søpler cybermax@dexter.no --- (In reply to nvaert1986 from comment #7)
It is basically the same issue i get with World of Warcraft PTR when running
wine-staging-5.10'ish (or thereabouts).
I just double checked and it's definitely not compiled with mingw, as I do not have mingw nor crossdev on my system.
Do you know wheter it works with a more recent wine-staging version for you (like 5.17 or 5.18?) If so I'll file a bug at Gentoo, referencing to this bug here.
As i have not tested every possible combination of patches and tweaks to figure out how it all ties together, i know that WoW PTR does not work with anything older than wine-staging-5.13 (Ref. this patchset: https://github.com/wine-staging/wine-staging/commit/d2d0366ce5df254957a96bb6...)
Wine-staging-5.12 did not work. This is when NTDLL was converted to PE, but did not have the above patchset. You could (and can) still build wine --without-mingw, but for some reason it does not work.
There are some posts (cba to dig them all up) indicating that it has to do with copy protection of sorts (for some games). The conclusion should be that it could work up until wine-staging-5.11, but if you use wine-staging-5.13 or NEWER, you probably need to compile using --with-mingw.
Gentoo seems to have had this "force-disabled" due to some bug back with wine-4.7, so i cannot tell if its fixable by just editing your ebuild conf manually?
Could you try to install mingw-w64, then edit the ebuild (/var/db/package-manager/repos/wine/wine-staging-5.18.ebuild ?? or wherever it is) manually, and change the line:
--without-mingw # linux LDFLAGS leak in mingw32: bug #685172 to --with-mingw # linux LDFLAGS leak in mingw32: bug #685172
Just to see if it compiles?
-
WineHQ Bugzilla