June 2020 - Wine-Bugs - list.winehq.org

[Bug 49007] StarCitizen freezes on start

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49007 --- Comment #25 from rawfox <rawfox(a)freenet.de> --- Created attachment 67311 --> https://bugs.winehq.org/attachment.cgi?id=67311 reverse patch for ntdll/loader.c This patch is reverting the changes to loader.c for the wine-staging commit bf83d755d987fec552cd1dce30638c31c49ab760 from today. wine-5.9-195-gbf83d755d9 (Staging) -- 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.

June 1, 2020

[Bug 49301] pthread_exit hangs on unwind through call_thread_exit_func on arm64

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49301 --- Comment #1 from Stefan Dösinger <stefan(a)codeweavers.com> --- Created attachment 67310 --> https://bugs.winehq.org/attachment.cgi?id=67310 Backtrace This file shows a backtrace of the hung thread. I did not notice this before, but gdb also struggles with the asm code. -- 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.

June 1, 2020

[Bug 49301] New: pthread_exit hangs on unwind through call_thread_exit_func on arm64

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49301 Bug ID: 49301 Summary: pthread_exit hangs on unwind through call_thread_exit_func on arm64 Product: Wine Version: unspecified Hardware: aarch64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: stefan(a)codeweavers.com Distribution: --- Created attachment 67309 --> https://bugs.winehq.org/attachment.cgi?id=67309 Workaround My arm64 Wine build spins in services.exe after starting up anything. The backtrace points into pthread_exit() - see attached file backtrace.txt. I placed pthread_exit calls throughout the thread creation / shutdown code and it works up to the point where signal_exit_thread() calls call_thread_exit_func(). After call_thread_exit_func() passes control to the C function exit_thread() pthread_exit() will hang. I previously had this problem only in a gcc wine build (with 8fb8cc03 reverted), but recently, presumably after an update to clang-10, the problem also happens when building Wine with clang. The attached backtrace is from a build with clang 10. Calling exit_thread() directly from signal_exit_thread() without going through call_thread_exit_func works around the problem. See attached file noasm.diff -- 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.

June 1, 2020

[Bug 49300] Multiple debuggers/tools from Windows 10 SDK want api-ms-win-downlevel-kernel32-l2-1-0.dll

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49300 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://software-download.m | |icrosoft.com/download/pr/17 | |763.1.180914-1434.rs5_relea | |se_WindowsSDK.iso Keywords| |download -- 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.

June 1, 2020

[Bug 49300] New: Multiple debuggers/tools from Windows 10 SDK want api-ms-win-downlevel-kernel32-l2-1-0.dll

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49300 Bug ID: 49300 Summary: Multiple debuggers/tools from Windows 10 SDK want api-ms-win-downlevel-kernel32-l2-1-0.dll Product: Wine Version: 5.9 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: api-ms-win-* Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, mentioned in bug 44988 and to track: https://www.winehq.org/pipermail/wine-devel/2020-May/167131.html 'api-ms-win-downlevel-kernel32-l2-1.0.dll' -> introduced with Windows 8.1 https://www.geoffchappell.com/studies/windows/win32/apisetschema/history/se… It seems the tools lazy-load/resolve this API set. It's not referenced in imports section. --- snip --- $ grep -ralZ --include \*.dll --include \*.exe api-ms-win-downlevel-kernel32-l2-1-0 drive_c/ | xargs -r0i bash -c "echo \"{}\"" drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm64/DbgModel.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm64/dbghelp.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm64/dbgsrv.exe drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm64/symproxy/symsrv.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm64/ntkd.exe drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm64/kdbgctrl.exe drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm64/kd.exe drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm64/winxp/exts.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm64/kdsrv.exe drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm64/dbgeng.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm64/dbgcore.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm64/winext/ext.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm64/winext/uext.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm64/dbengprx.exe drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm64/cdb.exe drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm64/ntsd.exe drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm64/symsrv.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm64/rtlist.exe drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm64/srcsrv/dbghelp.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm64/srcsrv/dbgcore.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm64/srcsrv/srcsrv.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm64/srcsrv.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm64/windbg.exe drive_c/Program Files (x86)/Windows Kits/10/Debuggers/x86/DbgModel.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/x86/dbghelp.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/x86/dbgsrv.exe drive_c/Program Files (x86)/Windows Kits/10/Debuggers/x86/symproxy/symsrv.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/x86/ntkd.exe drive_c/Program Files (x86)/Windows Kits/10/Debuggers/x86/kdbgctrl.exe drive_c/Program Files (x86)/Windows Kits/10/Debuggers/x86/kd.exe drive_c/Program Files (x86)/Windows Kits/10/Debuggers/x86/winxp/exts.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/x86/kdsrv.exe drive_c/Program Files (x86)/Windows Kits/10/Debuggers/x86/dbgeng.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/x86/dbgcore.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/x86/winext/ext.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/x86/winext/uext.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/x86/dbengprx.exe drive_c/Program Files (x86)/Windows Kits/10/Debuggers/x86/cdb.exe drive_c/Program Files (x86)/Windows Kits/10/Debuggers/x86/ntsd.exe drive_c/Program Files (x86)/Windows Kits/10/Debuggers/x86/symsrv.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/x86/rtlist.exe drive_c/Program Files (x86)/Windows Kits/10/Debuggers/x86/srcsrv/dbghelp.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/x86/srcsrv/dbgcore.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/x86/srcsrv/srcsrv.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/x86/srcsrv.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/x86/windbg.exe drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm/DbgModel.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm/dbghelp.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm/dbgsrv.exe drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm/symproxy/symsrv.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm/ntkd.exe drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm/kdbgctrl.exe drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm/kd.exe drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm/winxp/exts.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm/kdsrv.exe drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm/dbgeng.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm/dbgcore.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm/winext/ext.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm/winext/uext.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm/dbengprx.exe drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm/cdb.exe drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm/ntsd.exe drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm/symsrv.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm/rtlist.exe drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm/srcsrv/dbghelp.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm/srcsrv/dbgcore.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm/srcsrv/srcsrv.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm/srcsrv.dll drive_c/Program Files (x86)/Windows Kits/10/Debuggers/arm/windbg.exe --- snip --- Regards -- 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.

