[Bug 51567] Battle.net app takes a long time to start

WineHQ Bugzilla wine-bugs at winehq.org
Thu Nov 25 08:56:14 CST 2021


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

--- Comment #30 from Sveinar Søpler <cybermax at dexter.no> ---
There was some bugs around 6.12'ish ref:
https://bugs.winehq.org/show_bug.cgi?id=51319

This is closed as fixed with: 
https://source.winehq.org/git/wine.git/commitdiff/361435f6095f8c759979600b06ed28785e7b3aec

Not 100% sure it is related tho.

I know that the Battle.net client does not really work if you have enabled
"browser hardware acceleration" (default enabled) when using regular
wine-staging. This can be disabled in the settings.

I tried with Ubuntu distro provided wine-staging-6.22 and after disabling the
above, i did not seem to have any huge issues connecting, but going back and
forth a bit i experienced a couple of hangs of "Battle.net.exe --updatepid=xxx"
pinning one core to 100% leading me having to kill wineserver.

Normally a fresh prefix with battle.net seems to take around 5 seconds to start
and show my games list and schtuff.

Probably not easy to pinpoint a problem if it works for some :)

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


More information about the wine-bugs mailing list