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

WineHQ Bugzilla wine-bugs at winehq.org
Mon Jul 6 05:28:52 CDT 2020


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

Olivier F. R. Dierick <o.dierick at piezo-forte.be> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |o.dierick at piezo-forte.be

--- Comment #2 from Olivier F. R. Dierick <o.dierick at piezo-forte.be> ---
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.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.



More information about the wine-bugs mailing list