June 1, 2020

[Bug 47070] DA: Inquisition can't see gamepad

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=47070 --- Comment #15 from sorin.mikaelis255(a)gmail.com --- Created attachment 67308 --> https://bugs.winehq.org/attachment.cgi?id=67308 debug trace with +dinput,xinput ran a debug trace with +dinput,xinput with Wine 5.9 I believe I'm using a different controller from Timofeev, in his trace I'm seeing "generic usb controller" whereas I'm using an Xbox One controller via bluetooth In contrast to his traces there doesn't seem to be any output for xinput, just for dinput. I'm not sure if this is explained by the controller difference, something I did wrong, or something else entirely. -- 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.

June 1, 2020

[Bug 49193] Multiple kernel drivers need wdfldr.sys.WdfVersionBind function (Denuvo Anti-Cheat "denuvo-anti-cheat.sys", Steel Series Engine "ssdevfactory.sys")

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49193 --- Comment #2 from Anastasius Focht <focht(a)gmx.net> --- Hello Zeb, --- quote --- That said, I'm not sure how best to actually do so. The source is predictably ugly and all in C++, which makes importing it not particularly appealing, but there's no good reason to leave it in an external library. Perhaps porting it to C and rearranging it is the best option, but seems to be getting updates at least along with major releases of Windows 10... --- quote --- Microsoft promotes the porting of traditional WDM drivers to KDMF or UMDF for some years now. Vendors are catching up on this, specifically with Windows 10. https://docs.microsoft.com/en-us/windows-hardware/drivers/wdf/wdf-porting-g… https://docs.microsoft.com/en-us/windows-hardware/drivers/wdf/differences-b… I've only seen two drivers (with your addition) mentioned with Wine bug reports as of now. Paul's stubbed wdfldr seemed to work for one driver but in the long run it's probably better to have a proper design/lib port as we're likely going to see more and more drivers using it. It might be worth to bring up the topic on wine-devel. Some opinions if a C port/internalization of the lib using Microsoft's WDF GitHub repo as reference is feasible. Regards -- 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.

June 1, 2020

[Bug 49293] Impossible to create Wine prefix from scratch

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49293 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #2 from Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> --- Closing Duplicate. -- 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.

June 1, 2020

[Bug 49271] Python 3.8.3 crashes due to unimplemented function api-ms-win-core-path-l1-1-0.dll.PathCchCanonicalizeEx

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49271 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #3 from Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> --- Closing Duplicate. -- 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.

June 1, 2020

[Bug 48478] RealNetworks RealPlayer 18.x crashes when installing

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=48478 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #4 from Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> --- Closing Duplicate. -- 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.

June 1, 2020