[Bug 56761] New: So when I install Blizzard.net setup exe its crashes and gives me the backtrace log
https://bugs.winehq.org/show_bug.cgi?id=56761 Bug ID: 56761 Summary: So when I install Blizzard.net setup exe its crashes and gives me the backtrace log Product: Wine Version: 6.0.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: adampigeons(a)gmail.com Distribution: --- Created attachment 76555 --> https://bugs.winehq.org/attachment.cgi?id=76555 the log of the error i launch battlenet exe setup then the window becomes unusable then i get the backtrace log -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56761 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #1 from joaopa <jeremielapuree(a)yahoo.fr> --- You are using wine-6.0.1. There is no interest to use such an old version. Upgrade to the latest one. Currently, it is wine-9.10 If the bug persists, please attach a full console output. Otherwise, you can close this bug as INVALID. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56761 --- Comment #2 from tito <adampigeons(a)gmail.com> --- Created attachment 76558 --> https://bugs.winehq.org/attachment.cgi?id=76558 command line error with Wine --version 9.0 -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56761 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|critical |normal -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56761 --- Comment #3 from Austin English <austinenglish(a)gmail.com> --- (In reply to tito from comment #2)
Created attachment 76558 [details] command line error with Wine --version 9.0
Is that a clean WINEPREFIX? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56761 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|So when I install |Blizzard.net setup crashes |Blizzard.net setup exe its | |crashes and gives me the | |backtrace log | --- Comment #4 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- What URL did you download this from? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56761 --- Comment #5 from tito <adampigeons(a)gmail.com> --- (In reply to Austin English from comment #3)
(In reply to tito from comment #2)
Created attachment 76558 [details] command line error with Wine --version 9.0
Is that a clean WINEPREFIX?
um what do you mean clean? like a virus? im a little inexeperienced using the command line -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56761 --- Comment #6 from tito <adampigeons(a)gmail.com> --- (In reply to Ken Sharp from comment #4)
What URL did you download this from?
i downloaded and installed wine like this from chatgpt :DDDD and downloaded and installed the exe from here : https://download.battle.net/en-us/desktop :how do i install the latest version of wine? ChatGPT To install the latest version of Wine (Wine Is Not an Emulator) on your system, follow these steps depending on your operating system. Below are instructions for installing Wine on Ubuntu, Fedora, and macOS. Ubuntu Add the WineHQ repository: sh sudo dpkg --add-architecture i386 wget -nc https://dl.winehq.org/wine-builds/winehq.key sudo apt-key add winehq.key sudo apt-add-repository 'deb https://dl.winehq.org/wine-builds/ubuntu/ focal main' Replace focal with your Ubuntu version (e.g., bionic for 18.04, hirsute for 21.04, etc.). Update the package list: sh sudo apt update Install Wine: For the stable version: sh sudo apt install --install-recommends winehq-stable For the development version: sh sudo apt install --install-recommends winehq-devel For the staging version: sh sudo apt install --install-recommends winehq-staging Verify the installation: sh wine --version -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56761 --- Comment #7 from Austin English <austinenglish(a)gmail.com> --- (In reply to tito from comment #5)
(In reply to Austin English from comment #3)
(In reply to tito from comment #2)
Created attachment 76558 [details] command line error with Wine --version 9.0
Is that a clean WINEPREFIX?
um what do you mean clean? like a virus? im a little inexeperienced using the command line
No, 'clean' in this case would mean 'unused'. In other words, did you use the same WINEPREFIX that you used when testing with wine-6.0.3? Could you try: $ mv ~/.wine ~/.wine.bak # reinstall the application $ wine setup.exe $ cd "~/.wine/Program Files (x86)/Battle.net" $ wine Battle.net.exe And if that fails, attach the terminal output. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56761 --- Comment #8 from tito <adampigeons(a)gmail.com> --- Created attachment 76572 --> https://bugs.winehq.org/attachment.cgi?id=76572 command line error following user 'Austin English' instructions in the replies please check command line errors history alongside with this -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56761 --- Comment #9 from tito <adampigeons(a)gmail.com> --- Created attachment 76573 --> https://bugs.winehq.org/attachment.cgi?id=76573 terminal history: following user 'Austin English' instructions in the replies -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56761 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick(a)piezo-forte.be --- Comment #10 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, Battle.net is working for me with workarounds for bug 32342 and bug 55979. Bug 32342 can be worked-around by installing a missing font with the command: $ winetricks arial Bug 32342 can also be worked-around by using wine-staging. Bug 55979 can be worked-around by using wine-staging when setting the environment variable STAGING_WRITECOPY to a non-null value: $ env STAGING_WRITECOPY=1 wine Battle.net.exe 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.
http://bugs.winehq.org/show_bug.cgi?id=56761 zefkerr <zefkerrigan(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zefkerrigan(a)gmail.com -- 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.
http://bugs.winehq.org/show_bug.cgi?id=56761 Ken Sharp <imwellcushtymelike@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://www.battle.net/down | |load/getInstallerForGame?os | |=win&version=LIVE&gameProgr | |am=BATTLENET_APP Keywords| |download -- 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.
http://bugs.winehq.org/show_bug.cgi?id=56761 --- Comment #11 from Ken Sharp <imwellcushtymelike@gmail.com> --- I don't see this with Wine 11.10. Please retry. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=56761 mikey9220@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mikey9220@gmail.com --- Comment #12 from mikey9220@gmail.com --- Ran into this same int3 while getting Battle.net running on macOS (Apple Silicon, Wine 11 built from CrossOver's GPL sources), and got far enough to say what the check actually is. Same crash as the backtrace in attachment 76555: libcef at +0x16D00E1, in the --type=renderer child, right after DLL load. The code around it, from disassembling libcef.dll (RVA 0x16D00A0): ret = VirtualProtect(addr, size, PAGE_READONLY, &old); if (!ret) int3; // 0x16D00DE if (old != PAGE_READWRITE) int3; // 0x16D00E1 <- this one addr is a page in libcef's own .data section, i.e. an image mapping that's writable copy-on-write. On Windows the page has already been written to by then, so the previous protection comes back as PAGE_READWRITE. Wine maps writable image pages RW from the start and never tracks the first write, so old stays PAGE_WRITECOPY and Chromium's sanity check trips. Renderer dies, the browser process keeps respawning it, and you get the unusable window from comment 0. So this is bug 29384 (WRITECOPY emulation), just with a CEF face on it. Worth noting because every CEF-based launcher hits it the same way (Battle.net, and I'd expect the others in that bug's list). Two data points that back this up: 1. CrossOver's sources carry a hack for exactly this (simulate_writecopy in dlls/ntdll/unix/virtual.c, flips the vprot to "copied" on the first NtProtectVirtualMemory), gated in the GPL drop behind WINE_SIMULATE_WRITECOPY. Running the same self-built engine with that variable set: 0 EXCEPTION_BREAKPOINT in 90 s, both renderer processes alive, login works. Without it: 2 breakpoints, renderer dead, every time. Nothing else changed. 2. Swapping only ntdll.so from the shipped CrossOver binary into the self-built engine gives the same result as the env var, so it's confined to ntdll's virtual memory code. Full traces (+seh,+virtual,+process,+loaddll) and the engine recipe are at https://github.com/BCD1210/soju/blob/main/docs/DIAGNOSIS.md if anyone wants to reproduce. Happy to test the staging ntdll_WRITECOPY patchset against Battle.net on macOS if that's useful; I haven't yet because the CrossOver-style hack was enough to unblock me. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=56761 --- Comment #13 from Ken Sharp <imwellcushtymelike@gmail.com> --- That would be useful. Saves looking for a fix if it's already staged. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=56761 --- Comment #14 from mikey9220@gmail.com --- Tested. Summary: the staging patchset fixes it, but only the i386 kernelbase matters, and it's the two kernelbase patches, not ntdll. What's in wine-staging today under patches/ntdll-WRITECOPY is just 0010 and 0011 (kernelbase: VirtualProtect reports PAGE_READWRITE when the old protection was PAGE_WRITECOPY, plus the NULL old_prot guard). The ntdll half was dropped in Sept 2024 (commit 16dce521, "wine-staging will currently allow Chrome based application to run"). Applied those two to the same wine 11.0 tree (CrossOver 26.3 GPL sources, macOS 26.5, Apple Silicon), rebuilt kernelbase.dll only, WINE_SIMULATE_WRITECOPY unset, WINEDEBUG=+seh, 90 s per run, same bottle: i386 kernelbase unpatched: EXCEPTION_BREAKPOINT x1 at libcef+0x16D00E1, renderer dies and gets respawned i386 kernelbase patched: 0 breakpoints, both renderers alive from their first spawn, login page renders Battle.net is a 32-bit process, so patching only x86_64 kernelbase changes nothing (I tried that first: 4 renderer deaths in 90 s). Worth keeping in mind if someone tests this on a 64-bit only build. So for bug 29384's CEF face the staging kernelbase patch is enough. It's a workaround though: the page is still mapped RW from the start and nothing tracks the first write, VirtualProtect just lies about the previous protection. CrossOver's variant does it one layer down (ntdll NtProtectVirtualMemory flips the vprot to "copied" on the first protect call), which is closer to what Windows reports but also not a real implementation. -- 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.
participants (2)
-
WineHQ Bugzilla -
WineHQ Bugzilla