November 2021 - Wine-bugs - list.winehq.org

[Bug 51103] New: d3d11:d3d11 crashes on Windows + NVidia
by WineHQ Bugzilla 25 Feb '22

25 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=51103 Bug ID: 51103 Summary: d3d11:d3d11 crashes on Windows + NVidia Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Created attachment 69968 --> https://bugs.winehq.org/attachment.cgi?id=69968 Traces for the crash on cw-gtx560 d3d11:d3d11 crashes on the cw-gtx560 machine which has an NVidia graphics card. The crash happens from Windows 8.1 to Windows 10 2009 so it seems to be related to the graphics driver rather than to the Windows version. https://test.winehq.org/data/patterns.html#d3d11:d3d11 The crash shows no backtrace but I added traces and found that the crash happens on the final release in test_device_context_state(): refcount = ID3D11Device1_Release(device); Adding a trace on the previous line shows that the refcount before that call is 1. So it's not a case of a one-too-many release calls. Without test_device_context_state() d3d11:d3d11 does not crash. According to a bisect the commit causing this crash is: commit ccffc06c6df30aa8b4ea487b868c419b9c7f5a9a Author: Rémi Bernon <rbernon(a)codeweavers.com> Date: Tue Feb 2 16:41:00 2021 +0100 d3d11/tests: Add more tests for ID3D11DeviceContext1_SwapDeviceContextState. Better checking multiple context swap side effects. Signed-off-by: Rémi Bernon <rbernon(a)codeweavers.com> Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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.

1 7

[Bug 48096] New: Mulle Meck: Unhandled exception when starting game
by WineHQ Bugzilla 25 Feb '22

25 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=48096 Bug ID: 48096 Summary: Mulle Meck: Unhandled exception when starting game Product: Wine Version: 4.19 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: odecif(a)gmail.com Distribution: --- Created attachment 65654 --> https://bugs.winehq.org/attachment.cgi?id=65654 warn+all debug log When running the game w/o any debug flags one receive the following: wine: Unhandled exception 0x80000004 in thread 9 at address 0040986D (thread 0009), starting debugger... Attached is a pretty short debug log. Some specs: Manjaro Linux 18.1.2 (clean prefix) wine-4.19-251-g292b728908 Windows 2000-mode (also tried with 95/98/Me/XP/7) No overrides 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) The game is protected by SafeDisc 1 (old game), but running from CD gets pass the "Please insert the correct CD"-error message so it's probably nothing to do with that. -- 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.

1 17

[Bug 38210] New: WshScriptExec's StdIn StdOut and StdErr are missing.
by wine-bugs＠winehq.org 25 Feb '22

25 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=38210 Bug ID: 38210 Summary: WshScriptExec's StdIn StdOut and StdErr are missing. Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wshom.ocx Assignee: wine-bugs(a)winehq.org Reporter: ptubbytaylor(a)gmail.com Distribution: --- Created attachment 51003 --> https://bugs.winehq.org/attachment.cgi?id=51003 Example.ahk Here's the documentation for the WshScriptExec object: https://msdn.microsoft.com/en-us/library/2f38xsxe(v=vs.84).aspx The Std properties appear to have the same interface as TextStream objects, which are documented here: https://msdn.microsoft.com/en-us/library/312a5kbt(v=vs.84).aspx Attached is an AutoHotkey v1.1.20.00 script that demonstrates using the StdIn property. Note that this problem isn't limited to just AutoHotkey scripts, I'm just using this property primarily from AutoHotkey. -- 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.

2 9

[Bug 44635] New: Gray Matter: Crash on new game start
by wine-bugs＠winehq.org 25 Feb '22

25 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=44635 Bug ID: 44635 Summary: Gray Matter: Crash on new game start Product: Wine Version: 3.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sa(a)whiz.se Distribution: --- Created attachment 60627 --> https://bugs.winehq.org/attachment.cgi?id=60627 crash log The game Gray Matter (the version from GOG) crashes when a new game is started. The last message from Wine is 03b:fixme:d3dx:ID3DXEffectImpl_CloneEffect (0x47f5360)->(0x17be28, 0x5f74420): stub This is a regression of some sort. The game runs with staging 2.21 (in fact I completed the entire game with this version). The game does not start with vanilla Wine 2.21. If Appdb is to be believed the game was playable back in 1.9.14, but building older Wine releases is troublesome so I haven't been able to bisect: Error: Cannot open face courier.ttf Makefile:172: recipe for target 'coue1255.fon' failed make[1]: *** [coue1255.fon] Error 1 The game requires the following winetricks: mdx xact d3dcompiler_43. Bug filed against 3.2 but tried against wine-3.2-256-g7b62a970e9. -- 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.

