Battle.net crashes after login

Support
1

Wow has been working flawlessly for months. But yesterday when I presed “Play” in the Battle.net client, it all crashed. Since then, whenever I am trying to start battle.net, it is asking me to log in, Battle.net crashes right after I logged in.

I don’t know what I did to break it. I only did an “apt-upgrade”, which updated my graphics driver, so that might be it.

I tested it without DXVK, and then things actually worked. But I have very poor performance without DXVK.

Here is the log when trying to open Battle.net and it crashes - but I don’t really understand it.

INFO     2018-12-19 16:14:48,245 [lutriswindow]:Setting up view for first run
INFO     2018-12-19 16:14:53,509 [dxvk]:Replacing /home/simon/Games/world-of-warcraft-december/drive_c/windows/system32/dxgi with DXVK version
INFO     2018-12-19 16:14:53,509 [dxvk]:Replacing /home/simon/Games/world-of-warcraft-december/drive_c/windows/system32/d3d11 with DXVK version
INFO     2018-12-19 16:14:53,510 [dxvk]:Replacing /home/simon/Games/world-of-warcraft-december/drive_c/windows/system32/d3d10core with DXVK version
INFO     2018-12-19 16:14:53,510 [dxvk]:Replacing /home/simon/Games/world-of-warcraft-december/drive_c/windows/system32/d3d10_1 with DXVK version
INFO     2018-12-19 16:14:53,510 [dxvk]:Replacing /home/simon/Games/world-of-warcraft-december/drive_c/windows/system32/d3d10 with DXVK version
INFO     2018-12-19 16:14:53,510 [dxvk]:Replacing /home/simon/Games/world-of-warcraft-december/drive_c/windows/syswow64/dxgi with DXVK version
INFO     2018-12-19 16:14:53,510 [dxvk]:Replacing /home/simon/Games/world-of-warcraft-december/drive_c/windows/syswow64/d3d11 with DXVK version
INFO     2018-12-19 16:14:53,510 [dxvk]:Replacing /home/simon/Games/world-of-warcraft-december/drive_c/windows/syswow64/d3d10core with DXVK version
INFO     2018-12-19 16:14:53,510 [dxvk]:Replacing /home/simon/Games/world-of-warcraft-december/drive_c/windows/syswow64/d3d10_1 with DXVK version
INFO     2018-12-19 16:14:53,510 [dxvk]:Replacing /home/simon/Games/world-of-warcraft-december/drive_c/windows/syswow64/d3d10 with DXVK version
WARNING: radv is not a conformant vulkan implementation, testing use only.
wine: cannot find L"C:\\windows\\system32\\winemenubuilder.exe"
WARNING: radv is not a conformant vulkan implementation, testing use only.
WARNING: radv is not a conformant vulkan implementation, testing use only.
WARNING: radv is not a conformant vulkan implementation, testing use only.
ATTENTION: default value of option mesa_glthread overridden by environment.
WARNING: radv is not a conformant vulkan implementation, testing use only.
NIR validation failed after nir_opt_peephole_select
3 errors:
shader: MESA_SHADER_COMPUTE
name: tfb_query
local-size: 64, 1, 1
shared-size: 0
inputs: 0
outputs: 0
uniforms: 0
shared: 0
decl_function main (0 params)

impl main {
	block block_0:
	/* preds: */
	vec1 64 ssa_0 = load_const (0x               0 /* 0.000000 */)
	vec1 32 ssa_4 = load_const (0x00000000 /* 0.000000 */)
	/* flags */ vec1 32 ssa_7 = intrinsic load_push_constant (ssa_4) (0, 16) /* base=0 */ /* range=16 */
	vec1 32 ssa_9 = intrinsic vulkan_resource_index (ssa_4) (0, 0) /* desc-set=0 */ /* binding=0 */
	vec1 32 ssa_11 = intrinsic vulkan_resource_index (ssa_4) (0, 1) /* desc-set=0 */ /* binding=1 */
WARNING  2018-12-19 16:15:23,666 [thread]:Thread aborting now
2

Battle.net does not want DXVK, in my experience, although my WoW insists on it.
I have 2 setups in my Lutris :-

Battle.net gets started with “/win7/WoW/EU/World of Warcraft Launcher.exe” in my personal case. And I only use it for updates.

The Game itself runs with “/win7/WoW/EU/retail/Wow.exe” and for that I have TKG-3.21 with DXVK 0.94 and on this one I disable Lutris runtime.

Maybe you can steal some ideas from this.

3

But it’s weird that it worked 3 days ago. If I uncheck the Use DXVK, it works. But I get very poor performance then.

4

I have the same issue. Upgraded my Kubuntu 18.10 which included the following packages:
libcom-err2
libwayland-egl1
libibverbs1
libretro-beetle-psx
e2fsprogs
ibverbs-providers
retroarch
libss2
libwayland-client0
libext2fs2
libretro-core-info
unattended-upgrades
libwayland-server0
libwayland-cursor0
linux-headers-generic
linux-image-generic
linux-generic
linux-signed-generic

There were no updates to my Mesa packages.

Can you check which packages were upgraded for you LegolasDK?

5

I ran into the same problem 4 days ago. While debugging lutris I noticed a note short before Battle.net crashed (after the login window too):

Note: you can probably enable DRI3 in your Xorg config

So: I have a HP-Spectre x360 notebook with an Intel HD 630 and an AMD RX Vega M GL GPU.
OS: Ubuntu 18.10, Kernel: 4.19.11, Latest mesa/vulkan driver from the oibaf ppa

You can check your active DRI versions by:
xdpyinfo | grep DRI
DRI2

So I updated my xorg config to:

/etc/X11/xorg.conf.d/20-intel.conf

Section "Device"
  Identifier  "Intel Graphics"
  Driver      "intel"
  Option      "DRI"    "3"
EndSection

And now Battle.net starts with DXVK enabled :o Hope that helps you maybe :o

6

Old thread, my apologies for necromancing but I think this is relevant:

For anyone on OpenSUSE Tumbleweed who runs into Battle.net crashing after login:

warn: OpenVR: Failed to locate module
info: Required Vulkan extension VK_KHR_surface not supported
terminate called after throwing an instance of ‘dxvk::DxvkError’
Leaked struct Blizzard::File::StreamRecord 09CE18F4 {“Battle.net.mpq”}
Leaked struct Blizzard::File::StreamRecord 008F49BC {“Battle.net.mpq”}
Game is considered exited.
Initial process has exited.
All monitored processes have exited.
Exit with returncode 768

Install the following package:
sudo zypper install libvulkan_radeon-32bit