[Bug 49525] New: Battle.net launcher fails to launch games with "ClientSdk.dll" failed to initialize error

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=49525

Bug ID: 49525
           Summary: Battle.net launcher fails to launch games with
                    "ClientSdk.dll" failed to initialize error
           Product: Wine-staging
           Version: 5.12
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
                CC: [e-mail], [e-mail]
      Distribution: ---

Since wine-staging 5.12, the Battle.net launcher is failing to launch some
games and is getting error "04c4:err:module:LdrInitializeThunk "ClientSdk.dll"
failed to initialize, aborting".  With wine-staging 5.3, 5.9 - 5.11, both
Warcraft III and Starcraft I are able to launch.  Vanilla wine 5.1, 5.9 - 5.12
all appear to fail with the same ClientSdk.dll error.

[Bug 49525] Battle.net launcher fails to launch games with "ClientSdk.dll" failed to initialize error

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=49525

--- Comment #1 from Matthew Stapleton  ---
The Battle.net app version is currently 1.22.0.12040 and I am using Gentoo
Linux.

[Bug 49525] Battle.net launcher fails to launch games with "ClientSdk.dll" failed to initialize error

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=49525

Olivier F. R. Dierick  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #2 from Olivier F. R. Dierick  ---
Hello,

This is a resurgence of STAGED bug 42741.

It was covered by wine-staging patchset 'winebuild-Fake_Dlls', but that
patchset is disabled in 5.12 due to changes in ntdll.

--- quote from winebuild-Fake_Dlls/definition ---
# As of 43be3507c04, unless I've misread, ntdll.dll no longer has the chance to
# run code before ntdll.so performs process initialization. Unfortunately,
# ntdll.so is still making calls to Nt* exports during that process
# initialization, which in practice means it's calling syscall thunks. In order
# for this series to work, we need to poke __wine_syscall_dispatcher into the
# TEB before those calls are made. Fixing this would require a nontrivial
amount
# of effort, which will be obviated as soon as Alexandre finishes splitting
# ntdll upstream.
Disabled: true
--- end quote ---

Regards.

[Bug 49525] Battle.net launcher fails to launch games with "ClientSdk.dll" failed to initialize error

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=49525

Zebediah Figura  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|-unknown                    |ntdll
            Product|Wine-staging                |Wine
         Resolution|---                         |DUPLICATE
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #3 from Zebediah Figura  ---
Marking duplicate.

*** This bug has been marked as a duplicate of bug 42741 ***

[Bug 49525] Battle.net launcher fails to launch games with "ClientSdk.dll" failed to initialize error

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=49525

Mike Lothian  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 49525] Battle.net launcher fails to launch games with "ClientSdk.dll" failed to initialize error

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=49525

Alistair Leslie-Hughes  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #4 from Alistair Leslie-Hughes  ---
Closing Duplicate.