I can't install battle.net in lutris

[wlmosv]

My friends, this has always been a problem. Since lutris has almost no information about battle.net installation in gentoo, I got stuck at 45% during the installation process. It seems that he is reminding me to use 32-bit wintrick. I have tried many versions of wine and I don't know what dependencies should be installed in my gentoo.

[eccerr0r]

What version of wine are you using? I think later wines are okay and didn't need to winetricks (though it broke WoW for me...)

Battle.net has always been pretty broken. You should also snoop around the World of Warcraft thread as there's usually stuff about battle.net for updates there as well...

[YoungerDryas]

I'm encountering this issue and I've been playing around with debugging this issue. Initially before I switched wine's, wine-ge-8-26 errored that it required a lower version of gnutls:

Code: Select all

0024:err:winediag:gnutls_process_attach failed to load libgnutls, no support for encryption
0024:err:winediag:process_attach failed to load libgnutls, no support for pfx import/export
00e0:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 0175FEF4
0024:err:winediag:process_attach Failed to load libgnutls, secure connections will not be available.
0024:err:secur32:SECUR32_initSchannelSP no schannel support, expect problems
0024:err:kerberos:kerberos_LsaApInitializePackage no Kerberos support, expect problems
ntlm_auth: /home/sai/.local/share/lutris/runtime/Ubuntu-18.04-x86_64/libgnutls.so.30: version `GNUTLS_3_6_3' not found (required by /usr/lib64/samba/libgensec-private-samba.so)
0024:err:ntlm:ntlm_LsaApInitializePackage no NTLM support, expect problems

So, I moved to a newer version of wine, namely: Kron4ek's wine-staging v10.7, because I thought a newer version would be more compatible with my version of gnutls. And so far, it looks like it worked with a notable error popping up instead:

Code: Select all

0288:err:bcrypt:key_asymmetric_create no encryption support

Running Lutris with LUTRIS_RUNTIME=0 got the installer to progress past 45% and install Battle.net, BUT I cannot login while a looping CMD window pops in and out in quick succession such that I cannot see what text it displays.

[Kensai]

What I usually do is have wine-proton emerged and instead of using the lutris provided, I switch to system wine. It works, if it doesn't then I go back to lutris wine-ge.

[halcon]

I played in Diablo4 via Battle.net via Lutris in 2023.

Checked my installation (transferred to my current machine from the one I used in 2023) - and Battle.net launched, logged in and updated normally, without issues.

Lutris 0.5.19 with python 3.13, game runner GE-Proton (Latest), DXVK enabled.

[apo11o]

I'm using KDE with an NVIDIA GPU and I just recently fixed BNET after it was broken for awhile.
Here's how I did it from all my research from the BNet error codes and other sources:
1. Download the Battle.net-Setup.exe from bnet.com
2. For NVIDIA make sure the "nvidia-drivers" package is emerged with USE abi_x86_32 (I believe BNet still needs 32-bit compatibility so that's why I do this)
3. Make sure your wine package is updated and if you have an old 64-bit wineprefix in your home directory, completely delete it and recreate it so everything is fresh
4. In Lutris, in the "hamburger menu", go to "Add Games" and select "Add locally installed game"
5. Fill in the needed info (give it a name like "BNET" or whatever, select the Battle.net-Setup.exe as the program to run, "Runner" will obviously be Wine, select the folder of your new wineprefix, make sure the version is set to 64-bit, etc.)
6. When the "Add locally installed game" dialog closes, you should see your "BNET" entry added to your Lutris menu. Start it.
7. This will begin the installer and it should not freeze at 45% and finish normally, and you should be able to login.

The only errors I encountered in this process were because my wineprefix was outdated (and thus I was stacking failed BNet installation files, hence nuking the whole wine dir and starting fresh) and because I mistakenly had the wineprefix for BNET selected at 32-bit instead of 64 (it needs backwards compatibility with 32-bit but still needs to be set to 64).

The only downside to this method is you will have to manually manage the wine version in this "BNET" entry, so whenever you upgrade versions and delete the old one you need to manually change it in the entry via the "Configure" context menu. This happened to me this morning because I updated to a new wine version and deleted the old and when I noticed BNet acting dysfunctional again (opening but then freezing on the login screen or logging in but getting no data) I remembered I deleted the old wine. Updated the menu selection and it worked again.