February 2025 - Wine-GitLab

[PATCH 0/1] MR7445: ntdll/tests: Skip FileFsFullSizeInformationEx test on older windows.
by Bernhard Übelacker Feb. 28, 2025

Feb. 28, 2025

[Testbot shows failures](https://test.winehq.org/data/patterns-tb-win.html#ntdll:file) since a few days in ntdll:file on older windows versions. These failures seem to be related to 37c5fa3d and f15bd29c (CC: @cmccarthy). This patch just adds `STATUS_INVALID_INFO_CLASS` and moves the `ok` statement below the `win_skip`. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7445

2 5

[PATCH v8 0/1] MR7288: winegstreamer: Avoid large buffer pushes in wg_transform.
by Yuxuan Shui (＠yshui) Feb. 28, 2025

Feb. 28, 2025

## Context This is a problem discovered when running "Max: The Curse of Brotherhood" under proton. This game writes 4MB a piece into `wg_transform`, which contains about 4 seconds of compressed video. `wg_transform` calls `gst_pad_push` in `transform_ProcessOutput`, which takes \~300ms (i.e. 20 frames @ 60fps) to decode this buffer of video. So the end result is the game hitches every 4 seconds while playing cut scene videos. Proton currently has a special case for this particular game, for which it breaks up the buffer into small chunks to avoid long blocks. This MR adopts that and applies it generally. One concern raised by @redmcg is: > The only issue I can think of is if there are any decoders which don't have a parser; then they might not know how to deal with an arbitrary 4096 byte buffer (the parser is generally responsible for taking arbitrary buffers and producing something the decoder can work with, for example: a full frame). So this MR only enables this strategy when there is a parser element. -- v8: winegstreamer: Avoid large buffer pushes in wg_transform. https://gitlab.winehq.org/wine/wine/-/merge_requests/7288

2 2

[PATCH v4 0/8] MR7424: winebth.sys part 5: Update properties for tracked remote devices.
by Vibhav Pant (＠vibhavp) Feb. 28, 2025

Feb. 28, 2025

This adds to the basic infrastructure needed for device inquiry/scanning. Also, fixes radio properties being incorrectly updated. -- v4: winebth.sys: Update properties for tracked remote devices on receiving PropertiesChanged for org.bluez.Device1 objects from BlueZ. winebth.sys: Only set the updated properties for local radios on BLUETOOTH_WATCHER_EVENT_TYPE_RADIO_PROPERTIES_CHANGED. winebth.sys: Set the device class for remote devices from BlueZ's "Class" property. winebth.sys: Use the "Trusted" property from BlueZ device objects to set BDIF_PERSONAL. winebth.sys: Use the "Name" property of a BlueZ adapter for the local radio name. winebth.sys: Don't iterate over the remaining radios once a local device has been removed. winebth.sys: Initially set numOfDevices to 0 in IOCTL_BTH_GET_DEVICE_INFO. winebth.sys: Use the correct DBus property name in IOCTL_WINEBTH_RADIO_SET_FLAG. https://gitlab.winehq.org/wine/wine/-/merge_requests/7424

3 11

Re: [PATCH v6 0/2] MR1263: kernelbase: Fix VerQueryValueW with no data
by Mark Jansen (＠learn-more) Feb. 28, 2025

Feb. 28, 2025

Thanks! -- https://gitlab.winehq.org/wine/wine/-/merge_requests/1263#note_96216

1 0

[PATCH 0/1] MR7430: rtworkq/tests: Match return values of RtwqPutWorkItem returned in windows.
by Bernhard Übelacker Feb. 28, 2025

Feb. 28, 2025

Followup to c641a9a2 and b7fa3068. Failures of many windows tests show up in [1] since a few days. Seems CI was not happy about it in the original MR too. [2][3] 1. https://test.winehq.org/data/patterns.html#rtworkq:rtworkq 2. https://gitlab.winehq.org/cmccarthy/wine/-/jobs/134360#L102 3. https://gitlab.winehq.org/cmccarthy/wine/-/jobs/134361#L102 CC: @cmccarthy -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7430

3 7

[PATCH v2 0/2] MR7443: Draft: d2d1/tests: Add some tests for device context handling in the DC target.
by Nikolay Sivov (＠nsivov) Feb. 28, 2025

Feb. 28, 2025

Signed-off-by: Nikolay Sivov <nsivov(a)codeweavers.com> -- v2: d2d1: Update DC target surface with current HDC contents on BeginDraw(). https://gitlab.winehq.org/wine/wine/-/merge_requests/7443

2 2

[PATCH 0/2] MR7443: Draft: d2d1/tests: Add some tests for device context handling in the DC target.
by Nikolay Sivov (＠nsivov) Feb. 28, 2025

Feb. 28, 2025

Signed-off-by: Nikolay Sivov <nsivov(a)codeweavers.com> -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7443

2 2

[PATCH 0/1] MR7442: win32u: Also set DriverVersion for software devices such as llvmpipe.
by Hans Leidekker (＠hans) Feb. 28, 2025

Feb. 28, 2025

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

2 1

[PATCH 0/3] MR7429: winex11: Support absolute rawinput events and use window-relative coordinates.
by Rémi Bernon Feb. 28, 2025

Feb. 28, 2025

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=51357 Now that we're tracking window position changes as they arrive, they should always be consistent with the received mouse input events. Absolute rawinput is useful for tablets, touchpad or touchscreen when they are exposed as absolute mouse devices. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7429

3 10

[PATCH v6 0/8] MR7152: dxgi: Fix the frame latency waitable implementation.
by Giovanni Mascellani (＠giomasce) Feb. 28, 2025

Feb. 28, 2025

This is an alternative proposal to !5830. It fixes the same glitches in Horizon Zero Dawn, but attempts to do that by implementing the proper behavior expected from the swapchain. More precisely, it fixes a few mistakes I had made the last time I touched this code, it implements the frame latency waitable with a semaphore instead of an event (as it should be) and at last it uses the frame latency waitable to implement an appropriate wait after presentation when the client didn't request to manage the waitable directly. This implementation is not yet complete, because the semaphore should be released when the frame is presented. Knowing when this is the case would require using `VK_KHR_present_wait`. We currently approximate that with the moment in which the frame is submitted for presentation to Vulkan, which as far as I can tell is good enough. Eventually I'll try to write the proper thing. This MR depends on https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/1343, which has been submitted in the meantime to vkd3d. The vkd3d change is included in the first commit, so this MR is already functional. -- v6: dxgi/tests: Use an explicit frame latency waitable when testing the back buffer index. dxgi: Wait on the frame latency semaphore when the client doesn't do it. https://gitlab.winehq.org/wine/wine/-/merge_requests/7152

4 12