https://bugs.winehq.org/show_bug.cgi?id=51421
kolAflash kolAflash@kolahilft.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED
--- Comment #4 from kolAflash kolAflash@kolahilft.de --- (In reply to Zebediah Figura from comment #1)
Isn't this a duplicate of bug 51331? Or are the symptoms different?
This also fixed by https://bugs.winehq.org/show_bug.cgi?id=51331#c4 So I'd consider it a duplicate.
PLEASE associate this bug with the Battle.net app, so it can be found more easily. https://appdb.winehq.org/objectManager.php?sClass=version&iId=28855
(In reply to David Chalmers from comment #3)
Are you able to run the current/latest battle.net launcher from the site on your machine? I am not as of the latest update, even with bumping Wine back down to 6.11 / resetting prefix.
My already installed Battle.net launcher shows version 5.0.7.84643 and offers no further update.
Using the current Battle.net installer from https://www.blizzard.com/de-de/download/confirmation?product=bnetdesk gives me the same experience. It gets stuck initialising the setup using Wine-6.12. And it works well with Wine-6.11.
89a3b825932d7e3e9671e2a6ca8a646d Battle.net-Setup.exe
env LANG=C.UTF-8 WINEARCH=win64 WINEDLLOVERRIDES=winemenubuilder.exe=d WINEPREFIX="${HOME}"/wines/battle-net/ /opt/wine-devel/bin/wine 'C:\Battle.net-Setup.exe'
OS: Debian-11 x86_64 Same with LANG=de_DE.UTF-8
*** This bug has been marked as a duplicate of bug 51331 ***