[Bug 47207] New: Battle.net crashes with 4.8 Staging
https://bugs.winehq.org/show_bug.cgi?id=47207 Bug ID: 47207 Summary: Battle.net crashes with 4.8 Staging Product: Wine Version: 4.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: hewanci(a)gmail.com Distribution: --- I upgraded today from 4.7 Staging to 4.8, which causes Battle-net to crash upon launch with: wine: Unhandled exception 0x40000015 in thread 9 at address 0x499f27 (thread 0009), starting debugger... Downgrading to 4.7 Staging fixed it. The crash handler was unable to gather information. Arch Linux 64bit, fully upgraded -- 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=47207 Heff <heff(a)heff.se> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |heff(a)heff.se --- Comment #1 from Heff <heff(a)heff.se> --- Same issue here on a fresh install of 4.8. Downgraded to 4.7 and all seems fine. Manjaro 64bit, Up-to-date packages, 4.19 LTS -- 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=47207 pattietreutel <katyaberezyaka(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katyaberezyaka(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.
https://bugs.winehq.org/show_bug.cgi?id=47207 Jan Kowalski <e.misiek(a)poczta.fm> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |e.misiek(a)poczta.fm --- Comment #2 from Jan Kowalski <e.misiek(a)poczta.fm> --- 000b:fixme:winediag:start_process Wine Staging 4.8 is a testing version containing experimental patches. 000b:fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org. 000d:err:menubuilder:init_xdg error looking up the desktop directory 0009:fixme:kernelbase:AppPolicyGetProcessTerminationMethod 0xfffffffa, 0x33fe3c 002a:fixme:kernelbase:AppPolicyGetProcessTerminationMethod 0xfffffffa, 0x32fe3c There is also a error window from battle.net with info about missing dll(without a name of this missing dll), on 4.7 everything worked fine. Fedora 30, winehq-staging-4.8-3.1 -- 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=47207 sgiurgiu11(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sgiurgiu11(a)gmail.com --- Comment #3 from sgiurgiu11(a)gmail.com --- I can confirm this bug as well. On Fedora 30 with wine 4.8, Battle.net app does not start anymore complaining about "Missling DLL". It would not say which DLL is missing and the console messages are not helpful either: 000b:fixme:winediag:start_process Wine Staging 4.8 is a testing version containing experimental patches. 000b:fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org. 000d:err:menubuilder:init_xdg error looking up the desktop directory 0009:fixme:exec:SHELL_execute flags ignored: 0x00000100 0009:fixme:exec:SHELL_execute flags ignored: 0x00004100 002a:fixme:kernelbase:AppPolicyGetProcessTerminationMethod 0xfffffffa, 0x32fe3c 002c:fixme:kernelbase:AppPolicyGetProcessTerminationMethod 0xfffffffa, 0x32fe3c -- 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=47207 Shadders <richard.shadbolt(a)btinternet.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |richard.shadbolt(a)btinternet | |.com --- Comment #4 from Shadders <richard.shadbolt(a)btinternet.com> --- Hi, Given the different distro's listed in this bug report, and that other programs are affected, this is v4.8 wide issue, not just Battle.net. I am using LTSpiceXVII and this fails as it is a 64bit application being used. All 32bit applications function. Someone else on the following bug report has confirmed : https://bugzilla.redhat.com/show_bug.cgi?id=1713945 Also winecfg fails from the command line. [@localhost LTspiceXVII]$ winecfg 000b:fixme:winediag:start_process Wine Staging 4.8 is a testing version containing experimental patches. 000b:fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org. 000d:err:menubuilder:init_xdg error looking up the desktop directory [@localhost LTspiceXVII]$ [@localhost LTspiceXVII]$ wine XVIIx64.exe 000b:fixme:winediag:start_process Wine Staging 4.8 is a testing version containing experimental patches. 000b:fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org. 000d:err:menubuilder:init_xdg error looking up the desktop directory [@localhost LTspiceXVII]$ Regards, Shadders. -- 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=47207 Christian Klein <dvlohp(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dvlohp(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.
https://bugs.winehq.org/show_bug.cgi?id=47207 --- Comment #5 from Storm Engineer <hewanci(a)gmail.com> --- I'm not experiencing this crash with 2.9 - in the other hand, Overwatch itself does crash with 2.9, not sure if there is any relation. See: https://bugs.winehq.org/show_bug.cgi?id=47330 -- 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=47207 mirh <mirh(a)protonmail.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mirh(a)protonmail.ch --- Comment #6 from mirh <mirh(a)protonmail.ch> --- Just installed with 5.5-staging (the latest test result seems to confirm vanilla 5.5 is also fine) and there's no problem whatsoever. I would guess this can be closed? -- 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=47207 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |o.dierick(a)piezo-forte.be Resolution|--- |ABANDONED --- Comment #7 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, Probably a wine-staging regression, but since nobody bothered to investigate and the issue was fixed without notice, I'll mark this bug ABANDONED. If anyone want to have fun doing a regression test to find the staging commit that fixed it, then you're welcome to do it and mark this FIXED once you're done. 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.
https://bugs.winehq.org/show_bug.cgi?id=47207 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #8 from Austin English <austinenglish(a)gmail.com> --- Closing. -- 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)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla