[Bug 57098] New: Battle.net does not start after upgrade to 9.16
https://bugs.winehq.org/show_bug.cgi?id=57098 Bug ID: 57098 Summary: Battle.net does not start after upgrade to 9.16 Product: Wine Version: 9.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: sfjuocekr(a)gmail.com Distribution: --- Created attachment 76977 --> https://bugs.winehq.org/attachment.cgi?id=76977 log Battle.net does not work with the latest wine-staging = 9.16 I had just updated wine from apt, the launcher starts but during login it opens a command prompt with error message that closes and opens repeatedly. I suppose this has something to do with the latest cmd.exe changes? -- 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=57098 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=57098 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4(a)web.de --- Comment #1 from Fabian Maurer <dark.shadow4(a)web.de> --- Does this only affect wine-staging, or vanilla wine as well? -- 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=57098 Smoerrebroed <smoerrebroed(a)souls-of-midgard.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |smoerrebroed(a)souls-of-midga | |rd.de --- Comment #2 from Smoerrebroed <smoerrebroed(a)souls-of-midgard.de> --- I tried both wine and wine-staging, and this particular bug appears to be identical for both versions. It also persists on both variants of version 9.17. -- 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=57098 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|cmd |-unknown Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #3 from Fabian Maurer <dark.shadow4(a)web.de> --- Doubt it's cmd related. I can confirm the issue, but it still happens with wine-9.15. Does it still work for you using older wine? -- 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=57098 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |-unknown Product|Wine |Wine-staging CC| |leslie_alistair(a)hotmail.com | |, z.figura12(a)gmail.com --- Comment #4 from Fabian Maurer <dark.shadow4(a)web.de> --- Okay, so this is a wine-staging issue, to be exact it's bug 29384. Since commit c901884ac0af17eeeac309269693d959cfb45e0b (ntdll-WRITECOPY: Remove patch 0010.) the program is broken. FWIW, using "STAGING_WRITECOPY=1" completely breaks the launcher, it doesn't even start. -- 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=57098 --- Comment #5 from Smoerrebroed <smoerrebroed(a)souls-of-midgard.de> --- Running on Arch Linux, and 9.15-staging works reliably every time I downgrade from one of the broken releases. -- 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=57098 lyon(a)pvfree.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lyon(a)pvfree.net -- 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=57098 Ker noa <blue-t(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |blue-t(a)web.de -- 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=57098 --- Comment #6 from Ker noa <blue-t(a)web.de> --- (In reply to Fabian Maurer from comment #4)
Okay, so this is a wine-staging issue, to be exact it's bug 29384.
Since commit c901884ac0af17eeeac309269693d959cfb45e0b (ntdll-WRITECOPY: Remove patch 0010.) the program is broken.
FWIW, using "STAGING_WRITECOPY=1" completely breaks the launcher, it doesn't even start.
Can't be staging, because it happens with pure 9.16 and 9.17 too. -- 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=57098 --- Comment #7 from Fabian Maurer <dark.shadow4(a)web.de> ---
Can't be staging, because it happens with pure 9.16 and 9.17 too.
Obviously, because vanilla wine doesn't have a WRITECOPY implementation to begin with. Staging has one, but it broke due to an update. Or intentionally, since the hack was removed. -- 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=57098 --- Comment #8 from Smoerrebroed <smoerrebroed(a)souls-of-midgard.de> --- So can this be put back into wine-staging? -- 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=57098 --- Comment #9 from lyon(a)pvfree.net --- (In reply to Smoerrebroed from comment #8)
So can this be put back into wine-staging?
Technically the bug exists in both, not just staging. -- 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=57098 --- Comment #10 from lyon(a)pvfree.net --- *** Bug 57101 has been marked as a duplicate of this bug. *** -- 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=57098 --- Comment #11 from Sjoer van der Ploeg <sfjuocekr(a)gmail.com> --- I tried wine 9.17 both mainline and staging with and without: https://bugs.winehq.org/show_bug.cgi?id=29384 Neither solves the problem. Still works fine with 9.15, staging and mainline. ``` wine: Unhandled exception 0x80000003 in thread 394 at address 6DD200E1 (thread 0394), starting debugger... wine: Unhandled exception 0x80000003 in thread 3e4 at address 6DD200E1 (thread 03e4), starting debugger... wine: Unhandled exception 0x80000003 in thread 438 at address 6DD200E1 (thread 0438), starting debugger... ``` -- 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=57098 --- Comment #12 from Sjoer van der Ploeg <sfjuocekr(a)gmail.com> --- Actually(In reply to Sjoer van der Ploeg from comment #11)
I tried wine 9.17 both mainline and staging with and without: https://bugs.winehq.org/show_bug.cgi?id=29384
Neither solves the problem.
Still works fine with 9.15, staging and mainline.
``` wine: Unhandled exception 0x80000003 in thread 394 at address 6DD200E1 (thread 0394), starting debugger... wine: Unhandled exception 0x80000003 in thread 3e4 at address 6DD200E1 (thread 03e4), starting debugger... wine: Unhandled exception 0x80000003 in thread 438 at address 6DD200E1 (thread 0438), starting debugger... ```
Actually, I had failed to apply the patch and got it working now! -- 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=57098 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Battle.net does not start |Chromium and CEF |after upgrade to 9.16 |applications broken since | |wine-staging 9.16 -- 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=57098 Maciej Stanczew <maciej.stanczew(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maciej.stanczew(a)gmail.com --- Comment #13 from Maciej Stanczew <maciej.stanczew(a)gmail.com> --- Can confirm: ae46f56f2cf20585387ff61cb7b36fd5f3d84837 with STAGING_WRITECOPY=1 causes a segfault when starting Battle.net, and c901884ac0af17eeeac309269693d959cfb45e0b (*without* STAGING_WRITECOPY) causes the mentioned crash loop on the login window. Both 9.16 and 9.17 with reverted c901884ac0af17eeeac309269693d959cfb45e0b allow Battle.net to start successfully. -- 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=57098 --- Comment #14 from Fabian Maurer <dark.shadow4(a)web.de> --- Should be fixed in wine-staging-9.18. Can you confirm? -- 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=57098 --- Comment #15 from Maciej Stanczew <maciej.stanczew(a)gmail.com> --- Yes, there are no crashes in Staging 9.18. Thank you. -- 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=57098 --- Comment #16 from lyon(a)pvfree.net --- Can confirm Battle.net does indeed work with wine-staging 9.18. -- 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=57098 --- Comment #17 from Smoerrebroed <smoerrebroed(a)souls-of-midgard.de> --- Likewise, good job! Thanks for your help. -- 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=57098 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED Fixed by SHA1| |16dce521242b3f4a52cd2c8799c | |e6fe464fac83c --- Comment #18 from Fabian Maurer <dark.shadow4(a)web.de> --- Markign fixed by https://github.com/wine-staging/wine-staging/commit/16dce521242b3f4a52cd2c87... -- 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 (1)
-
WineHQ Bugzilla