https://bugs.winehq.org/show_bug.cgi?id=56486
--- Comment #8 from PeterG peter.g.anderson@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