June 2025 - Wine-GitLab - list.winehq.org

[PATCH v2 0/7] MR8415: mf: Get rid of the IMFMediaShutdownNotify interface.
by Rémi Bernon July 7, 2025

July 7, 2025

As discussed in !8402. @cmccarthy what do you think of this? I think queueing an event right before shutting down the queue is enough to get the media session notified? It won't get the actual event but it will be able to see the MF_E_SHUTDOWN error after calling `EndGetEvent`? -- v2: include: Remove now unnecessary IMFMediaShutdownNotify interface. mf/session: Remove now unnecessary IMFMediaShutdownNotify. winegstreamer: Remove now unnecessary IMFMediaShutdownNotify. mf/session: Handle an optional MEError event from sources on shutdown. winegstreamer: Queue an event before shutting down the event queues. mfsrcsnk: Queue an event before shutting down the event queues. mfplat/tests: Add more tests for event queue shutdown. https://gitlab.winehq.org/wine/wine/-/merge_requests/8415

3 13

[PATCH v6 0/7] MR8402: mf/session: Use a dedicated state when source is shutdown.
by Rémi Bernon July 7, 2025

July 7, 2025

This should fix some spurious test failure in `test_media_session_Close`, as sometimes the source shutdown happens quickly enough and changes the session state to SESSION_STATE_STOPPED, causing the later Close command to succeed when it consistently returns E_SHUTDOWN on Windows. -- v6: mf/session: Simplify the media session shutdown event handling. mf/session: Introduce a SESSION_FLAG_SOURCE_SHUTDOWN presentation flag. mf/session: Replace SESSION_FLAG_END_OF_PRESENTATION with dedicated states. mf/session: Replace SESSION_FLAG_FINALIZE_SINKS with dedicated states. mf/session: Remove unnecessary SESSION_FLAG_PENDING_COMMAND flag. mf/session: Move internal states to a separate command_state enum. mf/session: Clarify internal states from session states separation. https://gitlab.winehq.org/wine/wine/-/merge_requests/8402

2 10

[PATCH 0/1] MR8429: ddraw/tests: Release device after ddraw.
by Yuxuan Shui (＠yshui) July 7, 2025

July 7, 2025

Fix a use-after-free since device holds reference to ddraw surface, which in turn holds reference to ddraw. supersedes !8419 -- https://gitlab.winehq.org/wine/wine/-/merge_requests/8429

4 3

[PATCH v2 0/1] MR8421: dxgi/tests: Fix out-of-bound in test_cursor_clipping.
by Yuxuan Shui (＠yshui) July 7, 2025

July 7, 2025

Missing a bound check for "modes". -- v2: dxgi/tests: Fix out-of-bound in test_cursor_clipping. https://gitlab.winehq.org/wine/wine/-/merge_requests/8421

4 3

[PATCH 0/1] MR8407: wined3d: Fix missing data/resource type bounds check.
by Yuxuan Shui (＠yshui) July 7, 2025

July 7, 2025

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

4 3

[PATCH 0/3] MR8417: Draft: ntoskrnl.exe: Implement Io{Get,Set}DeviceInterfacePropertyData.
by Vibhav Pant (＠vibhavp) July 3, 2025

July 3, 2025

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

3 4

[PATCH 0/1] MR8236: dxcore/tests: Skip tests when there is no display available.
by Bernhard Übelacker July 3, 2025

July 3, 2025

[Test pattern page.](https://test.winehq.org/data/patterns.html#dxcore:dxcore) [Testbot run with this patch.](https://testbot.winehq.org/JobDetails.pl?Key=158548) -- https://gitlab.winehq.org/wine/wine/-/merge_requests/8236

2 2

[PATCH 0/31] MR7985: Draft: server: Sync interface refactor in prepration for inproc sync.
by Rémi Bernon July 3, 2025

July 3, 2025

As an overview for https://gitlab.winehq.org/wine/wine/-/merge_requests/7848 -- This merge request has too many patches to be relayed via email. Please visit the URL below to see the contents of the merge request. https://gitlab.winehq.org/wine/wine/-/merge_requests/7985

1 1

[PATCH 0/3] MR7045: Draft: win32u: Misc tweaks for vulkan surface offscreening.
by Rémi Bernon July 3, 2025

July 3, 2025

Similar to https://gitlab.winehq.org/wine/wine/-/merge_requests/7034 -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7045

1 4

[PATCH 0/1] MR8454: ntdll: Don't skip synchronous read when serial read timeout is infinite.
by Alex Henrie (＠alexhenrie) July 2, 2025

July 2, 2025

If get_io_timeouts sets the interval timeout to 0, it means that the read should return immediately even if there is no data. If get_io_timeouts sets the interval timeout to -1, it means that the read operation should wait indefinitely for the next byte. In either case, the interval timer is not used, so there's no need to worry about forgetting to start it, and the delay in returning data was causing a problem in Ti99Hdx. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=42882 -- https://gitlab.winehq.org/wine/wine/-/merge_requests/8454

3 8