2 9

[Bug 44658] New: Custom Win7+ APIset lookup/ resolver tool relies on presence of 'ApiSetMap' field in PEB
by wine-bugs＠winehq.org 25 Feb '22

25 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=44658 Bug ID: 44658 Summary: Custom Win7+ APIset lookup/resolver tool relies on presence of 'ApiSetMap' field in PEB Product: Wine Version: 3.3 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, to track the following Wine-Staging patchset just for the memes ;-) https://github.com/wine-staging/wine-staging/tree/master/patches/ntdll-ApiS… Tracing the origin to Wine-Staging issue tracker: https://dev.wine-staging.com/patches/91/ --- quote --- I found an application which tries to enumerate the loaded apisets by using the PEB. This patch adds a dummy struct so that the application does no longer crash. The definition should match the one for Win 7/8. As usual Microsoft changed the format in newer windows versions again ;-). --- quote --- Ohhhh-kay? I found some useful information at Geoff Chappell's site: https://www.geoffchappell.com/studies/windows/win32/apisetschema/index.htm https://www.geoffchappell.com/studies/windows/win32/ntdll/structs/peb/index… Nice illustration: https://www.cylance.com/en_us/blog/universal-unhooking-blinding-security-so… (in 'API Set Schema' section) An example application which makes use of this (source only): https://gist.github.com/lucasg/9aa464b95b4b7344cb0cddbdb4214b25#file-apiset… It also has a small test suite. $ wine --version wine-3.3 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.

2 7

[Bug 41386] New: Motocross Madness 2 Unhandled page fault on read access to 0x00000000 at address 0x44c468
by wine-bugs＠winehq.org 25 Feb '22

25 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=41386 Bug ID: 41386 Summary: Motocross Madness 2 Unhandled page fault on read access to 0x00000000 at address 0x44c468 Product: Wine Version: 1.9.19 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: haakobja(a)gmail.com Created attachment 55737 --> https://bugs.winehq.org/attachment.cgi?id=55737 PlayOnMac-log Motocross Madness 2 crashes due to "Unhandled page fault on read access to 0x00000000 at address 0x44c468" -- 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.

2 14

[Bug 48733] New: Microsoft Visual Studio 2019 web-installer fails due to missing NCryptOpenStorageProvider
by WineHQ Bugzilla 25 Feb '22

25 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=48733 Bug ID: 48733 Summary: Microsoft Visual Studio 2019 web-installer fails due to missing NCryptOpenStorageProvider Product: Wine Version: 5.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: crypt32 Assignee: wine-bugs(a)winehq.org Reporter: rpisl(a)seznam.cz Distribution: --- This is continuation of bug 47626. The workaround still works but information since comment 8 (including) is partially obsolete, Wine evolved. The small stage-1 web installer downloads the real installer but fails to validate it due to missing NCryptOpenStorageProvider. It can be seen from logs (WINEDEBUG=+crypt,+ncrypt) and also from generated log in Temp/dd_bootstrapper_*.log: Download failed using WebClient engine. Microsoft.VisualStudio.Setup.Security.InvalidSignatureException: Package signature verification threw exception: Unknown error "-2146893783"., for path: vs_installer.opc -2146893783 = 0x80090029 = NTE_NOT_SUPPORTED -- 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.

1 6

[Bug 48201] New: unimplemented function KERNEL32.dll.SetCurrentConsoleFontEx
by WineHQ Bugzilla 25 Feb '22

25 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=48201 Bug ID: 48201 Summary: unimplemented function KERNEL32.dll.SetCurrentConsoleFontEx Product: Wine Version: 4.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: davidmanuel1993(a)hotmail.com Distribution: --- When running a console program, wine crashes with: unimplemented function KERNEL32.dll.SetCurrentConsoleFontEx To reproduce you can compile the following program and try to run it with Wine. I compiled it with MinGW. https://pastebin.com/k5SfvEtp PS: This is a follow up of https://bugs.winehq.org/show_bug.cgi?id=47620 -- 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.

1 4

