February 2024 - Wine-GitLab

[PATCH 0/1] MR5076: explorer: Set layered style on systray icons on creation if we don't use our own taskbar.
by Gabriel Ivăncescu Feb. 14, 2024

Feb. 14, 2024

Turns out I broke the non virtual desktop case in some cases. Sorry about that. This basically uses previous behavior for such (`enable_taskbar` is what's used to also determine layered changes in rest of code) while keeping the fix for virtual desktops (i.e. our own taskbar). Works correctly for me, but let me know if I did something wrong again (welp). -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5076

4 13

[PATCH 0/1] MR1425: ntdll: Return FILE_DEVICE_DISK for Unix FIFOs and sockets from get_device_info().
by Paul Gofman (＠gofman) Feb. 14, 2024

Feb. 14, 2024

Currently GetFileType() ends up returning the file type solely based on Unix fd type if it gets it from server. The problematic case is when our process gets a pipe or socket fd as a stdin or stderr from Unix. The server object which gets created through wine_server_fd_to_handle is a regular file regardless of the underlying Unix fd type. It probably can't be anything else, at least for pipes, as the pipe should have both ends but we have only one in this case. That causes problems, e. g., with libuv (used, e. g., by Vampire Survivors). It checks stdout handle type and if it is pipe it tries to do SetNamedPipeHandleState() on it and does not tolerate the failure. It looks more sensible to me to report all the pipes and sockets created through wine_server_fd_to_handle() as regular files as that matches the server objects we have for them. When that is not the case we should get the correct type from server fd type. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/1425

4 4

[PATCH 0/7] MR5082: winebuild: Preparation for ARM64X support
by Jacek Caban (＠jacek) Feb. 14, 2024

Feb. 14, 2024

Right now we filter entry points for the target architecture when parsing .spec file. On ARM64X, we're interested in entry points for two different targets. On MSVC (and experimental LLVM), creating importlibs that support both ARM64EC and ARM64 requires passing two .def files. With .spec files, we may generate them both from the same .spec file. This separates per-target exports into a separate struct, while parser stores all entry points specified in the .spec file. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5082

2 7

[PATCH v3 0/7] MR5074: wininet: Improve proxy configuration reading and writing (part 2).
by Piotr Caban (＠piotr) Feb. 14, 2024

Feb. 14, 2024

-- v3: inetcpl.cpl: Use wininet functions to load and save proxy settings. https://gitlab.winehq.org/wine/wine/-/merge_requests/5074

2 7

[PATCH v3 0/2] MR4518: ntdll: Integrate with GDB using r_debug.
by Rémi Bernon Feb. 14, 2024

Feb. 14, 2024

Effectively implementing the debugger interface as described in https://sourceware.org/git/?p=glibc.git;a=blob;f=elf/rtld-debugger-interfac… This is an actual attempt at having this upstream, split from https://gitlab.winehq.org/wine/wine/-/merge_requests/1074 which people have been finding useful for debugging Wine directly in GDB. This supports everything you would expect, from automatic symbol loading as well as cross-syscall backtraces with the new Python unwinder. -- v3: ntdll: Maintain a PE module link map and expose it to GDB. loader: Expose the standard debugging symbols for GDB. https://gitlab.winehq.org/wine/wine/-/merge_requests/4518

2 4

Re: [PATCH v2 0/8] MR5074: wininet: Improve proxy configuration reading and writing (part 2).
by Piotr Caban (＠piotr) Feb. 14, 2024

Feb. 14, 2024

On Wed Feb 14 13:42:53 2024 +0000, Jacek Caban wrote: > Windows CI failure seems related. It looks like there's something strange happening because of PAC script tests. I'm still looking into it. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5074#note_61165

1 0

[PATCH v2 0/3] MR5081: Draft: dmime: Read through a MIDI file
by Yuxuan Shui (＠yshui) Feb. 14, 2024

Feb. 14, 2024

Add a dummy track parser, that reads through MIDI tracks and events. To make sure we understand the file structure correctly, no actual tracks or events are generated. Also add test cases to make sure we read through a MIDI file correctly. This is skeleton of the actual MIDI parser. Pending on the merge of !4982 -- v2: dmime: Read through a MIDI file. https://gitlab.winehq.org/wine/wine/-/merge_requests/5081

2 3

[PATCH 0/3] MR5081: Draft: dmime: Read through a MIDI file
by Yuxuan Shui (＠yshui) Feb. 14, 2024

Feb. 14, 2024

Add a dummy track parser, that reads through MIDI tracks and events. To make sure we understand the file structure correctly, no actual tracks or events are generated. Also add test cases to make sure we read through a MIDI file correctly. This is skeleton of the actual MIDI parser. Pending on the merge of !4982 -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5081

2 3

[PATCH 0/2] MR651: tests: Add some tests for rasteriser-ordered views.
by Henri Verbeet (＠hverbeet) Feb. 14, 2024

Feb. 14, 2024

-- https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/651

4 3

[PATCH v2 0/2] MR4518: ntdll: Integrate with GDB using r_debug.
by Rémi Bernon Feb. 14, 2024

Feb. 14, 2024

Effectively implementing the debugger interface as described in https://sourceware.org/git/?p=glibc.git;a=blob;f=elf/rtld-debugger-interfac… This is an actual attempt at having this upstream, split from https://gitlab.winehq.org/wine/wine/-/merge_requests/1074 which people have been finding useful for debugging Wine directly in GDB. This supports everything you would expect, from automatic symbol loading as well as cross-syscall backtraces with the new Python unwinder. -- v2: ntdll: Maintain a PE module link map and expose it to GDB. loader: Expose the standard debugging symbols for GDB. https://gitlab.winehq.org/wine/wine/-/merge_requests/4518

2 6