[Bug 49565] World of Warcraft: black screen/empty window
WineHQ Bugzilla
wine-bugs at winehq.org
Mon Jul 13 12:38:54 CDT 2020
https://bugs.winehq.org/show_bug.cgi?id=49565
Olivier F. R. Dierick <o.dierick at piezo-forte.be> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
CC| |o.dierick at piezo-forte.be
Severity|blocker |normal
--- Comment #2 from Olivier F. R. Dierick <o.dierick at piezo-forte.be> ---
Hello,
Please don't paste long texts, attach them as TXT files instead (@nerzhul).
Issues in a single application are severity 'normal'.
Read more about severity levels descriptions there:
https://wiki.winehq.org/Bugs#severity
I confirm the issue, but this is not really a bug.
This is in fact a resurgence of bug 45349.
World of Warcraft depends on 64bit syscall thunks provided by the staging
patchset 'winebuild-Fake_Dlls'.
Wine 5.11 had several 'temporary regressions' caused by a partial ntdll
splitting, and that patchset is currently (as of 5.12) disabled for that
reason.
--- 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 ---
Until that situation get resolved, you'll have to keep using wine 5.10.
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