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

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

Feb. 25, 2022

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 48201] New: unimplemented function KERNEL32.dll.SetCurrentConsoleFontEx
by WineHQ Bugzilla Feb. 25, 2022

Feb. 25, 2022

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 51348] New: uxtheme.SetWindowTheme should use SendMessage to send WM_THEMECHANGED
by WineHQ Bugzilla Feb. 25, 2022

Feb. 25, 2022

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

[Bug 51303] New: Metal Gear Solid V: Ground Zeroes needs d3d11_swapchain_GetLastPresentCount implementation
by WineHQ Bugzilla Feb. 25, 2022

Feb. 25, 2022

https://bugs.winehq.org/show_bug.cgi?id=51303 Bug ID: 51303 Summary: Metal Gear Solid V: Ground Zeroes needs d3d11_swapchain_GetLastPresentCount implementation Product: Wine Version: 6.11 Hardware: x86-64 OS: Linux Status: NEW Keywords: patch Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Silently stops with 0b30:fixme:dxgi:d3d11_swapchain_GetLastPresentCount iface 0x2c3aa70, last_present_count 0x41df3a0 stub! 0b30:err:seh:NtRaiseException Unhandled exception code c0000005 flags 0 addr 0x14129dc2b Temporary workaround https://www.winehq.org/pipermail/wine-devel/2021-May/187851.html -- 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 50412] New: Wrong check for needed access rights in QueryServiceConfig2
by WineHQ Bugzilla Feb. 25, 2022

Feb. 25, 2022

https://bugs.winehq.org/show_bug.cgi?id=50412 Bug ID: 50412 Summary: Wrong check for needed access rights in QueryServiceConfig2 Product: Wine Version: 6.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: dalai82(a)gmx.net Distribution: --- Hi there. While checking out Total Commander and one of my own TC plugins on Wine 4.0.2 on Debian 10.7 I saw that it failed to read the description of all services. After double-checking my code (and confirming its correctness) I saw Wine's output on the terminal: > 006b:err:service:validate_context_handle Access denied - handle created with access 1, needed 4 Then I downloaded the source code of the current version dev version 6.0-rc4, searched all files (because I didn't know where to look) and found the culprit in programs/services/rpc.c, more precise in function svcctl_QueryServiceConfig2W where it makes the call to validate_service_handle() in line 984. The bug and fix for it is simple: The needed access right must be SERVICE_QUERY_CONFIG instead of SERVICE_QUERY_STATUS, since it's the service config queried here, not its status. Out of curiosity, I checked half a dozen older versions and found that this bug has been in the code since its implementation back in Wine 1.1.14. This more than a decade old wine didn't age well ;). But I guess this is a simple copy'n'paste error. Maybe check for similar bugs/mistakes in the other functions when fixing this one. 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.

1 9

[Bug 48891] New: Cannot run any utility from msys2/git-bash
by WineHQ Bugzilla Feb. 25, 2022

Feb. 25, 2022

https://bugs.winehq.org/show_bug.cgi?id=48891 Bug ID: 48891 Summary: Cannot run any utility from msys2/git-bash Product: Wine Version: 5.5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: megastallman(a)gmail.com Distribution: --- Trying next steps after rebuilding wine-staging-5.5 with a patch, that fixes https://bugs.winehq.org/show_bug.cgi?id=48882 002b:fixme:netapi32:NetUserGetInfo Only implemented for local computer, but remote serverL"\\\\@" was requested. Cygwin WARNING: Couldn't compute FAST_CWD pointer. This typically occurs if you're using an older Cygwin version on a newer Windows. Please update to the latest available Cygwin version from https://cygwin.com/. If the problem persists, please see https://cygwin.com/problems.html -- 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 32

[Bug 36887] New: Installing Trusteer Rapport software failed. See trace.
by wine-bugs＠winehq.org Feb. 25, 2022

Feb. 25, 2022

