Current version of the app
Application Details:
Version: | Current |
License: | Free to use |
URL: | https://blizzard.com/apps/batt... |
Votes: | 11 |
Latest Rating: | Garbage |
Latest Wine Version Tested: | 9.16-staging |
Maintainers: About Maintainership
What works
Everything
What does not
Workarounds
What was not tested
Shop tab for real money purchasing
Hardware tested
Graphics:
Additional Comments
I give this a gold rating because for intel users it is necessary to upgrade your drivers using external drivers before you can even use Battle.net's Launcher. For intel the launcher may appear distorted or completely black without updated drivers. Any others like AMD and NVIDIA work just fine with bundled drivers typically and the only thing you may run into with bundled drivers for these is individual game performance problems. Other than the driver issue for intel installation and running works fine.
Operating system | Test date | Wine version | Installs? | Runs? | Used Workaround? | Rating | Submitter | ||
Show | Arch Linux x86_64 | Aug 31 2024 | 9.16-staging | Yes | Yes | No | Garbage | Smoerrebroed | |
Show | Arch Linux x86_64 | Aug 31 2024 | 9.15-staging | Yes | Yes | No | Silver | Smoerrebroed | |
Show | Fedora 40 | Aug 19 2024 | 9.15-staging | Yes | Yes | No | Garbage | John R. Sohn | |
Show | NixOs | May 17 2024 | 9.8-staging | Yes | Yes | No | Platinum | Igor Polyakov | |
Show | Debian GNU/Linux 12.x "Bookworm" x86_64 | May 10 2024 | 9.8 | Yes | Yes | Yes | Gold | Freeyorp |
Bug # | Description | Status | Resolution | Other apps affected |
29384 | Multiple applications expect correct handling of WRITECOPY memory protection (Voobly fails to launch Age of Empires II, MSYS2) | STAGED | View | |
32342 | Multiple applications and games using 'Webkit', 'Blink' or 'CEF' (libcef) web browser engine crash on startup ('Arial' and 'Times New Roman' font face name validation) | STAGED | View | |
33943 | Battle.net client dropdowns do not appear until you hover its options | STAGED | View | |
38845 | Battle.net launcher shows white screen with WINEPREFIX Windows version > 'Windows XP' and builtin d3dcompiler_47.dll | REOPENED | View | |
39069 | Battle.net launcher requires multiple click to focus tabs in Openbox | NEW | View | |
40857 | Battle.net drop-down menus lack border | NEW | View | |
40930 | Battle.net App: Windows versions higher than XP draw GTK decorations | UNCONFIRMED | View | |
43349 | Blizzard App Fails to Recognize Password Upon Switching Regions | UNCONFIRMED | View | |
44210 | GNUTLS_CIPHER_CHACHA20_POLY1305 is not supported | UNCONFIRMED | View | |
45837 | Battle.net Launcher dropdown menu cant be opened, no icon to click | UNCONFIRMED | View | |
46836 | Battle.Net UI freezes when downloading big games after a period of time | UNCONFIRMED | View | |
49941 | Battle.net gui pop-up on launch ubuntu 18.04 | UNCONFIRMED | View | |
50064 | A transparent Agent.exe window is shown when Battle.Net launches | UNCONFIRMED | View | |
51567 | Battle.net app takes a long time to start | UNCONFIRMED | View | |
52029 | Battle.net: A required DLL could not be found, on NTFS drive | NEEDINFO | View | |
53697 | Battle.net Agent.8009/Agent.exe not working (installing Battle.net client and updating games) (2022-09-17) | NEEDINFO | View | |
54050 | X11, 10-bit color: Battle.net launcher windows or parts thereof aren't rendered | UNCONFIRMED | View | |
55613 | right click does not work in Battle.net App (friends list, favorite games) | UNCONFIRMED | View | |
55979 | Blizzard Battle.net Launcher: New Version Released On 11/30/2023 Hangs During Installation | NEW | View | |
56486 | Battle.net App Crash Cycle on Startup | UNCONFIRMED | View | |
57098 | Chromium and CEF applications broken since wine-staging 9.16 | RESOLVED | FIXED | View |
Please note that due to syscall thunks requirements described in bug #45349, 64-bit game clients for Blizzard games will work only in Wine built with PE support.
Wine version
If possible, use Wine Staging (any reasonably new version will work).
Starting from version 3.12 vanilla Wine should also work, but it can have minor problems, so use it only if there is no option to install Staging.
Libraries
Ensure that your system has 32-bit libraries for libldap and gnutls installed (lib32-libldap and lib32-gnutls on Arch, but names may vary on other distros).
Wineprefix configuration
64-bit prefix is recommended, since Blizzard is discontinuing 32-bit support for some of their games.
Windows version should be set to Windows 7 or above.
Winetricks
"corefonts" should be installed, otherwise some pages will have incorrectly rendered text. The easiest way to do this is through winetricks:
$ winetricks corefonts
You can also have the fonts installed through your package manager:
Installation
After everything described above is configured, run (from the terminal):
$ wine Battle.net-Setup.exe
and follow instructions in the installer.
Blizzard App icon keeps spinning forever, can't login
Installer does not work on Arch Linux x86_64
Battle.net window is all white
Battle.net fails to start due to Qt error (bug #53826)
This application failed to start because it could not find or load the Qt platform plugin "windows" in "".
setfattr -x user.DOSATTRIB platforms/qwindows.dll
Lately there have been problems with Agent.exe, which result in users not being able to install and update games. The issue seems to appear randomly, but once it does, it will not go away without applying a workaround.
Currently known workarounds:
Unverified workarounds:
If anyone has new information on this topic, please let others know in the comments.
The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
by Ewan on Sunday August 25th 2024, 12:39
by Dazai Osamu on Sunday September 1st 2024, 9:22
by Ewan on Monday September 2nd 2024, 9:43
by lyon on Sunday August 25th 2024, 6:29
"wine: Unhandled exception 0x80000003 in thread 4bc at address 69E400E1 (thread 04bc), starting debugger..."
System information:
Wine build: wine-9.16 (Staging)
Platform: x86_64 (guest: i386)
Version: Windows 10
Host system: Linux
Host version: 6.7.12+bpo-amd64
by Chiro on Sunday August 25th 2024, 18:44
ntdll write patchset was changed in staging for this release.
by Igor Polyakov on Tuesday September 3rd 2024, 11:26
by Dif on Sunday September 8th 2024, 11:07
For the moment I am configuring my package manager to keep wine-staging at 9.15 (at least as long as Gentoo main tree keeps it available).
by Jon on Tuesday April 9th 2024, 21:47
by Chiro on Tuesday April 9th 2024, 23:12
I had no problems
by Igor Polyakov on Tuesday April 23rd 2024, 3:44
by Igor Polyakov on Saturday May 18th 2024, 19:10
by Joel Meijering on Tuesday March 19th 2024, 9:41
1. Clone Wine from source.
2. Perform git checkout wine-9.4
3. Apply this patch by hand: bugs.winehq.org/attachment.cgi?id=75727&action=diff
4. Build for WoW64 (32+64 bit). It was important to build in an empty folder and not in the source tree, and to build x64 first, then build x32, while pointing to the x64 build. Anyway, this is covered in the standard build guide, nothing unusual: wiki.winehq.org/Building_Wine#Shared_WoW64
5. Clean prefix. Default 64-bit mode. (rm rf ~/.wine)
6. Start installer and install Battle.net
7. Once install is complete and it displays the login screen, Wine error dialogs popped up and there was no Login button. However in Settings (Gear icon) I was able to turn of Browser acceleration. It will prompt to restart.
8. Instead of launching Battle.net normally, I launched it like this (I used build32 as x32 build dir and wine-src as Wine git source dir, yours may vary; I ran this command from one folder above):
./wine-src/wine ./build32/programs/winedbg/i386-windows/winedbg.exe ~/.wine/drive_c/Program\ Files\ \(x86\)/Battle.net/Battle.net.exe
9. It launched without any Wine error dialogs. However the Login button did not appear. Despite of that, after entering email and password, pressing enter while the password field was still in focussed triggered to login. I was able to login and initiate download of StarCraft without issues. The Battle.net app seemed to work fine.
by b0nt4kun on Friday February 16th 2024, 13:57
I had "strange" camera movements (camera going back to the PoV from a second before very regularly), and it **seems** happening with 9.2 only.
by Michael on Tuesday February 20th 2024, 12:40
by b0nt4kun on Tuesday February 20th 2024, 15:12
by b0nt4kun on Tuesday February 20th 2024, 15:14
by spaceman on Saturday January 27th 2024, 10:02
Delete /[WINPREFIX]/drive_c/Program Files (x86)/Battle.net/Battle.net.145x/
That's all Battle.net subfolders numbered greater than Battle.net.14494. This folder works all updates after this do not.
by JZ on Saturday January 27th 2024, 17:40
by spaceman on Saturday March 23rd 2024, 4:12
www.dropbox.com/scl/fo/ck1bazqr10x9bq61dj7np/h?rlkey=x80ekfjjf28g5ac8zrj38366q&dl=0
by Jon on Wednesday January 17th 2024, 17:32
by Philipp Ludwig on Wednesday January 24th 2024, 9:24
by Sean Rhone (Espionage724) on Wednesday January 10th 2024, 18:58
I was playing for a few days now on Fedora 39 with just logging in with email/pass, but earlier today I got Incompatible realms and needed to patch. I installed the Bnet client to my prefix, and at the log-in, used the Settings gear to continue without log-in. WoW was automatically detected. I then right-clicked the Bnet icon in the Wine System Tray and selected Resume Updates. Downloading happened, I eventually got a Bnet notification that WoW was playable, and then I launched WoW and signed-in no problem!
I've only tried WoW but it seems possible to try with any game that doesn't need Battle.net log-in (Diablo 3 I think does email/pass). The Bnet client's main page doesn't render, but Settings from the tray icon renders fine.
by Peter on Saturday December 23rd 2023, 23:43
I got Battle.net working correctly with wine-staging-9.0-rc3 by building Wine with the chromium issues hack from bugs.winehq.org/show_bug.cgi?id=29384#c56
by spaceman on Wednesday December 6th 2023, 3:13
Delete /[WINPREFIX]/drive_c/Program Files (x86)/Battle.net/Battle.net.14542/
I updated WoW and moved on. Hopefully one of our Wine Dev buddies will resolve the underlying cause soon.
by Adrian Demarais on Friday January 26th 2024, 17:17
You get a pop-up about a newer version being available, and to check your shortcuts.
Pop-up has big button "continue with newer version" which then launches the old (I think?) bnet.
I took a look at what was actually running once battle.net was up, it appears to be a mix of new and old.
by b0nt4kun on Saturday December 2nd 2023, 2:31
us.forums.blizzard.com/en/blizzard/t/latest-update-breaks-battlenet-launcher-on-linux/48424/20
In my case this sadly not to work, as a short term solution I deleted my Battle.net.14542 (I still had Battle.net.14494) which allowed me to have it display something after logon.
It seems to be a display issue, since even with Battle.net.14542 dark screen, the system tray icon allows to access parameters, and games seems to still update automatically (there is a also new vulkan-1.dll in Battle.net.14542 folder which convince me further it's related to display)
by Dmytro Bagrii on Sunday December 3rd 2023, 1:04
Looks like WINE_SIMULATE_WRITECOPY is not a Wine option but Proton, so it wouldn't work with vanilla Wine.
by Jon on Wednesday December 6th 2023, 11:15
by spaceman on Saturday March 25th 2023, 12:05
The app installs into a fresh prefix and fails to start with the QT error. setfattr -x user.DOSATTRIB qwindows.dll fixes that. Then the login box will appear, you have to press enter after typing in your password because there is no Log in button displayed. Installing corefonts (with winetricks) fixes this.The app will not display correctly after launching unless set to XP or Vista. The app will not install World of Warcraft as these OS are no longer supported. Deep joy. Tried installing VCRUN2015 with winetricks. No improvement.
An old install with display with Windows 10 or above set, however it doesn't install either. It says Initialising, counts up...populates the Warcraft folder with: two sub folders; Data and _retail_; World of Warcraft Launcher.exe; .product.db; Launcher.db. Then switches to Updating, with Initialising below and not a damn thing goes into _retail_ where the retail game should install...
by spaceman on Sunday March 26th 2023, 3:53
by Josh Whitley on Tuesday March 7th 2023, 14:20
- Wait until the Battle.net installer has failed to launch the Agent and quits with an error code.
- In the new WINE environment that was created for the install, open the WINE Control Panel.
- Open Add/Remove Programs.
- Click the �Install� button and select the Battle.net installer EXE.
- The installation should complete normally, successfully installing Battle.net
I can not explain why this worked for me. it may have somethinig to do with the permissions that the installer is launched with from this dialog. I tried many other suggested work-arounds and stumbled across this one on my own. Hope it works for others who find this thread!
by no on Tuesday March 21st 2023, 11:04
by Dmytro Bagrii on Friday February 3rd 2023, 20:39
Update stuck at 0% or in paused state . Attempt to resume or pressing "Update" button manually leads to "Whoops! Looks like something broke. Give it another shot. More help: BLZBNTAGT00000BB8". Probably because of another instance of StarCraft.exe already running after first attempt.
Suspicious messages in Agent-20230204T021039.log:
[I 2023-02-04 02:10:40.0019] Network Connection Response to eu.patch.battle.net:1119/agent - CURL error: 0, Status Code: 404
...
[W 2023-02-04 02:10:40.0144] Build marked non-playable for s1: Permissions check failure (2123)
...
[W 2023-02-04 02:10:49.0184] Failed to create registry key - HKEY_LOCAL_MACHINE\Software\RegisteredApplications
In AgentNGDP-20230204T021039.log:
[W 2023-02-04 02:11:35.0160] - Files found in EM that aren't in DLM: 3
[I 2023-02-04 02:11:35.0164] - garbage collection, final container state - spans allocated: 14871 - spans free: 0 - bytes allocated: 5752356142 - bytes available: 269125550746 - bytes capacity: 274877906944
[E 2023-02-04 02:11:35.0189] - failed to bind shared memory file 'C:/Program Files (x86)/StarCraft/Data/data/shmem': SHMEM_EXISTS
[E 2023-02-04 02:11:35.0190] - failed to bind shared memory file 'C:/Program Files (x86)/StarCraft/Data/data/shmem': SHMEM_EXISTS
[E 2023-02-04 02:11:35.0191] - failed to bind shared memory file 'C:/Program Files (x86)/StarCraft/Data/data/shmem': SHMEM_EXISTS
[E 2023-02-04 02:11:35.0191] - Failed to mount container index at 'C:/Program Files (x86)/StarCraft/Data/data': CCE_SHARED_MEMORY_BIND_FAILURE
[E 2023-02-04 02:11:35.0191] CASC Compaction failure
I also tried to copy Agent.exe from Agent.7984. It either overwrites old binary with new one on first run or complain about unability to update agent when modification blocked with `chattr +i`.
by Kai Sauerwald on Wednesday November 30th 2022, 12:39
find -exec setfattr -x user.DOSATTRIB {} \;
It recursively changes an attribute of the files so that the battle.net launcher can locate them.
by Matthew Farrell on Saturday September 17th 2022, 16:17
by kolAflash on Saturday September 17th 2022, 17:57
See here for workaround:
bugs.winehq.org/show_bug.cgi?id=53697
www.reddit.com/r/linux_gaming/comments/xgb5fx/problems_with_battlenet_today/
by Matthew Farrell on Monday September 26th 2022, 12:58
by Cory on Friday September 9th 2022, 15:39
Downloading games takes much longer than should be required, sometimes with the application spinning endlessly and never installing a game. Wrath of the Lich King Classic in particular had to be "installed" 3 times for it to actually work.
WoW itself will crash quite frequently, with the game locked up but the cursor and rest of the machine responsive. Killing the WoW.exe process is required to continue to use the computer. This behavior isn't reproduced with any specific event and occurs in retail and classic using both nvidia and amd cards. It's likely that a recent patch by Blizzard has caused this behavior, but it's become quite frustrating.
It seems that on a new install launching battle.net happens without problem, but the more you use it the more the odd behavior appears. I'm using the most recent Lutris install script, using pretty much any other runner makes the issue much worse.
by spaceman on Sunday July 24th 2022, 11:18
Test results have been posted, will be above soon. Any suggests for troubleshooting / fixes?
Many thanks, guys.
by Maciej Stanczew on Monday July 25th 2022, 17:33
The logs that you posted are just "fixme"s, they're probably not directly related to the issue. Try to see if there are any "err" logs before that.
by spaceman on Tuesday July 26th 2022, 5:49
Many thanks the the response.
by spaceman on Wednesday July 27th 2022, 12:40
This was the only error I've had:
ERROR:dxva_video_decode_accelerator_win.cc(1320)] DXVAVDA fatal error: Could not load msmpeg2vdec.dll: Module not found. (0x7E)
Now it got silly. I installed libasound2-plugins:i386, libsdl2-2.0-0:i386, libdbus-1-3:i386, libsqlite3-0:i386 and this fixed the crashing and Blizzard Report dialog problem. I now have a log in box (with a graphical corruption hiding the login button). So I removed these four components, so I could install them individual to test if one of them fixed the issue rather than all four. This took Wine out too! I reinstalled Wine, again, and I was back to a login box (with a graphical corruption)...still unable to log in. The fix is surely disabling Browser Hardware Acceleration, sadly before I did that I tried reinstalling those four components: libasound2-plugins:i386 was already, I reinstalled libsdl2-2.0-0:i386 then I remembered to enter Settings and disable Browser Hardware Acceleration...I am currently re-installing World of Warcraft.
I will rip out wine and all these extras at some point, reinstall Wine and test. If I have the original issue, I will test which component above actually fixes it and post new Test Results with my workarounds. Thanks Maciej. I suggest deleting my Garbage Test Results.
by Maciej Stanczew on Sunday July 31st 2022, 2:57
Done.
I'm not knowledgeable about running Wine on Debian-based distributions, but looking at Lutris' dependency list, it does indeed suggest those 4 packages you installed are required:
github.com/lutris/docs/blob/master/WineDependencies.md
On my Arch system I only have 32-bit versions of sdl2 and dbus installed (both pulled as dependencies of wine-staging package). I don't have alsa-lib (which I think is analogous to libasound2) or sqlite.
If you figure out exactly which packages are needed to be present (on top of those pulled as wine dependencies), I can update the HowTo note with this information.
by Svavar kjarrval on Sunday November 14th 2021, 8:45
Is anybody else been experiencing this lately? (Wine 6.20 for Impish is installed)
by spaceman on Tuesday July 20th 2021, 8:44
Currently known workarounds:
Try killing Agent.exe process; it will be restarted automatically and there is a chance that installation will proceed.
If that doesn't work:
Close Battle.net App (make sure that wineprefix is closed completely, e.g. by running "wineserver -k")
Delete "C:\ProgramData\Battle.net\Agent\product.db" file
Relaunch Battle.net App
I tried this old gold but App returns the original error before you get to Scan for Games through settings.
The above will remove Agent.exe's game installation info, so you will then have to go to Settings -> Game Install/Update and click Scan for Games to have it repopulated.
I see the bug for this issue: Bug 51331 is marked as resolved. Will that patch be part of 6.13?
by Maciej Stanczew on Thursday July 22nd 2021, 12:11
Fix was introduced to Wine code after 6.12, so it's included in 6.13 (I just verified that on Staging 6.13 Battle.net App works normally).
by spaceman on Friday July 23rd 2021, 4:57
by Pavel R on Wednesday August 4th 2021, 0:10
by Maciej Stanczew on Wednesday August 4th 2021, 13:37
by Pavel R on Friday August 6th 2021, 9:17
BTW, using Fedora 33 with Mate desktop, winehq-staging from WineHQ Fedora repos.
by Maciej Stanczew on Friday August 6th 2021, 14:54
by Steve Ebey on Saturday May 15th 2021, 23:49
by Alexey on Thursday November 26th 2020, 13:53
I have:
Linux Mint 19.2 MATE x64
NVidia Drivers 455.45.01 (GeForce GTX 1050 Ti) - installed
Wine 5.0.3 - installed
PlayOnLinux 4.3.4 - installed (have error "PlayOnLinux is unable to find 32bits OpenGL libraries")
Winetricks - installed
Battle.net have error BLZBNTBTS0000005C under wine 5.2.0-staging (or system or 5.2.0 or 3.2.0...)
eu.battle.net/support/ru/article/19031 - did not help
Can someone help me to solve this problem?
Regards, Alexey.
by Alexey on Saturday November 28th 2020, 2:28
Regards, Alexey.
by Lucas Pruvost on Wednesday November 25th 2020, 1:52
An easy fix is to go to the settings of the app and in the general tab uncheck "Use browser hardware acceleration when available", the settings page is displaying correctly.
The app will then restart and be fully available.
by Stefan on Wednesday October 14th 2020, 12:26
Not a big deal so far, since I could just use wow-staging-5.8 and 5.10.
But with the WoW Shadowlands prepatch WoW crashes with these wine-staging versions. I found some users report 5.18 and 5.19 work for them.
So I tried again and just as before: battle.net will not start, it'll sort of time out and after a minute the afore mentioned error pops up.
The funny thing is: Since some of the reports of "WoW SL pre-patch works with 5.19" I found were on the lutris site, I dowloaded lutris and had lutris install battle.net and wow again and lo and behold: That works.
But: I don't like using lutris, I much rather take care of my prefix myself. So I'd like to get my prefix to work with 5.19 too. Looking at the lutris install files for WoW and Battle.net nothing really strikes me as: Now that's keeping battle.net agent from being able to connect/launch!
That being said I tried the following: I
- changed my prefix from Win7 to Win10 (lutris has it set to Win10)
- used winetricks winhttp and wininet
- manually added all the dll-overrides lutris sets
- added the string "backend" with value "va" to the key HKEY_CURRENT_USER\Software\Wine\DXVA2 (taken from the lutris script)
- vimdiffed $GAMEDIR/drive_c/users/$USER/Application Data/Battle.net/Battle.net.config with mine and applied the changes to mine.
After each step I used wineboot -r in my prefix and tried to run the battle.net client. And it still doesn't work.
Wtf is Lutris doing differently?
by Maciej Stanczew on Saturday October 17th 2020, 5:49
bugs.winehq.org/show_bug.cgi?id=49590
bugs.winehq.org/show_bug.cgi?id=49712
but the first one was introduced in 5.13 and fixed in 5.14, and the second one introduced in 5.15 and fixed in 5.16 � so 5.14 should not be impacted by any of those.
Are you using Staging 5.19? There are some Staging patches that are required for Blizzard games to work, maybe they also impact Battle.net app.
Also, do you have a PE build of Wine? Lately a lot of Wine libraries were converted to PE format, and using a non-PE build will break a lot of games: bugs.winehq.org/show_bug.cgi?id=45349
by b0nt4kun on Saturday October 17th 2020, 7:35
Creating a fresh wine prefix for it worked immediately with only wine 5.19 and staging patches (no winetricks), but build with PE support (requires mingw crossdev compiler)
by Panos on Monday March 16th 2020, 16:30
Since patch 8.3 in WoW i had random freezes during the game. These freezes were so severe that i had to restart my PC, making the game unplayable. So I decided to make a new installation on PlayOnLinux and use the latest versions of Wine and dxvk (5.2 and 1.5.5 respectively).
Battle.net applications starts, i make the login but I have a black screen and an erron message that the application couldn't establish a graphic enviroment, prompting me to either exit or restart Battle.net. I remembered the same problem last winter with the white screen and i made the overides on api-ms-win-crt-private-l1-0-0 and ucrtbase but the problem persists. WoW works fine and without freezes with WineStaging 5.2, but without a working version of Battle.net I can't update the game.
So I decided to use the my previous drive with Wine Staging 4.3 to start Battle.net and use the WineStaging 5.2 to run WoW. But to my surprise the black screen migrated there also. Battle.net starts with Wine Staging 4.3 but the black screen follows.
I use a common folder with all the applications (Battle.net, WoW, Hearthstone) so that I don't "install" the games all the tine.
Any thoughts?
by MikeTechno on Thursday October 17th 2019, 23:37
imgur.com/a/yfexiA3
MacBook Pro 15 (2019) 2.6 Ghz w Radeon Pro 555x
by MikeTechno on Saturday October 19th 2019, 14:16
by Maciej Stanczew on Sunday October 20th 2019, 2:52
by MikeTechno on Sunday October 20th 2019, 9:58
by MikeTechno on Sunday October 20th 2019, 10:13
by Frank on Friday October 11th 2019, 12:49
TLDR, add api-ms-win-crt-private-l1-1-0 and ucrtbase to the winecfg Libraries list as native first.
by sh0gunai on Saturday October 12th 2019, 15:14
by Pawel Wiecha on Tuesday October 15th 2019, 14:38
by Maciej Stanczew on Sunday October 20th 2019, 3:02
I've added this info to Troubleshooting Notes.
by Maciej Stanczew on Sunday December 8th 2019, 16:48
For now everything works � the white screen problem seems to have been fixed, either on Wine/Staging or Battle.net part.
by JimB on Saturday July 27th 2019, 12:17
by JimB on Saturday July 27th 2019, 14:49
by Christian Widmer on Monday July 29th 2019, 11:17
[1] www.reddit.com/r/wine_gaming/comments/chizv8/battlenet_black_screen_help/
by Niklas Hambuechen on Tuesday August 6th 2019, 18:03
by illich on Sunday January 6th 2019, 8:34
www.reddit.com/r/linux_gaming/comments/acb4vm/battlenet_crashes_with_wine40rc4_staging_and/
Happens to me too.
Without DXVK, Battle.net runs.
After installing DXVK (either through Lutris or manually), Battle.net crashes immediatelly after login :(
Kubuntu 18.10, Nvidia 410, wine-4.0-rc4.
by Maciej Stanczew on Sunday January 6th 2019, 15:15
Are there any specific errors in the logs when it crashes?
Did it start happening recently? If so, was it after Wine update, DXVK update, or something else in the system?
Also, do you have every library installed like described in Lutris wiki[1][2]?
[1] github.com/lutris/lutris/wiki/Game:-Blizzard-App
[2] github.com/lutris/lutris/wiki/How-to:-DXVK
by chlenorub on Monday January 7th 2019, 8:41
Downgrading DXVK to 0.92 fixes this. (arch 4.19, wine 4.0-rc3, mesa 18.3)
by chlenorub on Monday January 7th 2019, 9:55
So options are - downgrade to 0.93 and earlier, compile master version or just wait till 0.95
by spaceman on Friday April 26th 2019, 12:58
by Markus Linnala on Tuesday September 18th 2018, 10:33
by Maciej Stanczew on Tuesday September 18th 2018, 16:38
You could try synchronizing your clock on both PC and authenticator.
Another idea to try would be to wait for a bit before clicking "Approve".
If everything fails, then I guess manually entering the code is the only option left.
by Brandon on Thursday September 13th 2018, 20:39
I tried uninstalling BattleNet completely and reinstalling, but it still won't work. Now I'm stuck with 10532 that keeps crashing and no 10491 to fall back on.
by Maciej Stanczew on Friday September 14th 2018, 1:52
2. Can you post your installed lib32- packages? I'm on Arch and I don't have any issues with 3.15 + 10532.
3. Anything shows up in the logs when the app crashes?
by Brandon on Friday September 14th 2018, 2:19
Here are my lib32- packages:
$ pacman -Qs lib32-* | grep 'lib32-'
local/lib32-acl 2.2.53-1
local/lib32-alsa-lib 1.1.6-1
local/lib32-alsa-plugins 1.1.6-1
local/lib32-atk 2.28.1-1
local/lib32-attr 2.4.48-1
local/lib32-bzip2 1.0.6-3
local/lib32-cairo 1.15.12-1
local/lib32-curl 7.61.1-1
local/lib32-db 5.3.28-4
local/lib32-dbus 1.12.8-1
local/lib32-e2fsprogs 1.44.4-1
local/lib32-expat 2.2.6-1
local/lib32-flac 1.3.2-1
local/lib32-flex 2.6.4-1
local/lib32-fontconfig 2:2.13.0+15+gc60ed9e-1
local/lib32-freetype2 2.9.1-1
local/lib32-fribidi 1.0.5-1
local/lib32-gcc-libs 8.2.1+20180831-1 (multilib-devel)
local/lib32-gdk-pixbuf2 2.36.12-1
local/lib32-gettext 0.19.8.1-1
local/lib32-glew 2.1.0-1
local/lib32-glib2 2.56.2-1
local/lib32-glibc 2.28-4
local/lib32-glu 9.0.0-4
local/lib32-gmp 6.1.2-1
local/lib32-gnutls 3.5.19-1
local/lib32-gtk2 2.24.32-1
local/lib32-harfbuzz 1.8.8-1
local/lib32-icu 62.1-1
local/lib32-intel-tbb 2018_20180618-1
local/lib32-jack 0.125.0-2
local/lib32-keyutils 1.5.11-1
local/lib32-krb5 1.16.1-1
local/lib32-lcms2 2.9-1
local/lib32-libaio 0.3.111-1
local/lib32-libasyncns 0.8+3+g68cd5af-1
local/lib32-libcanberra 0.30+2+gc0620e4-1
local/lib32-libcanberra-pulse 0.30+2+gc0620e4-1
local/lib32-libcap 2.25-1
local/lib32-libcups 2.2.7-1
local/lib32-libcurl-compat 7.61.1-1
local/lib32-libcurl-gnutls 7.61.1-1
local/lib32-libdatrie 0.2.12-1
local/lib32-libdrm 2.4.94-1
local/lib32-libelf 0.171-1
local/lib32-libffi 3.2.1-2
local/lib32-libgcrypt 1.8.3-1
local/lib32-libglvnd 1.1.0-1
local/lib32-libgpg-error 1.32-1
local/lib32-libice 1.0.9-3
local/lib32-libidn 1.33-1
local/lib32-libidn2 2.0.5-1
local/lib32-libjpeg-turbo 1.5.3-1
local/lib32-libldap 2.4.46-1
local/lib32-libltdl 2.4.6+40+g6ca5e224-4 (multilib-devel)
local/lib32-libnl 3.4.0-1
local/lib32-libogg 1.3.3-2
local/lib32-libpcap 1.9.0-1
local/lib32-libpciaccess 0.14-1
local/lib32-libpng 1.6.34-1
local/lib32-libpsl 0.20.2-1
local/lib32-libpulse 12.2-1
local/lib32-libsamplerate 0.1.9-1
local/lib32-libsm 1.2.2-2
local/lib32-libsndfile 1.0.28-1
local/lib32-libssh2 1.8.0-2
local/lib32-libtasn1 4.13-1
local/lib32-libthai 0.1.27-1
local/lib32-libtiff 4.0.9-1
local/lib32-libtxc_dxtn 1.0.1-5
local/lib32-libunistring 0.9.10-1
local/lib32-libusb 1.0.22-1
local/lib32-libvorbis 1.3.6-1
local/lib32-libx11 1.6.6-1
local/lib32-libxau 1.0.8-2
local/lib32-libxcb 1.13-1
local/lib32-libxcomposite 0.4.4-3
local/lib32-libxcursor 1.1.15-1
local/lib32-libxdamage 1.1.4-3
local/lib32-libxdmcp 1.1.2-2
local/lib32-libxext 1.3.3-2
local/lib32-libxfixes 5.0.3-1
local/lib32-libxft 2.3.2-2
local/lib32-libxi 1.7.9-1
local/lib32-libxinerama 1.1.3-2
local/lib32-libxml2 2.9.8-3
local/lib32-libxmu 1.1.2-2
local/lib32-libxrandr 1.5.1-1
local/lib32-libxrender 0.9.10-1
local/lib32-libxshmfence 1.3-1
local/lib32-libxss 1.2.2-3
local/lib32-libxt 1.1.5-2
local/lib32-libxtst 1.2.3-1
local/lib32-libxxf86vm 1.1.4-2
local/lib32-llvm-libs 6.0.1-1
local/lib32-lm_sensors 3.4.0-1
local/lib32-mesa 18.1.8-1
local/lib32-mesa-demos 8.4.0-1
local/lib32-ncurses 6.1-2
local/lib32-nettle 3.4-1
local/lib32-nvidia-cg-toolkit 3.1-5
local/lib32-nvidia-utils 1:396.54-2
local/lib32-openal 1.18.2-1
local/lib32-openssl 1:1.1.0.i-1
local/lib32-openssl-1.0 1.0.2.p-1
local/lib32-p11-kit 0.23.14-1
local/lib32-pango 1.42.4-1
local/lib32-pcre 8.42-1
local/lib32-pixman 0.34.0-1
local/lib32-portaudio 190600_20161030-1
local/lib32-readline 7.0.003-1
local/lib32-sdl2 2.0.8-9
local/lib32-soundtouch 2.0.0-1
local/lib32-sqlite 3.24.0-1
local/lib32-systemd 239.2-1
local/lib32-tdb 1.3.15-2
local/lib32-util-linux 2.32.1-1
local/lib32-wayland 1.16.0-1
local/lib32-wxgtk2 3.0.4-1
local/lib32-xz 5.2.4-1
local/lib32-zlib 1.2.11-1
As for logs, I'm not sure where to check for the logs.
by Brandon on Saturday September 15th 2018, 3:34
I had used winetricks to install dxvk in order to play Overwatch. I found out in the prior version that I had to set Agent.exe to use the builtin dxgi instead of native, but apparently in the current version of BattleNet I have to set the Battle.Net Launcher and Battle.Net.exe to use builtin dxgi, as well.
by Maciej Stanczew on Tuesday September 18th 2018, 16:48
Can you try installing and running the app in a clean wineprefix with no DLL overrides? Or just removing all DXGI overrides in your current prefix – what will be the result?
by Brandon on Friday September 21st 2018, 18:38
But Battle.Net runs fine with this setup, as does Overwatch (or at least as good as Overwatch works in Wine so far). I may even try HotS next.
by Storm Engineer on Wednesday September 12th 2018, 9:24
by Calmarius on Thursday September 6th 2018, 17:52
Now Battle.net no longer starts, it just crashes. Hearthstone no longer starts because it attempts to start battle.net which is then crashes so it exits...
I deleted my ~/.wine and attempted to reinstall battle.net now fails to connect to the update agent. Internet searches are useless, because everyone else in the world uses Windows and it doesn't apply to wine. And it seems it works for everyone else in this thread, except me in the entire world.
by Maciej Stanczew on Thursday September 6th 2018, 18:24
bugs.winehq.org/show_bug.cgi?id=45764
(There are also a couple of comments below by the submitter of this bug.)
by Maciej Stanczew on Thursday September 6th 2018, 19:08
by Florian on Saturday September 8th 2018, 10:07
I reverted the upgrade and now battle.net starts again. I more or less the following command to revert the upgrade:
sudo apt-get install wine-devel-amd64=3.13.0~xenial wine-staging-amd64=3.13.0~xenial winehq-staging=3.13.0~xenial wine-staging=3.13.0~xenial wine-staging-i386=3.13.0~xenial
I didn't had to do anything else to get it working.
by FlagDUDE08 on Monday September 10th 2018, 15:08
by Maciej Stanczew on Monday September 10th 2018, 15:26
Could someone using Ubuntu try compiling Wine and do a regression bisection of commits between 3.14 and 3.15? wiki.winehq.org/Regression_Testing
by Maciej Stanczew on Wednesday September 12th 2018, 11:18
If it doesn't help, the bug should probably be reopened.
bugs.winehq.org/show_bug.cgi?id=45764
by spaceman on Thursday September 6th 2018, 6:32
I only use the Blizzard App to install updates, so I am very impressed with someone else's suggestion that "most people still log in through Battle.net App." I never actually use the App to launch a game because Battle.net doesn't run with dxvk (for me) so I run it in its own prefix so game performance would be awful if I did launch games. I suspect I am not alone. I have written a script to "repair" the App and killall the Battle.net / agent.exe processes, then delete product.db, however given how badly the app works I might save myself a lot of wasted time and incorporate it into a startup script that deletes the product.db before each start up, then I only have to locate the game folder and update.
I will submit Staging 3.15 test results to detail my setup so welcome suggestions and feedback. Thanks all.
by Maciej Stanczew on Thursday September 6th 2018, 12:34
But isn't it true? It's still easier to launch games from the app instead of from specific game launchers, and for some games (Hearthstone) this is the only way to run them.
I just delete product.db when I need to update, and use the app normally (fwiw) all the other time.
> Battle.net doesn't run with dxvk (for me)
In the test result you list Nvidia driver 396.24 – this version is missing quite a lot of Vulkan-related stuff. You should try updating to at least 396.45.
For example, I remember 64-bit Diablo III with DXVK didn't launch at all on 396.24 – it started working only after update to 396.45. Currently I'm on version 396.54 (on GTX 1060, so similar to yours), and I have no problems running Battle.net with DXVK, in the same wineprefix as all other Battle.net games.
(Also, it should be possible to override DXVK DLLs to "builtin" just for Battle.net app – then all games would use DXVK, but the app would not.)
by spaceman on Thursday September 6th 2018, 12:47
I shall try your other suggestions and report back. Very many thanks.
by Maciej Stanczew on Thursday September 6th 2018, 14:56
> takes an age to load
For me it's 8 s from clicking the icon to fully loaded app; but I remember seeing someone else having this problem.
> doesn't shutdown cleanly
I'm seeing this, but quite rarely, and only after the update problem occurs (e.g. when I click "Check for updates" and it spins forever). In all other cases it exits cleanly (although – by design – it takes a couple of seconds for Agent.exe to shutdown).
This was happening always in Wine Staging 2.19, but starting from 3.3 it stopped occuring for me (see bug #44024, this was also confirmed by submitter to no longer occur).
Maybe those problems are distro / library version / configuration dependent? There has to be a reason for such vastly different behavior… but I guess debugging it would require quite a lot of effort.
Still, I think we should include information about (at least) distro used when describing issues we experience. Maybe we could then find a common denominator for some of the issues.
by spaceman on Saturday September 8th 2018, 8:16
Today I've managed to sort my stupidity out and built antiX on a Debian Stable base with the 396.54 driver set...if I ever get Wine working again (dependency problems!) I can test Battle.net...with and without dxvk, which I simply couldn't get working on Fedora 28 for love nor money. In frustration I turned to Ubuntu, as with it's huge software repo, Windows-like weight and approach, vast community and endless wordpress guides, I thought that I should be able to get something working...I impressed myself trashing a Xubuntu 17:10 install so soundly.
AntiX Core is a minimal distro (there is no X at install) which I love because I can then build up packages on a *need only* basis. The obvious problem with this approach is not always being able to establish which packages are needed in any case. This should be easier but, of course, this is the real world.
by Michael Goetze on Wednesday September 5th 2018, 19:00
It seems everyone else is just logging in via some game? This doesn't seem to be an option for Hearthstone, so which game would I need to install to log in?
by Maciej Stanczew on Wednesday September 5th 2018, 19:14
Logging in directly through games is possible for some of them, but most people still log in through Battle.net App.
Have you tried Staging 3.14/3.15? Do you have lib32-libldap and lib32-gnutls installed?
by Michael Goetze on Wednesday September 5th 2018, 19:22
by Finn Brinkmann on Thursday September 20th 2018, 8:41
by muke on Sunday September 2nd 2018, 15:49
and this seems to have got me past the black screen. I'm still getting errors as it stands right now, but so far I'm going to assume these are different errors as there are actual graphics now. Hope this helps people.
by muke on Sunday September 2nd 2018, 15:50
by Sveinar S�pler on Sunday September 2nd 2018, 14:17
Wine-staging-3.14 works like it use to, but 3.15 crashes with a nasty segfault for some reason.
by Maciej Stanczew on Sunday September 2nd 2018, 14:23
by Sveinar S�pler on Sunday September 2nd 2018, 14:59
us.battle.net/support/en/article/18771
by Adrian Demarais on Wednesday September 5th 2018, 11:42
The clickable area of all the side buttons is now approx two buttons lower than the displayed button.
For the top row, clickable area is now a few buttons to the right.
This forces one to resize battle.net's window vertically, dragging bottom edge down until the clickable area of the START button is within the window's border.
Virtual desktop or own windows matters not, same behaviour in both.
Happily, the main World of Warcraft game window works fine.
I hope this gets fixed soon; have been considering trying a rollback to 3.14.
4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Radeon HD-5670
by Sveinar S�pler on Wednesday September 5th 2018, 16:32
Did not notice any button problems tho...
by dopella on Wednesday August 22nd 2018, 19:59
by Maciej Stanczew on Thursday August 23rd 2018, 2:29
by dopella on Friday August 24th 2018, 8:28
Actually, I had to reinstall the OS later that day, and now, doing exactly the same, I can't even run the app. Installed it using 3.1.4-staging, and it will refuse to run, throwing:
wine: Unhandled exception 0x40000015 in thread 30 at address 0x494f73 (thread 0030)
Any ideas?
by dopella on Friday August 24th 2018, 8:34
by feliks on Sunday August 19th 2018, 14:35
it gives the message Game is Running. but it doesn't start and the button returns available again
by Maciej Stanczew on Sunday August 19th 2018, 19:46
by feliks on Tuesday August 21st 2018, 7:26
I'am trying now to 'Scan and Repair' starcraft. Will report when possible.
by feliks on Thursday August 23rd 2018, 8:17
So it does start the program but window doesn't show up.
by Maciej Stanczew on Thursday August 23rd 2018, 12:19
You can find more information on Starcraft's page: appdb.winehq.org/objectManager.php?sClass=version&iId=35645
by feliks on Monday August 27th 2018, 10:44
I had development version which I thought was the same as Staging but it is not.
The next problem was that I couldn't create a character because I didnt't have permission
to write in Starcraft directory.
SOLVED: indeed My Documents/StarCraft directory needed root permission, had to change permissions.
Now it is correctly working
by feliks on Saturday August 18th 2018, 6:33
Anyone else with this problem?
I have installed dlls:
atl80
msvcm80
msvcp80
msvcr80
vcomp
api-ms-win-crt-heap-l1-1-0
api-ms-win-crt-locale-l1-1-0
api-ms-win-crt-runtime-l1-1-0
api-ms-win-crt-stdio-l1-1-0
d3d11
ucrtbase
vcruntime140
by Maciej Stanczew on Saturday August 18th 2018, 6:45
I remember I've seen those 2 white boxes a long time ago on vanilla Wine. New versions, both vanilla and Staging, should work without major issues.
Also, all of those DLL overrides should not be required anymore.
by feliks on Saturday August 18th 2018, 12:31
by Maciej Stanczew on Saturday August 18th 2018, 13:55
by feliks on Sunday August 19th 2018, 7:27
Thank you very much, indeed now I can see buttons and everything.
Now my new problem is that I'am stuck on the Installation window.
I clicked on 'Play Now' for Starcraft, it opened the installation window,
which simply has a loading logo which keeps spinning.
by Maciej Stanczew on Sunday August 19th 2018, 7:50
by feliks on Sunday August 19th 2018, 8:52
Thank you very much, again!
by feliks on Sunday August 19th 2018, 9:57
but in reality it is stuck saying "Waiting..." after I said to download the game.
I waited a lot of time but it's still stuck
by feliks on Sunday August 19th 2018, 10:52
by Maciej Stanczew on Sunday August 19th 2018, 19:51
by Aleks on Thursday August 9th 2018, 3:59
I use PlayOnLinux frontend.
In mid-July, I logged out of BlizzardApp and I was not able to log in again.
No big deal, I login via SC2 itself.
Up until version 4.5 of SC2, on August 8th.
SC2 needs an update and tells me to update it from BlizzardApp, where I was never able to log in.
I wasn't able to install corefonts. Or I don't see arial in the registry editor.
Out of despair I create a new prefix and install new BlizzardApp. No login yet.
Somehow I decided to point the new installation the data folder of SC2, the one with 28Gb of data.
And I see "Initializing" progress bar.
After some 20 minutes or thereabouts, I see the play button and a text that the version is now 4.5.
So pointing the client to a data folder forces it to update the game, even without logging in.
Now I can play SC2 again!
Hope that helps someone. Don't hesitate to drop a simple "thanks" line here.
by Angus on Friday August 3rd 2018, 19:47
Clean new WinePrefix with WINEARCH=win32.
Installed corefonts, ie8 and VC2015. No DLL overrides installed.
Updated the Battlenet config file to disable hardware acceleration but still no dice. Not sure what else to try.
by Maciej Stanczew on Friday August 3rd 2018, 20:07
Regarding clicking buttons, please see bug #33943; try to move your mouse down after you click, the menu should show up then.
Also make sure to set Windows version to Win 7, as installing ie8 will set it back to Win XP.
by Angus on Friday August 3rd 2018, 21:00
Hope this helps someone! :)
by Maciej Stanczew on Saturday August 4th 2018, 4:01
by Maciej Stanczew on Tuesday July 31st 2018, 15:17
This can mostly be mitigated by killing Agent.exe while installation window is shown, but it doesn't seem to always work [1].
Another option is removing "C:\ProgramData\Battle.net" directory before launching Battle.net App – but this is also not permanent (the problem will reappear after restarting the app).
[1] www.reddit.com/r/wine_gaming/comments/92l58n/problems_installing_wow_with_lutris/e37aizw/
by Maciej Stanczew on Thursday August 2nd 2018, 16:26
Regarding above workaround with deleting files: the problematic file seems to be "C:\ProgramData\Battle.net\Agent\product.db", which contains information about installed games. Moving/deleting the file makes the issue go away temporarily.
As a side effect of removing this file, information about installed games is lost. One needs to go into Settings -> Game Install/Update -> Scan for Games to detect already installed games.
by K-M. Knaak on Sunday August 12th 2018, 13:56
Finally, I got the install working. Apparently, vcrun2015 installed with winecfg did the trick. In my previous fresh install trials I had chosen vcrun2017 because newer is supposed to be better...
WINEPREFIX=/home/$USER/bnet/ winetricks
→ select default wine prefix
→ install a Windows DLL or component
→ vcrun2015
by Maciej Stanczew on Sunday August 12th 2018, 14:39
I don't know if installing vcrun2015 and then setting the version back to Win 7 fixes the install/update issue, since it comes and goes away randomly for me.
by evilny0 on Friday August 17th 2018, 13:51
by K-M. Knaak on Sunday August 19th 2018, 18:27
There is a hint by Maciej Stanczew two sections above:
* close BN completely (wineserver -k to make sure), delete "C:\ProgramData\Battle.net\Agent\product.db", and then start BN again.
by Maciej Stanczew on Sunday August 19th 2018, 20:14
I'm trying to see any patterns here, but for now it seems that sometimes Agent.exe just "decides" to break, and that it's somehow connected to product.db (which contains information about installed games, their versions, and more).
I have added a note explaining known workarounds for this issue. As mentioned there, if anyone stumbles upon some new information related to this problem, please make a comment here.
Also one interesting thing is that I think I saw the problem on Windows when I launched BN there about a week ago. But after removing product.db once, the issue went away, and didn't return that day. I had no way to check it since then, so I can't really confirm this.
by aaahaaap on Wednesday August 22nd 2018, 12:44
The workaround as described (delete product.db, then scan) works. Immediately after scanning the update was downloaded and checking for updates works again as well. Thanks!
by Josh R Raymond on Tuesday August 28th 2018, 17:26
by Maciej Stanczew on Wednesday August 29th 2018, 0:46
by spiritsc on Monday July 30th 2018, 20:51
msvcp140(Native, Builtin)
vcruntime140(Native, Builtin)
Worked, took some time to load but worked just fine.
by Maciej Stanczew on Tuesday July 31st 2018, 15:00
by Mike Swi on Tuesday July 10th 2018, 9:00
I'm running Wine 3.11-staging on Ubuntu Mate 18.04. AMD FX-8320 CPU, AMD Radeon HD 5770 video card, open source drivers. Setting "Enable_VAAPI as backend for DXVA2 GPU decoding" enabled, no winetricks config set. Wine set to Windows 7.
Some combination of the following two changes fixed it:
1. Per zen's earlier comment, I disabled hardware acceleration for Battle.net in the .config file.
2. I downgraded my kernel to 4.12.10-041210-generic (which, unfortunately, is old) but the linux-image-4.15.0-23-generic kernel installed when I upgraded to 18.04 did not work. If I can get it to work with a newer kernel, I will report back.
by Michiel on Friday July 6th 2018, 4:17
Anyone else noticed this and knows a cure?
Currently on wine 3.11-staging, on Slackware 14.2 core fonts and all winetricks outlined in the howto's are done. Eventually everything works, but it just takes very long.
Another thing I notice is the amount of cpu that is eaten by the app (and since I use AMD this becomes a thermal thing :-( I have no idea why it needs so much cpu power)
by asasaa on Wednesday June 13th 2018, 15:21
Any idea? When I try now to reinstall the battle.net client from .exe the computer freezes
by Carbone on Tuesday May 29th 2018, 16:27
after an update, I tried to reinstall battlenet besause of a missing dll. I deleted end created a new wineprefix, installed battlenet but I had the same error
Here are my specs :
Ubuntu 16.04.01 64bit
Wineprefix 32bit 2.21-staging (with CSMT enabled)
My winecfg is set with Windows 7 version
Thx for the help
by Jeff Hoogland on Tuesday May 29th 2018, 18:56
by Jeff Hoogland on Tuesday May 29th 2018, 19:07
by Lukas on Friday June 1st 2018, 13:32
You need to install the following libraries:
msvcp140(Native, Builtin)
vcruntime140(Native, Builtin)
After that it runs fine for me
by Stefan on Saturday May 26th 2018, 5:36
The workarounds stopped working for me a really long time ago (hard to say exactly, feels like years, but months for sure).
A while ago I figured out that installing corefonts with winetricks let me log in. But the fonts then look crappy compared to using the microsoft-ttf-fonts installed on my system.
So yeah, I guess my questions are:
- anyone else having the same issue with the spinning logo and the known workarounds don't work?
- if so, would you test winetricks corefonts?
by Stefan on Saturday May 26th 2018, 6:55
Anyhow, just as I said, winetricks corefonts makes the fonts look ugly on my system so I don't really want that. I've been looking into the winetricks script, seems like the installation of the fonts is copying the ttf files to $wine_dir/drive_c/windows/Fonts and then changing the path for every font in [HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows NT\\CurrentVersion\\Fonts] as well as [HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Fonts] to the c:/windows/Fonts/fontname.
So if I backed up the corresponding keys in [HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows NT\\CurrentVersion\\Fonts] and [HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Fonts] (or simply all of them so I don't have to manually find and export the 29 fonts wintricks installs) now, then winetricks corefonts, log into battle.net to get my magic token for the next year or so back, then manually rm the fonts from c:/windows/Fonts and use my registry backups the fonts should be completely uninstalled, right? Or am I missing something in the script? because I really want every trace from the winetricks corefonts gone when I'm done.
by Stefan on Saturday May 26th 2018, 12:53
1 I downloaded the arial32.exe and arialb32.exe (link in the winetricks script)
2 cabextracted the ttfs
3 fired up regedit in my prefix, navigated to HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows NT\\CurrentVersion\\Fonts and changed the values of the 5 Arial keys from "\\?\unix\path\to\font\ArialXYZ.ttf" to "ArialXYZ.ttf"
4 copied the 5 ttf files to windows/Fonts
5 started battle.net, logged in, then shut wine down
6 reverted the values in the registry so they would again point at the font files on my "host" system
7 deleted the fonts from windows/Fonts (probably optional if you want to be prepared for whenever your magic token from battle.net expires and you need to log in again)
Things to mention:
- do the regedit before you copy the ttf files! If they are present in windows/Fonts then they won't show up in the registry anymore.
- I accidentally only changed the keys in HKLM\\.......\Windows NT\... and not also in HKLM\\........\Windows\... . I meant to change the Arial keys in either location, but I forgot. The changes in Windows NT were enough in my case for the launcher log in to work.
- winetricks corefonts installs a bunch of fonts. In bug 32342 someone mentioned it's due to Arial and Times New Roman. I purposely tried only Arial (from arial32.exe and arialb32.exe) and it was enough in my case.
- if changing only Arial doesn't do the trick for you, then winetricks corefonts, start battle.net, log in, exit battle.net and kill remaining processes of it, then regedit and re-set the values of the 29 installed fonts so they point to your host system again in both HKLM\\.....Windows\... and HKLM\\...Windows NT\\..., then remove the ttf-files from windows/Fonts
- on my system the battle.net launcher starts a lot faster with winetricks corefonts. Just looks a little weird (letter spacing questionable I think), so I prefer to use the ttf from my host system.
And can someone with more knowledge please explain to me how a fricken font can have such an impact?
May my trials and errors help someone else as well.
Cheers
by Roland D on Tuesday July 3rd 2018, 17:43
by DeeDee Ranged on Monday May 14th 2018, 7:27
Instead of starting the "Battle.net Launcher.exe" just start it with "Battle.net.exe". Only thing I encountered was the SystemSurvey crash, but I resolved that by just renaming it.
"Battle.net.exe" does also run with wine64.
Tested it on 2 systems,
notebook y50-70 16GB mem, nvidia gtx860m, Debian stretch 64bit, wine-staging 3.7, had to set graphics setting in game to 4 (recommended was 6, way to slow) 35-60 fps.
desktop amd fx-8320, 16GB mem, nvidia gtx1070, Debian buster 64bit, wine-staging 3.7, had to set graphics setting in game to 2 (recommended was 7, slow as hell) 27-60 fps.
All set to Windows 7 and no overrides.
If anyone can explain why the gtx1070 is slower than the gtx860m in my notebook your welcome.
Tried wine-staging 3.8 but had to revert to 3.7 due to very low fps 2-5 while I had 30-
by Alberto on Tuesday May 15th 2018, 3:56
by Maciej Stanczew on Tuesday May 15th 2018, 11:34
by Alberto on Tuesday May 15th 2018, 11:38
appdb.winehq.org/objectManager.php?sClass=version&iId=33768
by spaceman on Wednesday May 16th 2018, 3:57
by spaceman on Wednesday May 16th 2018, 4:13
by Xantek on Friday May 4th 2018, 14:25
by spaceman on Wednesday May 9th 2018, 15:12
WINEPREFIX="/home/spaceman/.bnet" wine wineboot
Then launch battle.net "in that PREFIX":
WINEPREFIX="/home/spaceman/.bnet" wine "/${YOURPATH}/Battle.net/Battle.net.exe"
by spaceman on Wednesday May 9th 2018, 15:14
by UniMaX on Saturday April 21st 2018, 12:36
by zen on Monday February 26th 2018, 12:44
Add
"HardwareAcceleration": "false",
to "Client" section in file
$WINEPREFIX/users/$(whoami)/Application\ Data/Battle.net/Battle.net.config. You have to get something like that:
{
"Client": {
"HardwareAcceleration": "false",
"Version": {
"FirstRun": "false",
"Release": {
"FirstRun": "false",
"LastBuildVersion": "9854",
"LastSeenPatchNotesVersion": "9854"
}
},
by Oliver Sperke on Saturday February 24th 2018, 7:15
by spaceman on Sunday February 11th 2018, 7:57
$ wine --version
wine-2.21 (Staging)
What graphics drivers are you using? Have you tried a new wineprefix? Do you have any dll overrides, have you tried it without? "I also get a systemsurvey.exe error every time I start battle.net." I think we all do this doesn't affect performance at all.
"Battle.net Helper.exe goes full retard." I have no idea what that means. Battle.net frequently crashes on me I have kill agent.exe, Blizzard Battle.net and Battle.net Helper.exe in order to get it to launch again.
by Scottie on Thursday February 8th 2018, 6:42
You have to hit the settings icon, that's where the 'continue without logging in' button is, in case anyone was having difficulties.
by Scottie on Thursday February 8th 2018, 6:27
I can log in just fine from within the game, but not through the launcher. Not really a big deal. To stop the display of these stupid error messages I just went into the install folder and appended '.cpy' to both the battle.net helper.exe file and the systemsurvey.exe file. Since both crash themselves and I can still play, they obviously aren't serving that much of a function.
No more error messages, the game works just fine. Sure, you have to hit 'continue without logging in', but it does work.
by Storm Engineer on Tuesday February 6th 2018, 11:20
I disabled hardware acceleration but it didn't help.
by Storm Engineer on Tuesday February 6th 2018, 11:31
"Failed to create a graphics context"
us.battle.net/support/en/article/12706
by Storm Engineer on Tuesday February 6th 2018, 13:32
Downgraded the nVidia driver and the kernel (was required for the nvidia downgrade) and the issue is fixed!
Downgraded:
nvidia-390.25-4-x86_64 > nvidia-387.34-21-x86_64
nvidia-utils-390.25-2-x86_64 > nvidia-utils-387.34-5-x86_64
linux-4.15.1-2-x86_64 > linux-4.14.15-1-x86_64
So it's a bug with the driver then?
by Maciej Stanczew on Tuesday February 6th 2018, 13:49
by Storm Engineer on Saturday February 10th 2018, 6:29
by Matt Spraggs on Sunday February 11th 2018, 7:06
I'm experiencing the same problem as you and probably everyone else (i.e. the perpetually-spinning login logo). You say you created a fresh wine prefix. Could you provide some deets? Which wine version did you install, and which architecture (i386 or amd64)? Also which distro are you running?
Thanks,
Matt
by spaceman on Tuesday February 6th 2018, 10:00
Battle.Net itself is extremely unstable and I would question whether this even deserves the Silver rating. It's constantly crashing, you then have kill the process, kill the Agent.exe process and relaunch. It's beyond irritating this application needs some love.
by Jon Rayner on Wednesday January 31st 2018, 1:26
Archlinux x86_64 4.14.15-1
wine-staging 2.21-1
lib32-libldap lib32-gnutls installed (and many other 32-bit libraries installed, as per randomly following advice from several other places)
Have tried with/without all combinations of
WINEPREFIX=/home/****/bnet winetricks corefonts fontsmooth=rgb
WINEPREFIX=/home/****/bnet winetricks vcrun2015
WINEPREFIX=/home/****/bnet winetricks vcrun2017
with Win 7 and Win 10 in winecfg (because some users here and on reddit have reported not needed to use winetricks at all in recent versions). Fresh wineprefix between each try. No success.
Have also tried manually added/removed certain dlls as per other older recommendations on other sites. Fresh wineprefix between each try. No success.
Fresh wineprefix for the purpose of logs for this comment. Running
WINEPREFIX=/home/****/bnet winecfg
gives: pastebin.com/i5T6FMmX
Settings Windows 10 and clicking apply, then following op and running
WINEPREFIX=/home/****/bnet winetricks corefonts fontsmooth=rgb
gives: pastebin.com/g20re9Bn
Running
WINEPREFIX=/home/****/bnet wine "/home/****/Desktop/Battle.net-Setup.exe"
Brings up the Battle.net setup and allows me to select language (I choose English EU). The client says says that it's updating, then asks me to confirm install location. Before clicking Continue with the install location, the output in the terminal seems to have many errors. The output so far is:
pastebin.com/yxR9VyQy
I uncheck "Create Desktop icon" and click continue. The app says it is installing and the progress bar reaches 100%. The full output in the terminal for the install is then
pastebin.com/1xiM4AYE
Attempting to run the client with
WINEPREFIX=/home/****/bnet optirun wine /home/****/bnet/drive_c/Program\ Files\ \(x86\)/Battle.net/Battle.net\ Launcher.exe
gives pastebin.com/Z6HUNUej and the client does not start. Similarly for using Battle.net.exe in the same folder.
Help would be greatly appreciated.
by Jon Rayner on Wednesday January 31st 2018, 6:45
The logs I posted were with no vpn on - I normally play Blizzard games with a vpn, installing with the vpn on didn't help though, so made me think that this isn't the problem. But maybe the windows emulation doesn't know how to connect through my vpn when it's on? Just stabbing in the dark here...
by Maciej Stanczew on Thursday January 11th 2018, 12:26
In my case, since I had d3d11 disabled in winecfg, the application wouldn't start, displaying the message "A required DLL could not be found". After enabling d3d11 it works; the only issue is that selecting Starcraft II causes "Battle.net Helper.exe" (not the app itself) to crash, and "Whoops" is displayed instead of usual news images.
by lu on Friday January 12th 2018, 11:31
some logs:
pastebin.com/DMqr1Xmp
I press ctrl+c becouse nothing happend after start and wanting 10 minutes.
by Maciej Stanczew on Monday January 15th 2018, 23:49
by lu on Tuesday January 16th 2018, 11:22
I'm in game again after a week break.
by Tom B on Saturday March 10th 2018, 2:29
by Maciej Stanczew on Saturday March 10th 2018, 4:28
by lu on Thursday January 11th 2018, 11:09
fixme:ntdll:EtwEventRegister ({5eec90ab-c022-44b2-a5dd-fd716a222a15}, 0x157483b, 0x15ef6d0, 0x15ef6e8) stub.
fixme:ntdll:EtwEventSetInformation (deadbeef, 2, 0x15eb49a, 43) stub
fixme:ntdll:EtwEventRegister ({5eec90ab-c022-44b2-a5dd-fd716a222a15}, 0x1031123, 0x144f110, 0x144f128) stub.
fixme:ntdll:EtwEventSetInformation (deadbeef, 2, 0x13ba3b0, 43) stub
fixme:kernelbase:AppPolicyGetThreadInitializationType 0xfffffffa, 0x5cde99c
wine: Unhandled exception 0x40000015 in thread a7 at address 0x49461e (thread 00a7), starting debugger...
fixme:ver:GetCurrentPackageId (0x32d238 (nil)): stub
wine-staging 2.21
Archlinux x86_64
by asembus on Sunday November 26th 2017, 4:06
with Ubuntu 16.04
it seems working fine with older windows version but always fail on windows 7 or later. since blizzard always ask for windows version higher than 7 i cant install any game with windows xp version
is there anything i can do ?
i only did
winetricks vcrun 2017
by Peter Anderson on Monday November 27th 2017, 4:02
You need to install wine-staging 2.18 or better.
Wine-devel is not wine staging.
by asembus on Thursday November 30th 2017, 0:41
it works now. thank you :)
by Hase on Tuesday November 21st 2017, 16:34
wine-development --version
wine-2.20 (Debian 2.20-1)
I guess I had the mistaken view that wine-development was the staging package?
by Peter Anderson on Tuesday November 21st 2017, 16:40
by alfadir on Tuesday November 21st 2017, 3:31
I suspect this [bugs.winehq.org/show_bug.cgi?id=42865#c18] is the cause, will see if it is easy to add the patches to the packages.
by Hase on Sunday November 19th 2017, 16:35
by Peter Anderson on Tuesday November 21st 2017, 16:26
Please check your active wine in a terminal by typing:
wine --version
by Hase on Tuesday November 21st 2017, 16:35
wine-development --version
wine-2.20 (Debian 2.20-1)
I guess I had the mistaken view that wine-development was the staging package?
Comment
by Peter Anderson on Monday November 13th 2017, 14:20
bugs.winehq.org/show_bug.cgi?id=44024
by Chiro on Sunday November 12th 2017, 4:24
The progress bar is stuck at "init" and the console complains about stubs on MoveFileWithProgress and GetUniversalName.
It seems that it doesn't know how to read/write and find the files that need updating.
Is that part solved with the winetricks somehow?
by Peter Anderson on Sunday November 5th 2017, 12:12
Please note that the recent test results that indicate everything works correctly, are based upon installation using wine-staging and not plain wine. There are a number of fixes in wine-staging that are not yet present in wine which have a huge impact on the successful installation and use of the client.
Please use the latest wine-staging when installing the Blizzard App / Battle.net client in a new, clean WINEPREFIX.
by BloodyIron on Sunday November 5th 2017, 12:09
This effectively means you can't play Overwatch now, as the game refuses to install when it sees you're running XP.
There's a bug report for this, and we need to get attention on it : bugs.winehq.org/show_bug.cgi?id=43910
Until then, Overwatch is not even possible, and "XP support is ending" will mean soon we won't be able to play ANYTHING Blizzard.
by CromatDragon on Thursday November 2nd 2017, 12:59
This how to is not working for me. I have an Arch distro (manjaro) and when I follow this how to step by step (a lot of times by now) the client never works. If I put it in WindowsXP, the client works, but no Diablo 3, and if I change it to Windows 7, Windows 8, Windows 2008 R2, etc no one of them works. Some clue?
Regards
by sykhro on Thursday November 2nd 2017, 14:52
by kleshas on Friday November 3rd 2017, 17:11
wine, winetricks, lib32-gnutls, lib32-libldap, lib32-mpg123
WINEPREFIX=/home/kleshas/.PlayOnLinux/wineprefix/battle.net WINEARCH=win32 winetricks (installs mono and gecko)
WINEPREFIX=/home/kleshas/.PlayOnLinux/wineprefix/battle.net WINEARCH=win32 winetricks corefonts
WINEPREFIX=/home/kleshas/.PlayOnLinux/wineprefix/battle.net WINEARCH=win32 winetricks ie8
Reboot the WINE battle.net ‘system’
WINEPREFIX=/home/kleshas/.PlayOnLinux/wineprefix/battle.net WINEARCH=win32 winetricks vcrun2015
I think this step changes the virtual drive to WinXP
Open winecfg. Go to Libraries tab and check libraries with default (native, builtin) setting:
api-ms-win-crt-runtime-l1-1-0.dll
api-ms-win-crt-stdio-l1-1-0.dll
ucrtbase.dll
vcruntime140.dll
I think these should be there already.
Under winecfg, Libraries tab:
d3d11 - disabled
WINEPREFIX=/home/kleshas/.PlayOnLinux/wineprefix/battle.net WINEARCH=win32 wine /home/kleshas/Downloads/Battle.net_Setup.exe
This worked for me under archx64. Still under WinXP, but for now the games work just with an extra warning from the battle.net client regarding out-of-support OS's. I'm not sure you need the WINEARCH=win32 every time.
by CromatDragon on Saturday November 4th 2017, 5:04
"We can't install StarCraft II because your operatin system doesn't meet the minimum specs to run it.
Your OS: Windows XP Service Pack 3
Minimum: Windows 7"
Someone has some clue to launch the client with Win7?
Regards
by Jean-Michel on Tuesday November 21st 2017, 16:17
1) winecfg : choose WinXP
2) launch battle.net
3) in the same terminal : winecfg : choose Windows 7
4) then on battle.net launch the game
You will have the windows version message and it will launch
hope it will help someone else
by Dan (Strit) Johansen on Tuesday October 31st 2017, 15:57
This results in loads of "Battle.net.exe" processes running unless you manually close them after each exit of the Blizzard App.
I'm using wine-staging 2.19, also tried wine-staging-nine 2.19.
Anyone else noticed this? Is it a bug?
by kleshas on Thursday November 2nd 2017, 11:34
by Peter Anderson on Sunday November 5th 2017, 12:19
by Storm Engineer on Saturday October 21st 2017, 10:58
"winetricks dotnet40" + "winetricks --force ie8" fixed it.
by Storm Engineer on Saturday October 21st 2017, 11:04
Either way, my issue is NOT fixed after all. :(
by Storm Engineer on Monday October 16th 2017, 12:39
BUT... With Win 7 or newer, News and Chat doesn't work (Battle.net Helper.exe crashed). And I have Staging 2.18, corefonts installed and 32 bit packages installed.
Any workaround for this? Can I have wine run 2008 preset but report Win 7 towards programs to fool the system check maybe?
by Storm Engineer on Friday October 20th 2017, 11:31
I have to chose between either the Social tab, news tab and Chat works, or the actual games work... this sucks.
by spaceman on Thursday December 21st 2017, 12:34
Wine is free, opne source software, if you're not happy with any aspect of it you can always fork it and fix it yourself.
by Storm Engineer on Friday October 20th 2017, 20:37
by mioc on Wednesday October 4th 2017, 8:33
Any ideas how to solve this?
by Dox on Thursday October 5th 2017, 9:59
1) Settings > Sound & Notifications: Disable "Enable Sound".
If that doesn't work, try this:
2) Settings > General: Disable "Use browser hardware acceleration when available"
And please, let me know if this works.
by mioc on Thursday October 5th 2017, 10:59
2. HW acceleration was already disabled.
This started a few versions before.
by Tod Jackson on Tuesday October 3rd 2017, 15:26
Is this still an issue for anyone else? I've been waiting for wine-staging 2.18 to try before I file a bug. ;-)
by Tod Jackson on Tuesday October 3rd 2017, 15:34
by mioc on Thursday October 5th 2017, 11:52
by Alberto on Tuesday October 3rd 2017, 10:09
By now, wine-staging 2.17 works at least to launch games (WoW) from the app without the use of wine-overwatch 2.14.
Thanks for your report.
by Alberto on Tuesday October 3rd 2017, 10:11
Sorry for New Coment instead of Reply.
by diego on Thursday September 28th 2017, 15:57
by mioc on Sunday September 24th 2017, 4:41
After updating to latest version the client starts but after a few seconds it crashes everytime. I have to be quick and click on play in order to run any game. Tried several wine versions, win xp, 10 ...
Before the update all worked flawlessly. Any else experiencing this?
by Alberto on Monday September 25th 2017, 4:13
by mioc on Sunday October 1st 2017, 10:36
by pk on Thursday September 14th 2017, 10:24
Now after setting up a fresh wine bottle with the 2.16 staging (tried other verions) 32bit and exactly like the instructions above - I still get two annoying bugs which maybe related or not:
- everytime I launch the client the SystemSurvey.exe crashes but seems to have no effect on starting the Battlent App
The crash windows holds no information: "Waiting for detailed information, please wait..." never finishes.
Using playonlinux I can get a debug information:
p11-kit: couldn't load module: /usr/lib32/pkcs11/gnome-keyring-pkcs11.so: /usr/lib32/pkcs11/gnome-keyring-pkcs11.so
- also the battlenet client window works for starting the games but doesn't show the inbuilt browser news anymore, just shows a spinning wheel forever.
Any ideas how to fix this? (Also I tried with all different windows version set in wine (XP up to W10).
thx, p.
by Peter Anderson on Monday September 18th 2017, 8:29
The system survey crash happens when the MS corefonts aren't correctly installed. Make sure they are installed for the correct WINEPREFIX that the app is running in. e.g.
WINEPREFIX=/home/username/myblizzardapp winetricks corefonts
The policykit error can be caused by not having a policykit running, or sometimes two different policykits are installed and trying to run on the system. Are you using LXDE by any chance? Sometimes unticking the LXDE policykit in startup options under LXDE default applications on the start menu solves this.
by pk on Monday September 18th 2017, 14:54
Corefonts are installed on arch here...
Using the command to install them into the WINEPRFIX doesn't work - "no absolute path", well I will have to recreate the folder structure of my system for that - can't do it right now.
The polkit seems to be correctly installed, do I need the 32bit or the 64bit or both (on a 64bit system)?
Using playonlinux doesn't work anymore cause of all the python updates...
Meh,. :-(
p.
by Peter Anderson on Monday September 18th 2017, 8:33
Exit the app
Set windows version to XP using winecfg
Run the app and log in.
Now exit again and set win version to any version >= win 7
Next time you run the app the web content should be displayed properly.
by Alberto on Monday September 18th 2017, 13:17
But is a pain to do everyday.
In other hand, in October 1st (if I remember good) Blizzard delete XP version to run Blizzard (or Battle.net again in a nearly future) Launcher. The major problem is this.
If we can't change to XP to do the workaround to see web elements, we are dammned.
Regards and thank you to share the workaround.
by pk on Monday September 18th 2017, 14:48
by Peter Anderson on Tuesday October 3rd 2017, 10:02
by Alberto on Friday October 6th 2017, 14:09
With wine-staging 2.18 all feed works, images and videos in all tabs!
by Jen on Wednesday July 12th 2017, 11:03
by Jen on Friday July 14th 2017, 14:47
by Jen on Friday July 14th 2017, 14:55
by Siren Watcher on Saturday July 8th 2017, 3:39
This didn't fix it. So, its still bugged for me.
by Siren Watcher on Friday June 30th 2017, 11:26
Issue: Blizzard App Fails to Recognize Password Upon Switching Regions. The default "password" area isn't recognised when typed into. There is an override in place for US logins but not for EU logins.
Images: [with override under US] imgur.com/zZHUtPN [failing to override for EU] imgur.com/h6z3IWQ
Tried fixes:
> Changing the Launcher.db codes for both WoW and Blizz App to enEU from enUS to see if the override is just for the defaulted region. Does load the launcher by default as "europe", though still does not give the override.
> Typing in the password like 100 times to see if the override was something that proc'd from failed attempts on US. Hasn't worked.
When occured:
The Blizzard App ran an update about a week or so ago, it bugged out around this time. It threw all users of the application "out" of being signed in. Both on US and EU after the update. Upon signing back in I received this error, I assume from a GUI override update. A new game has been introduced to the application, which is not directly linked to Blizzard Entertainment, so I assume the integration of the new Destiny PC players accounts, put an issue in the coding for Wine under EU?
Currently, using the Blizzard App on US works fine. Though after a week of trying, waiting to see if it just fixed itself, I still cannot use it to sign into the EU interface.
I can still sign onto my EU WoW account through the US interface. So there is no rush, its just a minor hindrance. Does not affect gameplay of any of Blizzard's games. Just stops me talking to my EU friends when I am signed onto US WoW.
by jarao on Monday July 3rd 2017, 15:37
Even when the system is set to windows 10, even the blizzard news work.
by Siren Watcher on Saturday July 8th 2017, 4:05
Under what you said, I deleted the application data seeming as it was working for you but not for me.
This didn't fix it. So, its still bugged for me.
by Nikita on Monday June 19th 2017, 16:44
by CiciBean on Thursday June 15th 2017, 21:13
by moxian on Wednesday June 14th 2017, 12:16
I still, however, cannot see patch notes, update, "breaking news" and other type of "cards", once the app opens - I have two small white rectangles instead. That said, this problem can definitely be fixed, as it worked fine before I updated wine and purged my wine prefix, breaking my setup :P
by AdamTheGrump on Wednesday June 14th 2017, 12:22
I have had luck with the News/Patch cards by using "winetricks dotnet40", then setting windows version back to 7. This appears to work from my testing yesterday but I haven't added it to the installation guide yet. Wanted to mess around a bit more. Maybe a different .NET version won't require a weird version hack?
by moxian on Wednesday June 14th 2017, 12:40
I can confirm that using `winetricks dotnet40` fixes the cards. For me it *also* fixes the login screen in the absence of ie8.
For reference: wine-2.9 (or 2.1 - both work), staging (doesn't work with vanilla for me), 64-bit prefix, gentoo.
by AdamTheGrump on Wednesday June 14th 2017, 12:43
by moxian on Wednesday June 14th 2017, 13:39
dotnet40 does not fix. Force-installing ie8 fixes it. I haven't tried actually buying anything, but navigation certainly works just fine.
In case the issue lies within winetricks (ie8 installation being different or something):
$ winetricks --version
20170517 - sha256sum: 0461b25e833fd242b65addc72a5195c0047d3aaa91136b768d37102acb829a8e
by François Warnet on Tuesday June 27th 2017, 21:29
by Nate Clark on Saturday May 27th 2017, 7:02
setting plz. (I can't play "overwatch" of because of that)
by kolAflash on Sunday June 4th 2017, 13:21
by AdamTheGrump on Sunday June 11th 2017, 12:52
by mioc on Saturday May 27th 2017, 2:46
by asembus on Friday May 26th 2017, 21:01
get this error when running on every version except win xp
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported
fixme:wininet:InternetSetOptionW Option 77 STUB
fixme:wininet:InternetSetOptionW Option 77 STUB
err:wininet:open_http_connection create_netconn failed: 12029
by Nate Clark on Saturday May 27th 2017, 10:12
Maybe not the same error code though.
by kolAflash on Sunday June 4th 2017, 13:18
by pyr0man99 on Thursday May 25th 2017, 14:39
System Details:
Linux Mint 18
Wine 2.8
by pyr0man99 on Tuesday May 30th 2017, 19:03
by AdamTheGrump on Wednesday May 24th 2017, 1:08
by Zeke Sonxx on Wednesday May 24th 2017, 12:35
by kolAflash on Wednesday May 24th 2017, 13:44
What happened:
1. Loading bar shows up
2. Crash before login window opens
by kolAflash on Wednesday May 24th 2017, 14:44
download.opensuse.org/repositories/Emulators:/Wine/openSUSE_Leap_42.2/x86_64/wine-staging-2.8-665.1.x86_64.rpm
download.opensuse.org/repositories/Emulators:/Wine/openSUSE_Leap_42.2/x86_64/wine-staging-32bit-2.8-665.1.x86_64.rpm
Only problem: There where two "E-Mail" and two "Password" fields in the login window and I had to enter my login data in the lower ones.
by Pacane on Friday June 2nd 2017, 14:25
by kolAflash on Sunday June 4th 2017, 13:18
by Marc Grondin on Sunday June 4th 2017, 14:15
by kolAflash on Monday June 5th 2017, 7:56
(I wasn't able to do exact tests until now)
dev.wine-staging.com/patches/99/
dev.wine-staging.com/patches/103/
dev.wine-staging.com/patches/104/
dev.wine-staging.com/patches/107/
by Alberto on Monday June 5th 2017, 4:35
Only 2 errors.
1 - Two e-mail and passwords fields. Only type in the lower ones and uncheking (every day) the "no close session" option.
2 - Don't feed anything in Games panels (other tabs as Shop and News works OK). I can't see players on games nor Frame of news or eventually frames of warnings of problems or semanal maintenances. In SC and OW not appear the buttons Try free.
The point what bothers me the most is the second Point. The first point is annoying but passable.
by Alberto on Monday June 5th 2017, 5:01
by Thomas Woltjer on Monday May 8th 2017, 21:20
by Mike on Friday April 28th 2017, 7:54
Now it runs well, however it literally takes AGES to start up (almost 10 minutes from $wine Battle.net Launcher.exe to the logged-in & working program.)
by Mike on Friday April 28th 2017, 8:04
by Mike on Friday April 28th 2017, 8:51
by Svito on Friday April 28th 2017, 10:24
I remember that launching Battle.net took 2 minutes for me year ago, then they updated it with new Qt and that fixed it.
Also remember that updating was stuck for me on Waiting if I didn't install vcrun2015, doing so fixed it.
Try winetricks vcrun2015 or disabling browser acceleration in settings if you have not tried it already.
Also consider starting from fresh WINEPREFIX and installing it with new Blizzard App installer if that was not the case.
by Mike on Friday April 28th 2017, 18:42
Took much faster to start, yet at the moment its stuck at "Waiting" pre-update, which I hope would pass at some point and update would apply itself. :-S
by Svito on Friday April 28th 2017, 10:26
by Mike on Friday April 28th 2017, 18:41
by Jose on Tuesday February 28th 2017, 11:38
I installed the required update and ever since then i have been experiencing performance issues. The client seems heavy now, and every game I run with it is even heavier to handle, making it impossible to play comfortably (even HS has minor lag issues, not to mention Heroes of the Storm or Diablo 3, which I can run but not play smoothly with a group of people) . Unfortunately we don't have the option to use an older version of the launcher,
Anyone has noted this issue now or in the past? Does someone have a workaround maybe in the form of some library override?
I am running Ubuntu 16.04 in a Intel i7 8x 2.5GHz with 8Gb RAM and 1Gb Graphic card running from a SSD Disk. It is a laptop but a decent one and i have not suffered performance issues in the past within this system.
Any suggestion would be appreciated.
Thanks :)
by AdamTheGrump on Tuesday April 18th 2017, 12:22
I wonder if this has something to do with us.battle.net/forums/en/wow/topic/20753178086