[Bug 56486] New: Battle.net App Crash Cycle on Startup

[WineHQ Bugzilla]

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: [e-mail]
          Reporter: [e-mail]
      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.

[Bug 56486] Battle.net App Crash Cycle on Startup

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=56486

--- Comment #1 from [e-mail] ---
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.

[Bug 56486] Battle.net App Crash Cycle on Startup

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=56486

PeterG  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #2 from PeterG  ---

(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).

[Bug 56486] Battle.net App Crash Cycle on Startup

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=56486

--- Comment #3 from PeterG  ---
Mods, please consider marking this as a duplicate of 55979.

[Bug 56486] Battle.net App Crash Cycle on Startup

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=56486

--- Comment #4 from [e-mail] ---
Your fix doesn't work; the same issue happens. Clearly not a duplicate.

[Bug 56486] Battle.net App Crash Cycle on Startup

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=56486

--- Comment #5 from PeterG  ---

(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.

[Bug 56486] Battle.net App Crash Cycle on Startup

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=56486

Alexander Potashev  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 56486] Battle.net App Crash Cycle on Startup

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=56486

Ken Sharp  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #6 from Ken Sharp  ---
*** Bug 56495 has been marked as a duplicate of this bug. ***

[Bug 56486] Battle.net App Crash Cycle on Startup

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=56486

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #7 from [e-mail] ---
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.

[Bug 56486] Battle.net App Crash Cycle on Startup

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=56486

--- Comment #8 from PeterG  ---
(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

[Bug 56486] Battle.net App Crash Cycle on Startup

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=56486

--- Comment #9 from [e-mail] ---
(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.

[Bug 56486] Battle.net App Crash Cycle on Startup

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=56486

--- Comment #10 from [e-mail] ---
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.

[Bug 56486] Battle.net App Crash Cycle on Startup

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=56486

--- Comment #11 from PeterG  ---
(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.

[Bug 56486] Battle.net App Crash Cycle on Startup

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=56486

--- Comment #12 from PeterG  ---
(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.

[Bug 56486] Battle.net App Crash Cycle on Startup

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=56486

Igor Polyakov  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #13 from Igor Polyakov  ---
not sure if related, but I got a looping crash in 9.16 staging, even though
it's  still working in 9.15 staging

[Bug 56486] Battle.net App Crash Cycle on Startup

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=56486

Smoerrebroed  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |smoerrebroed@souls-of-midga
                   |                            |rd.de

--- Comment #14 from Smoerrebroed  ---
https://bugs.winehq.org/show_bug.cgi?id=57098

[Bug 56486] Battle.net App Crash Cycle on Startup

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=56486

--- Comment #15 from Igor Polyakov  ---
(In reply to Smoerrebroed from comment #14)
> https://bugs.winehq.org/show_bug.cgi?id=57098

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