http://bugs.winehq.org/show_bug.cgi?id=36887 Bug ID: 36887 Summary: Installing Trusteer Rapport software failed. See trace. Product: Wine Version: 1.7.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mnoock(a)gmail.com Created attachment 48980 --> http://bugs.winehq.org/attachment.cgi?id=48980 Installing Trusteer Rapport software failed. See trace. Installing Trusteer Rapport software failed. See trace. -- 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 51302] New: NASCAR '15 Victory Edition needs d3dx_effect_ValidateTechnique implementation
by WineHQ Bugzilla Feb. 25, 2022

Feb. 25, 2022

https://bugs.winehq.org/show_bug.cgi?id=51302 Bug ID: 51302 Summary: NASCAR '15 Victory Edition needs d3dx_effect_ValidateTechnique implementation Product: Wine Version: 6.11 Hardware: x86-64 OS: Linux Status: NEW Severity: minor Priority: P2 Component: directx-d3d-util Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Shows a black screen and looping of 0158:fixme:d3dx:d3dx_effect_ValidateTechnique iface 02ACF2C8, technique 0C6460A8 semi-stub. 0158:fixme:d3dx:d3dx_effect_ValidateTechnique iface 02ACF2C8, technique 0C6460C0 semi-stub. 0158:fixme:d3dx:d3dx_effect_ValidateTechnique iface 02ACF2C8, technique 0C6460D8 semi-stub. -- 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 8

[Bug 51264] New: GUI exe receives invalid StdOutput HANDLE if launched via ShellExecuteEx
by WineHQ Bugzilla Feb. 25, 2022

Feb. 25, 2022

https://bugs.winehq.org/show_bug.cgi?id=51264 Bug ID: 51264 Summary: GUI exe receives invalid StdOutput HANDLE if launched via ShellExecuteEx Product: Wine Version: 6.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: brendan(a)redmandi.com Distribution: --- Created attachment 70142 --> https://bugs.winehq.org/attachment.cgi?id=70142 Source code for the primary exe to recreate the issue It is possible for a child process to inherit an invalid hStdOutput HANDLE if the PE header has the subsystem value of IMAGE_SUBSYSTEM_WINDOWS_GUI and it is launched via ShellExecuteEx. It also requires the primary process to be launched via: - 'wine' if it is a PE32+ executable; or - 'wine64' if it is a PE32 executable Attached are two source files that can be used to recreate the issue: 1. main.c (the primary process); and 2. child.c (the child process) Compile with: x86_64-w64-mingw32-gcc -o main.exe main.c x86_64-w64-mingw32-gcc -o child.exe child.c -mwindows and run with: wine main.exe The child.exe creates a file called 'stdout.log' that dumps the STD_OUTPUT_HANDLE value and its FileType. Under wine, this is: StdOutput: 14, Type: 1 and under Windows, it is: StdOutput: 0, Type: 0 I first ran in this this issue when running Elite Dangerous from Proton 6.3 (i.e. wine version 6.3) - but my investigations show this still occurs with git commit 6b277dc89d55. -- 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 11

[Bug 50735] New: MSBuild fails to launch FileTracker
by WineHQ Bugzilla Feb. 25, 2022

Feb. 25, 2022

https://bugs.winehq.org/show_bug.cgi?id=50735 Bug ID: 50735 Summary: MSBuild fails to launch FileTracker Product: Wine Version: 6.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: rpisl(a)seznam.cz Distribution: --- Created attachment 69503 --> https://bugs.winehq.org/attachment.cgi?id=69503 WINEDEBUG=+relay,+process,+module,+loaddll BAD MSBuild from Visual Studio build tools 2019 fails to launch FileTracker which is needed for incremental builds. This apply for Wine 6.3 but it works on Staging. I bisected this to wow64cpu patchset which is tracked in bug 45567. Then I found that there are patches for wow64cpu on the list for upstream. But these don't fix the problem. So after investigating this further I've found this: what really fixes the problem is calling load_builtin_dll() in process_init() and this builtin dll must not be in PE format. If -mno-cygwin is enabled, it does not work. It is not important which exports the library has, no need for setting Wow64Transition. I'm attaching two traces - good and bad. Maybe someone could identify what is happening here. -- 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