https://bugs.winehq.org/show_bug.cgi?id=38742
Bug ID: 38742 Summary: Watch_Dogs fail to run after successful Uplay installation Product: Wine Version: 1.7.44 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: tomasz.piotr.kowalczyk@gmail.com Distribution: ---
I run Ubuntu 14.04 and tried to play Watch_Dogs. My steps:
* install PlayOnLinux * create x64 container for WD (latest WINE 1.7.44) * install Uplay from .exe from its website * login and install WD
When I click "play" Uplay installs other related packages (don't remember exact names but there were 9 of them) like DirectX, VC2008, VS2010 and .NET Framework, on which it hangs for more than an hour, but after some fiddling (closing and retrying) finally passes. I'm greeted with the error about ntlm_auth which was fixed by installing winbind, but then I get the error:
error Disrupt_b64.dll, procedure entry point __crt_debugger_hook could not be loaded in the dynamic link library MSVCR100.dll
I read somewhere that this error is caused by something other and it's just a stub so I opened POL logs and found:
fixme:heap:RtlSetHeapInformation 0x690000 0 0x23fc90 4 stub fixme:heap:RtlSetHeapInformation 0x7a0000 0 0x23fc90 4 stub fixme:heap:RtlSetHeapInformation 0x8b0000 0 0x23fc90 4 stub fixme:heap:RtlSetHeapInformation 0xad0000 0 0x23fca0 4 stub fixme:heap:RtlSetHeapInformation 0xe00000 0 0x23fc90 4 stub err:module:attach_process_dlls "Disrupt_b64.dll" failed to initialize, aborting err:module:LdrInitializeThunk Main exe initialization for L"C:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\games\Watch_Dogs\bin\watch_dogs.exe" failed, status c0000142
and a bunch of:
fixme:gdiplus:GdipCreateFontFamilyFromName No support for FontCollections yet!
I can provide any necessary information, please guide me what should I do in this situation. I tried installing gdiplus package using winetricks but that only created a bunch of other errors (haven't saved those and unfortunately removed them) and I'd like to know the other way before downloading those ~20GiB again.
I found error #36713 which seems related (same error message) but as I wrote above I use a "fixed" version 1.7.44 and there wasn't any mention of what went wrong, just that "DLL failed to initialize".