- Wine-GitLab - list.winehq.org

[PATCH v2 0/1] MR10556: odbc32: Report SQL_TIMESTAMP format for timestamp data in ODBC 2.x application.
by Piotr Caban (＠piotr) April 20, 2026

April 20, 2026

-- v2: odbc32: Support data type conversion on version mismatch. https://gitlab.winehq.org/wine/wine/-/merge_requests/10556

3 3

[PATCH 0/1] MR10439: crypt32: Protect certificate context from repeated releases.
by Dmitry Timoshkov (＠dmitry) April 20, 2026

April 20, 2026

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

3 14

[PATCH 0/1] MR10701: gitlab: Add nasm to the CI docker images.
by Rémi Bernon (＠rbernon) April 20, 2026

April 20, 2026

For https://gitlab.winehq.org/wine/wine/-/merge_requests/10687 -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10701

2 1

[PATCH v7 0/1] MR10561: secur32: Fix handling by SChannel for CNG/NCrypt client certificates for mTLS
by Benoît Legat (＠blegat) April 20, 2026

April 20, 2026

Part 3 of my attempt to run the [Niko Home Control programming software](https://appdb.winehq.org/objectManager.php?sClass=application&iId… under Wine. If I understand correctly, the current implementation only supports retrieving via the legacy CryptoAPI (CAPI). The Niko app uses Cryptography Next Generation (CNG/NCrypt) so this PRs adds support for it in acquire_credentials_handle. -- v7: secur32: Fix handling by SChannel for CNG/NCrypt client certificates for mTLS https://gitlab.winehq.org/wine/wine/-/merge_requests/10561

4 6

[PATCH v8 0/2] MR10659: combase: Implement restricted WinRT error handling APIs.
by Anna R Békefi (＠annareginabekefi) April 20, 2026

April 20, 2026

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=58900 Bug 58900 This series implements restricted WinRT error handling in combase and\ adds conformance tests for the new behavior. Implemented APIs include restricted error creation / retrieval,\ error context capture, transform, matching, and unhandled error reporting\ paths. Tests were added under dlls/combase/tests and pass locally.\ The existing combase tests also continue to pass. -- v8: combase/tests: Add tests for restricted WinRT error handling. combase: Implement restricted WinRT error handling APIs. https://gitlab.winehq.org/wine/wine/-/merge_requests/10659

2 2

[PATCH v4 0/10] MR10645: mf/topology_loader: Insert optional nodes after each branch is connected.
by Conor McCarthy (＠cmccarthy) April 20, 2026

April 20, 2026

New tests show each optional node is connected after the nodes on either side are connected. This is an issue in the game Psycho Sleuth (at least in the demo) because it uses a transform which must have its input types enumerated before it will work correctly. This occurs when a decoder is inserted before the transform, but an optional node lies immediately upstream of the transform, and if optional nodes are not handled correctly, the decoder is initially connected to the optional instead of being inserted later. A couple of other issues revealed while making new tests are fixed here too. -- v4: mf/topology_loader: Remove the fixme from topology_loader_Load(). https://gitlab.winehq.org/wine/wine/-/merge_requests/10645

2 10

[PATCH v3 0/9] MR10645: mf/topology_loader: Insert optional nodes after each branch is connected.
by Conor McCarthy (＠cmccarthy) April 20, 2026

April 20, 2026

New tests show each optional node is connected after the nodes on either side are connected. This is an issue in the game Psycho Sleuth (at least in the demo) because it uses a transform which must have its input types enumerated before it will work correctly. This occurs when a decoder is inserted before the transform, but an optional node lies immediately upstream of the transform, and if optional nodes are not handled correctly, the decoder is initially connected to the optional instead of being inserted later. A couple of other issues revealed while making new tests are fixed here too. -- v3: mf/topology_loader: Try to insert optional nodes after resolving the surrounding branch. mf/topology_loader: Resolve topologies by walking down from each source node. mf/topology_loader: Introduce a helper to get the connection semantic flags. mf/tests: Test optional topology nodes. mf/tests: Fix comments for two topology loader tests. https://gitlab.winehq.org/wine/wine/-/merge_requests/10645

2 9

[PATCH 0/1] MR10698: kernelbase: Add message string for error 302-316
by Antoine Leresche (＠A2va) April 19, 2026

April 19, 2026

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

2 1

[PATCH v2 0/1] MR10696: shcore: 0 terminate params->WindowTitle when turning into WCHAR
by Marcus Meissner (＠msmeissn) April 19, 2026

April 19, 2026

WindowTitle is not necessarily NUL terminated. Reported-By: Dirk Mueller <dmueller(a)suse.de> Found-by: Gemini 3.1 Pro Signed-off-by: Marcus Meissner <marcus(a)jet.franken.de> -- v2: shcore: 0 terminate params->WindowTitle when turning into WCHAR https://gitlab.winehq.org/wine/wine/-/merge_requests/10696

4 4

[PATCH 0/1] MR10276: ntdll/wineandroid: Redirect stdout/stderr to Android logcat in the Java startup path
by Twaik Yont (＠twaik) April 19, 2026

April 19, 2026

This change redirects Wine’s `stdout` and `stderr` to Android `logcat` when running through the Java entry point used by `wineandroid.drv`. Currently `WineActivity` writes debug output to a file via the `WINEDEBUGLOG` mechanism. In practice this is inconvenient to use: the file lives in the application's private storage and reading it on a device typically requires either a debug build or root access. Even when accessible, inspecting logs directly on the device is less practical than using Android’s standard logging tools. Android applications normally expose diagnostic output through logcat. This change forwards Wine’s `stdout` and `stderr` to `logcat` so that Wine debug output can be observed using standard Android tooling (`adb logcat`, Android Studio, etc.) without accessing the application’s internal storage. The implementation is intentionally simple and best-effort. A pipe is installed on `stdout` and `stderr` and a small detached thread forwards the output to `__android_log_write()`. Data is forwarded in chunks without reconstructing line boundaries; this is sufficient for diagnostic purposes and keeps the implementation minimal. The redirection is only enabled in the Android Java startup path, which corresponds to the environment used by `wineandroid`. In this configuration `stdout` and `stderr` are typically not visible to the user (commonly pointing to `/dev/null`), so redirecting them to logcat does not replace any usable diagnostics channel. It is also unlikely that Wine will be compiled directly on Android devices in practice. Android does not provide an official NDK toolchain that runs on-device, and mingw toolchains are not distributed for Android either. Building Wine therefore normally happens off-device using standard cross-compilation toolchains (android NDK, mingw, host toolchain). Because of this, the `logcat` forwarding is primarily intended for runtime diagnostics and debugging rather than build-time development directly on the device. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10276

3 6