Fresh WoW install

[Kaz]

I'm trying to reinstall the game on Linux using Wine. I can install/launch the game using the updater, but as soon as I put my password/authenticator information in, the game will not connect to the world server. It attempts to connect, but dies. I usually get a very quick glimpse of an error code 104, but it goes away too quickly to be certain.

The client and launcher work perfectly fine as far as I can tell. I've tried copying a working install from another machine, using a fresh wine prefix, forcing directx, forcing opengl, all to no avail.

I'm stumped. I've tried to troubleshoot this and dig through all the forums, wikis, and faqs, but I've got nothing.

[dimesio]

Wine version? If it's not the latest development release, upgrade. If the problem is in current Wine, post terminal output. http://wiki.winehq.org/FAQ#get_log

[Kaz]

I'm using version 1.7.23 on Arch and the all the latest updates. Using wine or wine64 or forcing into opengl/directx give the same results. The game itself runs, but I can't make it past the authentication stage. I had it installed an running on this machine a year or so ago, but deleting my .wine folder/prefix should have cleared that up.

Code: Select all

fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:d3d11:D3D11CreateDevice stub: adapter (nil), driver_type D3D_DRIVER_TYPE_HARDWARE, swrast (nil), flags 0x1, feature_levels 0x23f770, levels 0x3, sdk_version 7, device (nil), feature_level 0x23f790, context (nil)
fixme:win:EnumDisplayDevicesW ((null),0,0x23e8c0,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x23e700,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x23ed20,0x00000000), stub!
fixme:dxgi:dxgi_adapter_CheckInterfaceSupport iface 0x48e80, guid {9b7e4c0f-342c-4106-a19f-4f2704f689f0}, umd_version (nil) stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x23ec30,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x23eb20,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x23e960,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x23f0d0,0x00000000), stub!
fixme:d3d9:D3DPERF_SetOptions (0x1) : stub
fixme:d3d:debug_d3dformat Unrecognized 0x5a574152 (as fourcc: RAWZ) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x5a574152) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x5a574152 (as fourcc: RAWZ) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x5a574152) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x5a574152 (as fourcc: RAWZ) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x5a574152) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table
fixme:win:EnumDisplayDevicesW ((null),0,0x23e1e0,0x00000000), stub!
err:ntdll:NtQueryInformationToken Unhandled Token Information class 28!
fixme:advapi:BuildSecurityDescriptorW ((nil),(nil),1,0x23f640,0,(nil),0x4a6d8a0,0x23f634,0x23f618) stub!
err:ntdll:NtQueryInformationToken Unhandled Token Information class 28!
fixme:advapi:BuildSecurityDescriptorW ((nil),(nil),1,0x23f640,0,(nil),0x4a6d8a0,0x23f634,0x23f618) stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x23d9d0,0x00000000), stub!
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:win:EnumDisplayDevicesW ((null),0,0x23e340,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x23e180,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x23e330,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x23e170,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x23e330,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x23e170,0x00000000), stub!
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:win:EnumDisplayDevicesW ((null),0,0x23e590,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x23e3d0,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x23e580,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x23e3c0,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x23e580,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x23e3c0,0x00000000), stub!
fixme:imm:ImmReleaseContext (0x70046, 0x4a6f4f0): stub
fixme:win:EnumDisplayDevicesW ((null),0,0x23e570,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x23e3b0,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x23e560,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x23e3a0,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x23e560,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x23e3a0,0x00000000), stub!
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:ole:CoInitializeSecurity ((nil),-1,(nil),(nil),0,3,(nil),0,(nil)) - stub!
fixme:wbemprox:wbem_locator_QueryInterface interface {00000126-0000-0000-c000-000000000046} not implemented

[Soulcage]

So is the battle.net launcher required? See if this command works to launch the launcher. I have to do it for Diablo 3 otherwise it would get stuck retrieving character.

Code: Select all

setarch i386 -3 wine 'c:\program files\battle.net\battle.net launcher.exe'

[Kaz]

It is not required as far as I know. I can launch the game either via the battle.net launcher or running the executable directly. Both end with the same results.

The game client itself runs, but it seems to fail on the authentication to the worldserver or there's another check that is happening that I'm missing thats not throwing a flag or error message to debug.