The forum

I was able to successfully install Diablo 2 LOD 1.14d on Ubuntu Mate 19.10 but when I want to connect to Battle.net the game freezes. Here is the output I get in the logs:

 

[12/05/19 13:09:32] - Running wine-4.5 Diablo II.exe -w (Working directory : /home/echodrome/.PlayOnLinux/wineprefix/DiabloII/drive_c/Program Files/Diablo II)
0030:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
0030:fixme:ole:CoInitializeSecurity ((nil),-1,(nil),(nil),0,3,(nil),0,(nil)) - stub!
0030:fixme:wbemprox:wbem_locator_QueryInterface interface {00000126-0000-0000-c000-000000000046} not implemented
0030:err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
[2019-12-05T18:09:34Z][..\source\main.cpp:690][INFO]: System Survey 2.3.1.44, Data Version 3, Git Revision v2.3.0.42-20-ge49c7e7, Copyright (C) 2013 Blizzard Entertainment. All rights reserved.
[2019-12-05T18:09:34Z][..\source\main.cpp:764][INFO]: Exit value: 0
0039:fixme:process:GetProcessWorkingSetSizeEx (0xffffffff,0x38ccc18,0x38ccc14,(nil)): stub
0039:fixme:ntdll:EtwRegisterTraceGuidsW (0x2166d58, (nil), {f7b697a3-4db5-4d3b-be71-c4d284e6592f}, 7, 0x21b0244, (null), (null), 0x21b5ca8): stub
0039:fixme:ntdll:EtwRegisterTraceGuidsW   register trace class {72b14a7d-704c-423e-92f8-7e6d64bcb92a}
0039:fixme:ntdll:EtwRegisterTraceGuidsW   register trace class {e2091f8a-1e0a-4731-84a2-0dd57c8a5261}
0039:fixme:ntdll:EtwRegisterTraceGuidsW   register trace class {e8a3bf1f-a86b-4390-9c60-5390b969d22c}
0039:fixme:ntdll:EtwRegisterTraceGuidsW   register trace class {5727a00f-50be-4519-8256-f7699871fecb}
0039:fixme:ntdll:EtwRegisterTraceGuidsW   register trace class {7e854ec7-cdc4-405a-b5b2-aaf7c9e7d40c}
0039:fixme:ntdll:EtwRegisterTraceGuidsW   register trace class {79a60dc6-5fc8-4952-a41c-1163aeec5eb8}
0039:fixme:ntdll:EtwRegisterTraceGuidsW   register trace class {2718d25b-5bf5-4479-8e88-babc64bdbfca}
0039:fixme:process:GetNumaHighestNodeNumber (0x38ccab8): semi-stub
003d:fixme:ntdll:EtwUnregisterTraceGuids deadbeef: stub
0041:fixme:process:GetProcessWorkingSetSizeEx (0xffffffff,0x40bde60,0x40bde5c,(nil)): stub
0041:fixme:thread:NtCreateThreadEx 0x40bb530, 1f03ff, (nil), 0xffffffff, 0x553d270, (nil), 6, 0, 0, 0, (nil) semi-stub!
0041:fixme:thread:NtCreateThreadEx 0x40bb5f0, 1f03ff, (nil), 0xffffffff, 0x553d250, 0xfffffffe, 6, 0, 0, 0, (nil) semi-stub!
0043:err:ntdll:RtlpWaitForCriticalSection section 0x7bd14d60 "loader.c: loader_section" wait timed out in thread 0043, blocked by 0041, retrying (60 sec)
003e:err:ntdll:RtlpWaitForCriticalSection section 0x7bd14d60 "loader.c: loader_section" wait timed out in thread 003e, blocked by 0041, retrying (60 sec)

 

These last two lines repeat indefinitely. Any help appreciated.

 

Thanks

 

Edited by Tinou

This caught my eye because I actually have a working copy installed myself. One of the things I noticed I had to do to stop getting errors was make a shortcut to the game.exe itself if I recall correctly. Now keep in mind I have an older OG copy of the game and the only thing that happens when I connect to BE is the game updates itself to the current version. I'd have to rebuy a key to connect fully in. That having been said though if running it directly from the game.exe doesn't solve your problem then I'd be more then happy to screenshot my set up for you so you can see what you've may have done differently then I have. Hope this helps and good luck mate.