[Bug 48760] New: ConEmu shows 'GetConsoleProcessList failed' at startup
by WineHQ Bugzilla 25 Feb '22

25 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=48760 Bug ID: 48760 Summary: ConEmu shows 'GetConsoleProcessList failed' at startup Product: Wine Version: 5.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rpisl(a)seznam.cz Distribution: --- ConEmu shows "ConEmuC64.exe: PID=132: GetConsoleProcessList failed, code=0" at startup due to GetConsoleProcessList being just a stub. Returning zero is an error according to documentation, "because every console has at least one process associated with it". Then ConEmu starts successfully, so this is a minor issue. -- 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.

1 7

[Bug 51348] New: uxtheme.SetWindowTheme should use SendMessage to send WM_THEMECHANGED
by WineHQ Bugzilla 25 Feb '22

25 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=51348 Bug ID: 51348 Summary: uxtheme.SetWindowTheme should use SendMessage to send WM_THEMECHANGED Product: Wine Version: 6.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: uxtheme Assignee: wine-bugs(a)winehq.org Reporter: x1917x(a)gmail.com Distribution: --- Created attachment 70205 --> https://bugs.winehq.org/attachment.cgi?id=70205 Bad behavior The issue affects SourceInsight 4 in particular. SourceInsight has its own built-in theme functionality which doesn't get along well with any non-standard Wine theme. When a non-standard Wine theme is selected, then the main toolbar in SI4 ignores its app theme and always gets drawn with the selected Wine theme. Selecting the default Wine theme fixes the issue - the toolbar is drawn according to the app theme. On Windows it's ok no matter which UI theme is set. Screenshot of the issue is attached. The root cause of the issue is that UXTHEME_broadcast_msg/UXTHEME_broadcast_msg_enumchild in dlls/uxtheme/system.c both use a PostMessage() call to send WM_THEMECHANGED to affected window(s). In SI4 the main toolbar is implemented as a combination of a custom container window (si_Rebar class) and a standard win32 Rebar control (RebarWindow32 class). Immediately after creating the RebarWindow32 window, SI4 does SetWindowTheme(hwndRebar, L" ", L" ") for it. According to MSDN (https://docs.microsoft.com/en-us/windows/win32/api/uxtheme/nf-uxtheme-setwi…) > The theme manager retains the pszSubAppName and the pszSubIdList associations through the lifetime of the window, even if visual styles subsequently change. The window is sent a WM_THEMECHANGED message at the end of a SetWindowTheme call, so that the new visual style can be found and applied. > > When pszSubAppName and pszSubIdList are NULL, the theme manager removes the previously applied associations. You can prevent visual styles from being applied to a specified window by specifying an empty string, (L" "), which does not match any section entries. - this L" ", L" " stuff means that SI4 DOES NOT want for system visual styles being applied to its RebarWindow32 control. However, according to WINEDEBUG logs they were applied to all bg erase, painting etc operations no matter the SetWindowTheme(, L" ", L" ") call. Turns out that RebarWindow32' WndProc receives WM_THEMECHANGED too late, after all stuff including drawing already happened with the system-wide theme being applied. The reason why it was received so late is simple - SetWindowTheme implementation in wine uses PostMessage() instead of SendMessage(). Replacing it with a SendMessage() call allows to fix the bug. I've checked what Windows actually does in SetWindowTheme and found out that it always uses SendMessage to send WM_THEMECHANGED (for any HWND). So. suggested fix: diff --git a/dlls/uxtheme/system.c b/dlls/uxtheme/system.c index a37e532500a..3b6e6d2b6b6 100644 --- a/dlls/uxtheme/system.c +++ b/dlls/uxtheme/system.c @@ -59,7 +59,7 @@ static WCHAR szCurrentSize[64]; static BOOL CALLBACK UXTHEME_broadcast_msg_enumchild (HWND hWnd, LPARAM msg) { - PostMessageW(hWnd, msg, 0, 0); + SendMessageW(hWnd, msg, 0, 0); return TRUE; } @@ -72,7 +72,7 @@ static BOOL CALLBACK UXTHEME_broadcast_msg (HWND hWnd, LPARAM msg) } else { - PostMessageW(hWnd, msg, 0, 0); + SendMessageW(hWnd, msg, 0, 0); EnumChildWindows (hWnd, UXTHEME_broadcast_msg_enumchild, msg); } return TRUE; -- 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.

1 10