February 2023 - Wine-GitLab

[PATCH 0/1] MR2097: wbemprox: Recognize Windows 11.
by Hans Leidekker (＠hans) Feb. 2, 2023

Feb. 2, 2023

-- https://gitlab.winehq.org/wine/wine/-/merge_requests/2097

2 1

[PATCH v3 0/2] MR46: vkd3d-shader/spirv: Do not write the point size if shaderTessellationAndGeometryPointSize is disabled.
by Zebediah Figura (＠zfigura) Feb. 2, 2023

Feb. 2, 2023

-- v3: vkd3d: Do not write the point size for SPIR-V shaders. vkd3d-shader/spirv: Introduce an option to control whether point size is written. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/46

3 4

[PATCH v6 0/1] MR74: vkd3d-shader/hlsl: Support dot() for SM1.
by Nikolay Sivov (＠nsivov) Feb. 2, 2023

Feb. 2, 2023

-- v6: vkd3d-shader/hlsl: Support dot() for SM1. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/74

5 6

[PATCH 0/4] MR2096: msi: Perform late initialization of the assembly caches
by Hans Leidekker (＠hans) Feb. 2, 2023

Feb. 2, 2023

-- https://gitlab.winehq.org/wine/wine/-/merge_requests/2096

2 4

[PATCH 0/1] MR2095: include: Add uiviewsettingsinterop.idl.
by Zhiyi Zhang (＠zhiyi) Feb. 2, 2023

Feb. 2, 2023

-- https://gitlab.winehq.org/wine/wine/-/merge_requests/2095

2 1

[PATCH 0/1] MR2094: include: Add missing DXGI_COLOR_SPACE_TYPE enumeration values.
by Kacper Michajłow Feb. 2, 2023

Feb. 2, 2023

Signed-off-by: Kacper Michajłow <kasper93(a)gmail.com> -- https://gitlab.winehq.org/wine/wine/-/merge_requests/2094

1 1

[PATCH v3 0/1] MR1975: Add indeo 5 video format support in winegstreamer.
by Shaun Ren (＠shaunren) Feb. 2, 2023

Feb. 2, 2023

-- v3: https://gitlab.winehq.org/wine/wine/-/merge_requests/1975

2 3

[PATCH v2 0/1] MR2082: opengl32/tests: Skip the wglCopyContext test on Nvidia on Windows.
by Alex Henrie (＠alexhenrie) Feb. 1, 2023

Feb. 1, 2023

Fixes a testbot crash. -- v2: opengl32/tests: Skip the wglCopyContext test on Nvidia on Windows. https://gitlab.winehq.org/wine/wine/-/merge_requests/2082

4 10

[PATCH 0/1] MR2092: opengl32/tests: Make context current before calling wglCopyContext().
by Zhiyi Zhang (＠zhiyi) Feb. 1, 2023

Feb. 1, 2023

Otherwise, wglCopyContext() crashes on Windows with a NVIDIA GPU and fails on Windows with a AMD GPU. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=51311 Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54103 -- https://gitlab.winehq.org/wine/wine/-/merge_requests/2092

2 1

[PATCH v4 0/2] MR2059: combase: Generate apartment OXID in rpcss
by Aaron Hill (＠Aaron1011) Feb. 1, 2023

Feb. 1, 2023

Currently, apartment OXIDs are generated using the process ID (and the thread ID for a single threaded-apartment). This means that if an apartment is destroyed and re-created (using `CoUninitialize` followed by `CoInitializeEx`), the newly created apartment will end up with the same OXID as the old apartment. However, testing shows that Windows will generate a *new* OXID when an apartment is created in the above manner. This patch uses `rpcss` to generate a new OXID. The current process id is combined with an incrementing counter stored in rpcss. This ensures that re-creating an apartment will not re-use an OXID. Additionally, this fixes an issue that caused the .NET 4.8 installer to become stuck during the downloading stage under Wine. The installer appears to perform the following actions: 1. Call `IBackgroundCopyJob_SetNotify` interface on a BITS job. This causes us to create a proxy (in the other process hosting 'qmgr') for the `IBackgroundCopyCallback` pointer passed as a parameter. 2. Trigger MTA apartment re-creation (in the process running the setup, *not* the process with the `IBackgroundCopyCallback` proxy) through `CoUninitialize` followed by `CoInitializeEx`. 3. Call `IBackgroundCopyJob_SetNotify` on a newly created job, but with the same `IBackgroundCopyCallback` pointer parameter. When we deserialize the pointer passed to `IBackgroundCopyJob_SetNotify`, we will end up re-using the same `proxy_manager` that we created for the previous `IBackgroundCopyCallback`. This is due to the fact that the OIDs happen to match (due to the fact that the .NET 4.8 setup appears to perform actions in the same order between the old and new apartments), and the apartment OXIDs match as explained above. above. As a result, we will use the old IPID when we send RPC packets using this `proxy_manager`. However, the new and old IPIDs will *never* match, since their generation process includes `RtlGenRandom`. This will cause a fault packet to be generated on the listening side of the RPC connection. By avoiding re-using OXIDs across re-created apartments, we ensure that the proxy side will never incorrectly re-use a stale `proxy_manager`. -- v4: combase: Generate apartment OXID in rpcss ole32/tests: Test that re-creating an apartment results in a new OXID https://gitlab.winehq.org/wine/wine/-/merge_requests/2059

3 5