[Bug 39636] New: Assassin's Creed Syndicate crashes due to lack of DisplayConfigGetDeviceInfo in user32.dll
https://bugs.winehq.org/show_bug.cgi?id=39636 Bug ID: 39636 Summary: Assassin's Creed Syndicate crashes due to lack of DisplayConfigGetDeviceInfo in user32.dll Product: Wine Version: 1.7.55 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: n8bk13(a)gmail.com Distribution: --- After trying to launch Assassin's Creed Syndicate, it crashed and showed a message box with text: "The procedure entry point DisplayConfigGetDeviceInfo could not be located in the dynamic link library USER32.dll". It doesn't matter whether it was started directly from exe file or from UPlay. I found out that this function was first introduced in Windows Vista, so I tried to change operating system in winecfg from default "Windows XP" to "Windows 7", but it didn't help either. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39636 fjfrackiewicz(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fjfrackiewicz(a)gmail.com --- Comment #1 from fjfrackiewicz(a)gmail.com --- (In reply to n8bk from comment #0)
After trying to launch Assassin's Creed Syndicate, it crashed and showed a message box with text: "The procedure entry point DisplayConfigGetDeviceInfo could not be located in the dynamic link library USER32.dll". It doesn't matter whether it was started directly from exe file or from UPlay. I found out that this function was first introduced in Windows Vista, so I tried to change operating system in winecfg from default "Windows XP" to "Windows 7", but it didn't help either.
Does this happen in Wine 1.8-rc1? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39636 super_man(a)post.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |super_man(a)post.com --- Comment #2 from super_man(a)post.com --- (In reply to fjfrackiewicz from comment #1)
(In reply to n8bk from comment #0)
After trying to launch Assassin's Creed Syndicate, it crashed and showed a message box with text: "The procedure entry point DisplayConfigGetDeviceInfo could not be located in the dynamic link library USER32.dll". It doesn't matter whether it was started directly from exe file or from UPlay. I found out that this function was first introduced in Windows Vista, so I tried to change operating system in winecfg from default "Windows XP" to "Windows 7", but it didn't help either.
Does this happen in Wine 1.8-rc1?
To my understading there haven't been such a merge into wine code between 1.7.55 and 1.8.rc1 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39636 --- Comment #3 from n8bk <n8bk13(a)gmail.com> --- Unfortunately I couldn't manage to run client 1.8 with a right server (despite setting WINESERVER variable pointing to a server in version 1.8), so I can't definitely confirm this, but looking at the built user32.dll.so library and at the full code of Wine 1.8-rc1 I didn't find such symbol as DisplayConfigGetDeviceInfo (and some other functions introduced in Vista and 7), so I suppose the bug still exists. If I finally find out why Wine 1.8 client always tries to launch older version of the server existing in the system, then I will be able to check if the bug is really still there. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39636 --- Comment #4 from Nikolay Sivov <bunglehead(a)gmail.com> --- Could you attach full output please? If it used to work, the reason it asks for this function now could be that we offer a stub for GetDisplayConfigBufferSizes now (http://source.winehq.org/git/wine.git/commit/8b353f5409c205d4643ece3a42fcd9a...). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39636 --- Comment #5 from n8bk <n8bk13(a)gmail.com> --- Created attachment 52832 --> https://bugs.winehq.org/attachment.cgi?id=52832 Debug for AC:Syndicate in Wine 1.7.55 I don't know if it used to work before 1.7.55 - it was the first version of Wine in which I tested this game, which was released a few days ago. I posted a link to full debug log (about 42 MB). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39636 --- Comment #6 from n8bk <n8bk13(a)gmail.com> --- Finally I didn't check it in Wine 1.8, but I confirm the bug still exists in Wine 1.9. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39636 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |austinenglish(a)gmail.com -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39636 --- Comment #7 from Austin English <austinenglish(a)gmail.com> --- Created attachment 53323 --> https://bugs.winehq.org/attachment.cgi?id=53323 stub Does this help? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39636 --- Comment #8 from n8bk <n8bk13(a)gmail.com> --- After applying stub patch from comment #7 the message box about DisplayConfigGetDeviceInfo went away, but the game started to complain about QueryDisplayConfig: "The procedure entry point QueryDisplayConfig could not be located in the dynamic link library USER32.dll". Will it be processed in this issue or should I report another bug? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39636 --- Comment #9 from Austin English <austinenglish(a)gmail.com> --- (In reply to n8bk from comment #8)
After applying stub patch from comment #7 the message box about DisplayConfigGetDeviceInfo went away, but the game started to complain about QueryDisplayConfig: "The procedure entry point QueryDisplayConfig could not be located in the dynamic link library USER32.dll".
Will it be processed in this issue or should I report another bug?
A new bug please. Feel free to cc me. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39636 --- Comment #10 from Austin English <austinenglish(a)gmail.com> --- (In reply to Austin English from comment #9)
(In reply to n8bk from comment #8)
After applying stub patch from comment #7 the message box about DisplayConfigGetDeviceInfo went away, but the game started to complain about QueryDisplayConfig: "The procedure entry point QueryDisplayConfig could not be located in the dynamic link library USER32.dll".
Will it be processed in this issue or should I report another bug?
A new bug please. Feel free to cc me.
Actually, that's bug 39510 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39636 --- Comment #11 from n8bk <n8bk13(a)gmail.com> --- I applied also https://source.winehq.org/patches/data/115821 from bug 39510 and a splash screen appeared, but the game failed with message: "Unable to run the game. Your video card doesn't support DirectX 11 or video drivers need to be updated.". In logs there can be seen: ... fixme:win:RegisterDeviceNotificationA (hwnd=0x30102, filter=0x139bda60,flags=0x00000000) returns a fake device notification handle! fixme:win:EnumDisplayDevicesW ((null),0,0x23f040,0x00000000), stub! fixme:d3d11:D3D11CoreCreateDevice Ignoring feature levels. fixme:dxgi:dxgi_check_d3d10_support Ignoring adapter type. fixme:dxgi:dxgi_device_init Ignoring adapter type. ... So I suppose it might be caused by lack of implemention of those stubs or bug 34978. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39636 --- Comment #12 from Austin English <austinenglish(a)gmail.com> --- (In reply to n8bk from comment #11)
I applied also https://source.winehq.org/patches/data/115821 from bug 39510 and a splash screen appeared, but the game failed with message: "Unable to run the game. Your video card doesn't support DirectX 11 or video drivers need to be updated.". In logs there can be seen:
... fixme:win:RegisterDeviceNotificationA (hwnd=0x30102, filter=0x139bda60,flags=0x00000000) returns a fake device notification handle! fixme:win:EnumDisplayDevicesW ((null),0,0x23f040,0x00000000), stub! fixme:d3d11:D3D11CoreCreateDevice Ignoring feature levels. fixme:dxgi:dxgi_check_d3d10_support Ignoring adapter type. fixme:dxgi:dxgi_device_init Ignoring adapter type. ...
Likely it's because Wine's d3d11 support is incomplete.
So I suppose it might be caused by lack of implemention of those stubs or bug 34978.
You could try the patch for it. I've only noticed it being an issue when multiple monitors are attached. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39636 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39636 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |c7a4b0628d7597fb0eff3e5dd58 | |9f70dbba04ec1 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #13 from Austin English <austinenglish(a)gmail.com> --- (In reply to n8bk from comment #8)
After applying stub patch from comment #7 the message box about DisplayConfigGetDeviceInfo went away, but the game started to complain about QueryDisplayConfig: "The procedure entry point QueryDisplayConfig could not be located in the dynamic link library USER32.dll".
This should be fixed by https://source.winehq.org/git/wine.git/commitdiff/c7a4b0628d7597fb0eff3e5dd5... -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39636 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #14 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 1.9.5. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
wine-bugs＠winehq.org