[Bug 56486] New: Battle.net App Crash Cycle on Startup
https://bugs.winehq.org/show_bug.cgi?id=56486 Bug ID: 56486 Summary: Battle.net App Crash Cycle on Startup Product: Wine Version: 9.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wschmrdr(a)gmail.com Distribution: --- Created attachment 76256 --> https://bugs.winehq.org/attachment.cgi?id=76256 Backtrace from the Program Error Starting up Battle.net App. Login screen shows with a loading circle as if it's trying to use a saved password to login. I receive a notice that there's an error and Battle.net has to shut down. I close it, and the error shows up again. This continues in a cycle until I use "wineserver -k" to exit. The backtrace saved from this has been attached. I am able to use the Settings button on the login screen for the Battle.net app, as well as typing in a username/password, but I cannot go any farther than that because there is no submit button and it doesn't seem to want to load. Be aware that I had previously been loading Starcraft II directly using the SC2Switcher.exe executable, but because a new version needs to be downloaded, I'm needing to get into the Battle.net app. Not sure if not using the app is a side effect. For the heck of it, I tried running the setup to update Battle.net, and the same thing occurred. -- 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=56486 --- Comment #1 from wschmrdr(a)gmail.com --- Be aware I have tried this with WINE 9.5, 9.4, and 9.1; all are experiencing the same crash. I also tried using version 8.15 just for the heck of it, and am still seeing the problem. I'm at a loss, since I would have thought I've loaded up the app since that point. -- 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=56486 PeterG <peter.g.anderson(a)live.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |peter.g.anderson(a)live.co.uk --- Comment #2 from PeterG <peter.g.anderson(a)live.co.uk> --- (In reply to wschmrdr from comment #0)
Created attachment 76256 [details] Backtrace from the Program Error
Starting up Battle.net App. Login screen shows with a loading circle as if it's trying to use a saved password to login. I receive a notice that there's an error and Battle.net has to shut down. I close it, and the error shows up again. This continues in a cycle until I use "wineserver -k" to exit. The backtrace saved from this has been attached. I am able to use the Settings button on the login screen for the Battle.net app, as well as typing in a username/password, but I cannot go any farther than that because there is no submit button and it doesn't seem to want to load.
Be aware that I had previously been loading Starcraft II directly using the SC2Switcher.exe executable, but because a new version needs to be downloaded, I'm needing to get into the Battle.net app. Not sure if not using the app is a side effect. For the heck of it, I tried running the setup to update Battle.net, and the same thing occurred.
This looks like the same bug as already reported as https://bugs.winehq.org/show_bug.cgi?id=55979 If you read the comments, there is a workaround in there. See my comment ( #6). -- 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=56486 --- Comment #3 from PeterG <peter.g.anderson(a)live.co.uk> --- Mods, please consider marking this as a duplicate of 55979. -- 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=56486 --- Comment #4 from wschmrdr(a)gmail.com --- Your fix doesn't work; the same issue happens. Clearly not a duplicate. -- 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=56486 --- Comment #5 from PeterG <peter.g.anderson(a)live.co.uk> --- (In reply to wschmrdr from comment #4)
Your fix doesn't work; the same issue happens. Clearly not a duplicate.
Can you list the folders present under the Program Files (x86)/Battle.net/ folder in the WINEPREFIX please? The most recent one I have after installing battle.net is called Battle.net.14766. -- 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=56486 Alexander Potashev <aspotashev(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aspotashev(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=56486 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nicolafragale(a)hotmail.it --- Comment #6 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- *** Bug 56495 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=56486 pep(a)bouah.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pep(a)bouah.net --- Comment #7 from pep(a)bouah.net --- I can still reproduce on the following:
System information: Wine build: wine-9.13 Platform: x86_64 (guest: i386) Version: Windows 10 Host system: Linux Host version: 6.10-arch1-1
Excerpt of the traceback:
00000468 (D) C:\Program Files (x86)\Battle.net\Battle.net.exe 0000046c 0 <== CrRendererMain 0000047c 0 00000480 0 BrokerEvent 00000484 0 ThreadPoolServiceThread 00000488 0 ThreadPoolForegroundWorker 0000048c -2 ThreadPoolBackgroundWorker 00000490 1 Chrome_ChildIOThread 00000494 0 ThreadPoolForegroundWorker 00000498 0 wine_threadpool_worker 0000049c 0 wine_threadpool_waitqueue 000004a0 0 GpuMemoryThread 000004b4 0
This is blocking to me. It's been a while I haven't opened Battle.net so it forced me out of the session and I can't login anymore. Same issue with a fresh WINEPREFIX & Battle.net install. -- 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=56486 --- Comment #8 from PeterG <peter.g.anderson(a)live.co.uk> --- (In reply to pep from comment #7)
I can still reproduce on the following:
System information: Wine build: wine-9.13 Platform: x86_64 (guest: i386) Version: Windows 10 Host system: Linux Host version: 6.10-arch1-1
Excerpt of the traceback:
00000468 (D) C:\Program Files (x86)\Battle.net\Battle.net.exe 0000046c 0 <== CrRendererMain 0000047c 0 00000480 0 BrokerEvent 00000484 0 ThreadPoolServiceThread 00000488 0 ThreadPoolForegroundWorker 0000048c -2 ThreadPoolBackgroundWorker 00000490 1 Chrome_ChildIOThread 00000494 0 ThreadPoolForegroundWorker 00000498 0 wine_threadpool_worker 0000049c 0 wine_threadpool_waitqueue 000004a0 0 GpuMemoryThread 000004b4 0
Are you running this in a 32-bit wineprefix? Battle.net uses some 32-bit libraries but needs to be in a 64-bit wineprefix? Your system information shows that your platform is x86_64 but '(guest: i386)' If you are running in a VM you need KVM or similar enabled in the BIOS to be able to use 64-bit VMs. Also, you would need some kind of GFX card passthrough enabled in the kernel for full 3d acceleration to work in the VM.
This is blocking to me. It's been a while I haven't opened Battle.net so it forced me out of the session and I can't login anymore. Same issue with a fresh WINEPREFIX & Battle.net install.
I notice that you are -- 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=56486 --- Comment #9 from pep(a)bouah.net --- (In reply to PeterG from comment #8) Thanks for the reply!
Are you running this in a 32-bit wineprefix? Battle.net uses some 32-bit libraries but needs to be in a 64-bit wineprefix? Your system information shows that your platform is x86_64 but '(guest: i386)' If you are running in a VM you need KVM or similar enabled in the BIOS to be able to use 64-bit VMs. Also, you would need some kind of GFX card passthrough enabled in the kernel for full 3d acceleration to work in the VM.
I don't think I'm doing anything special, I'm not running in a VM either. I use the package from Archlinux, and I call `WINEPREFIX=foo wine Battle.net-Setup.exe` (which then calls the launcher). The folder didn't even exist at this point. -- 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=56486 --- Comment #10 from wschmrdr(a)gmail.com --- I did notice, during the last update, that the bug still happens. Whilst I respect one commenter's workaround of using older versions of Battle.net, not everyone is going to have that available to them, and when making my original reply, I did not have it available. -- 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=56486 --- Comment #11 from PeterG <peter.g.anderson(a)live.co.uk> --- (In reply to pep from comment #9)
(In reply to PeterG from comment #8)
Thanks for the reply!
Are you running this in a 32-bit wineprefix? Battle.net uses some 32-bit libraries but needs to be in a 64-bit wineprefix? Your system information shows that your platform is x86_64 but '(guest: i386)' If you are running in a VM you need KVM or similar enabled in the BIOS to be able to use 64-bit VMs. Also, you would need some kind of GFX card passthrough enabled in the kernel for full 3d acceleration to work in the VM.
I don't think I'm doing anything special, I'm not running in a VM either. I use the package from Archlinux, and I call `WINEPREFIX=foo wine Battle.net-Setup.exe` (which then calls the launcher). The folder didn't even exist at this point.
Thanks for the info. the simplest way to deal with this is to use the Arch wine-staging package. <code> sudo pacman -R wine sudo pacman -Sy wine-staging STAGING_WRITECOPY=1 WINEPREFIX=foo wine Battle.net-Setup.exe </code> I would recommend you use dxvk in conjunction with wine for gaming if the performance without it is sub-par. -- 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=56486 --- Comment #12 from PeterG <peter.g.anderson(a)live.co.uk> --- (In reply to PeterG from comment #11)
(In reply to pep from comment #9)
(In reply to PeterG from comment #8)
Thanks for the reply!
Are you running this in a 32-bit wineprefix? Battle.net uses some 32-bit libraries but needs to be in a 64-bit wineprefix? Your system information shows that your platform is x86_64 but '(guest: i386)' If you are running in a VM you need KVM or similar enabled in the BIOS to be able to use 64-bit VMs. Also, you would need some kind of GFX card passthrough enabled in the kernel for full 3d acceleration to work in the VM.
I don't think I'm doing anything special, I'm not running in a VM either. I use the package from Archlinux, and I call `WINEPREFIX=foo wine Battle.net-Setup.exe` (which then calls the launcher). The folder didn't even exist at this point.
Thanks for the info. the simplest way to deal with this is to use the Arch wine-staging package.
sudo pacman -R wine sudo pacman -Sy wine-staging
STAGING_WRITECOPY=1 WINEPREFIX=foo wine Battle.net-Setup.exe
I would recommend you use dxvk in conjunction with wine for gaming if the performance without it is sub-par.
-- 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=56486 Igor Polyakov <iop_jr(a)yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |iop_jr(a)yahoo.com --- Comment #13 from Igor Polyakov <iop_jr(a)yahoo.com> --- not sure if related, but I got a looping crash in 9.16 staging, even though it's still working in 9.15 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=56486 Smoerrebroed <smoerrebroed(a)souls-of-midgard.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |smoerrebroed(a)souls-of-midga | |rd.de --- Comment #14 from Smoerrebroed <smoerrebroed(a)souls-of-midgard.de> --- https://bugs.winehq.org/show_bug.cgi?id=57098 -- 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=56486 --- Comment #15 from Igor Polyakov <iop_jr(a)yahoo.com> --- (In reply to Smoerrebroed from comment #14)
okay, so this problem is now fixed but this issue is still relevant for vanilla wine, I still have to use staging to launch battle.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.
http://bugs.winehq.org/show_bug.cgi?id=56486 Chiitoo <chiitoo(a)gentoo.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |chiitoo(a)gentoo.org -- 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=56486 Alexander Vereeken <Alexander88207(a)Protonmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Alexander88207(a)Protonmail.c | |om -- 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=56486 Dmytro Bagrii <dimich.dmb@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dimich.dmb@gmail.com --- Comment #16 from Dmytro Bagrii <dimich.dmb@gmail.com> --- I switched to wine-staging at some point because of this issue. Now in wine-staging-10.20 Battle.net Launcher is also broken by another issue. So I tried non-staging wine. The issue still exists in wine-10.18, 10.19 and 10.20. This patch fixes the issue: https://bugs.winehq.org/attachment.cgi?id=76495 Will it ever be ported into non-staging wine? I would create a ticket for another new issue which breaks Battle.net Launcher in both wine-10.20 and wine-staging-10.20, but can't, because: 1. It can't be created for wine-staging because it also present in non-staging. 2. It can't be created for non-staging because it requires the patch above to be reproducible. How to solve this puzzle? -- 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=56486 Olivier F. R. Dierick <o.dierick@piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be --- Comment #17 from Olivier F. R. Dierick <o.dierick@piezo-forte.be> --- (In reply to Dmytro Bagrii from comment #16)
I would create a ticket for another new issue which breaks Battle.net Launcher in both wine-10.20 and wine-staging-10.20, but can't, because:
1. It can't be created for wine-staging because it also present in non-staging. 2. It can't be created for non-staging because it requires the patch above to be reproducible.
How to solve this puzzle?
Hello, Bugs in upstream Wine that require wine-staging patches to work around other unrelated known bugs can be filed for the Wine product, provided that you explicitly state which wine-staging patches are used for which other bugs, in addition to the usual bug filing information. 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=56486 --- Comment #18 from Dmytro Bagrii <dimich.dmb@gmail.com> --- (In reply to Olivier F. R. Dierick from comment #17)
Bugs in upstream Wine that require wine-staging patches to work around other unrelated known bugs can be filed for the Wine product, provided that you explicitly state which wine-staging patches are used for which other bugs, in addition to the usual bug filing information.
Hello. Thank you for explanation. I'll make sure which exact patch from staging patchset fixes this issue and will create a ticket for new issue (if it's not there yet) referring to that patch. -- 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=56486 --- Comment #19 from wschmrdr@gmail.com --- Well this is still happening, and now the suggestion of going to some old version doesn't even work either because a required DLL is missing. -- 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=56486 mata <sutupud@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sutupud@yahoo.com --- Comment #20 from mata <sutupud@yahoo.com> --- For me it's working using the latest wine-staging (11.4) when starting the launcher using: wine Battle.net.exe --in-process-gpu -- 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=56486 --- Comment #21 from wschmrdr@gmail.com --- (In reply to mata from comment #20)
For me it's working using the latest wine-staging (11.4) when starting the launcher using:
wine Battle.net.exe --in-process-gpu
No good still, whether with the present or "older" version of Battle.net (luckily found a backup with it); same things happen. With the older, a missing DLL. With a newer, the same cycle of crashing as was first reported two years ago. -- 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=56486 --- Comment #22 from wschmrdr@gmail.com --- Went to 11.5, and although the new downloads of the Battle.net app still don't work, I was able to bring up a legacy version of the app. -- 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=56486 zefkerr <zefkerrigan@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zefkerrigan@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=56486 Koli <kollardavid.kolibry@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kollardavid.kolibry@gmail.c | |om --- Comment #23 from Koli <kollardavid.kolibry@gmail.com> --- I see this issue again, it has been working up until wine-staging 11.5, but shows these symptoms on 11.6 and 11.7 -- 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 (3)
-
WineHQ Bugzilla -
WineHQ Bugzilla -
WineHQ Bugzilla