- wine-gitlab - winehq.org

[PATCH 0/6] MR8821: mshtml: Implement DOMParser.
by Gabriel Ivăncescu (＠insn) 22 Aug '25

22 Aug '25

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

3 10

[PATCH v6 0/5] MR8786: Draft: winebuild: Add flag to disable dynamicbase/aslr
by Tres Finocchiaro (＠tresf) 22 Aug '25

22 Aug '25

Commit 518e394794160818ffe6826c874ff2f550c95bbb introduced new and important default behavior for PE binaries built using `winegcc`/`wineg++`/`winebuild`. * `/DYNAMICBASE` - Generates an executable image that can be randomly rebased at load time by using the address space layout randomization (ASLR) feature of Windows that was first available in Windows Vista. * `/HIGHENTROPYVA` - Randomized 64-bit virtual addresses make it more difficult for an attacker to guess the location of a particular memory region. ... however as identified in https://bugs.winehq.org/show_bug.cgi?id=58480, this new default behavior can severely impact applications that interact with binaries created for Windows XP and older. This is quite common for legacy audio plugins, such as VST2(TM) plugins. This MR keeps the new default "dynamicbase" and "highentropyva" flags by default, but mirrors the mingw/msys2 `--disable-dynamicbase` flag as explained here: https://www.msys2.org/news/#2021-01-31-aslr-enabled-by-default. MSVC also provides a similarly named flag [here](https://learn.microsoft.com/en-us/cpp/build/reference/dynamicbase). Downstream, the LMMS project has successfully deployed the mingw flag and the MSVC flag for our Windows builds. Our Linux builds use a custom wine-bridge and would benefit from the same. We've currently tested this MR downstream against a snapshot of master branch to passing results. Downstream PRs: * Linux: https://github.com/LMMS/lmms/pull/7987 * Windows: https://github.com/LMMS/lmms/pull/7976 -- v6: Simplify https://gitlab.winehq.org/wine/wine/-/merge_requests/8786

2 7

[PATCH 0/1] MR8820: winewayland: Mark only windows with per-pixel alpha as layered.
by Alexandros Frantzis (＠afrantzis) 22 Aug '25

22 Aug '25

This avoids using buffers with an alpha channel for windows that use SetLayeredWindowAttributes() and don't really utilize per-pixel alpha. Fixes: 6f8f5fe7bf989ba1429bc42114091e8416ad1a7c Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=58504 -- https://gitlab.winehq.org/wine/wine/-/merge_requests/8820

2 1

[PATCH 0/3] MR8812: winegstreamer: Support 2D sample buffer.
by Conor McCarthy (＠cmccarthy) 22 Aug '25

22 Aug '25

Performance issues can occur when a video output sample has a 2D buffer, because winegstreamer currently outputs only to a linear buffer, which must then be copied into the 2D buffer. Worse, a linear lock of the 2D buffer requires the current contents to be copied to a linear buffer, even when we intend to overwrite it, because MF linear buffers do not support write-only locking. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/8812

3 9

Re: [PATCH v15 0/1] MR8778: sane.ds: Adding a window for loading and saving the scanner configuration
by Ivan Lyugaev (＠valy) 22 Aug '25

22 Aug '25

On Fri Aug 22 11:05:37 2025 +0000, Alexandre Julliard wrote: > The registry can be edited by ordinary users as well. I understand, but would it be more convenient for them than opening a regular file? -- https://gitlab.winehq.org/wine/wine/-/merge_requests/8778#note_113606

1 0

Re: [PATCH v3 0/7] MR8776: More runtimeclass type checks - approved
by Huw Davies (＠huw) 22 Aug '25

22 Aug '25

This merge request was approved by Huw Davies. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/8776

1 0

[PATCH v3 0/3] MR8769: winebus: Miscellaneous changes relating to device identification.
by Connor McAdams (＠cmcadams) 22 Aug '25

22 Aug '25

These patches are prerequisites for getting DualShock 4 controllers to work via USB in Tekken 8. -- v3: winebus: Override device instance enumerator string if bus type is known. winebus: Generate unique container IDs when adding devices. winebus: Generate unique serial numbers when adding devices. https://gitlab.winehq.org/wine/wine/-/merge_requests/8769

3 4

[PATCH v5 0/3] MR8808: winealsa, winecoremidi: Fixed MIDI reset Control Change
by Keigo Okamoto (＠KeigoOkamoto) 22 Aug '25

22 Aug '25

This pull request fixes Wine's MIDI synthesizer reset process to be the same as Windows'. When playing Touhou Project games in MIDI BGM mode, the music playback becomes buggy when the BGM changes. The video below is an example of an anomaly that occurs when playing The Fantastic Tales from Tono after playing Crystallized Silver in Touhou 7. https://youtu.be/O69sndJ45Ag Here's a correct example of The Fantastic Tales from Tono playback: https://youtu.be/XlFAQEbbNDg Piano sound is clearly missing on Wine. This issue occurs due to an Wine's incorrect reset process for MIDI synthesizer. When I ran FluidSynth on Windows and checked the log, I found that CC123 and CC121 were executed for each MIDI channel when switching songs. CC123 means All Notes Off, CC121 means Reset All Controllers. -- v5: wineoss: Send All Notes Off and Reset Controllers. https://gitlab.winehq.org/wine/wine/-/merge_requests/8808

3 5

Re: [PATCH v15 0/1] MR8778: sane.ds: Adding a window for loading and saving the scanner configuration
by Alexandre Julliard (＠julliard) 22 Aug '25

22 Aug '25

On Fri Aug 22 10:41:14 2025 +0000, Ivan Lyugaev wrote: > Saving settings in a configuration file allows ordinary users to change > them directly in the file itself. Use the same configuration on > different devices. In my opinion, saving the settings in the registry > complicates this decision from the point of view of the average user. > For example, in Windows, for the canon 3010 scanner, the driver saved > the settings in the configuration file along the path > **%AppData%\Roaming\Canon\G3010 Series ** > Taking into account the above, do I need to change the location where > the settings are saved, or should I stick with this solution? The registry can be edited by ordinary users as well. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/8778#note_113600

1 0

Re: [PATCH v15 0/1] MR8778: sane.ds: Adding a window for loading and saving the scanner configuration
by Ivan Lyugaev (＠valy) 22 Aug '25

22 Aug '25

On Thu Aug 21 20:44:13 2025 +0000, Esme Povirk wrote: > Alternative configurations could be stored in named keys in the registry > though. This might be an easier UI, since you could select them with a > combo box. Saving settings in a configuration file allows ordinary users to change them directly in the file itself. Use the same configuration on different devices. In my opinion, saving the settings in the registry complicates this decision from the point of view of the average user. For example, in Windows, for the canon 3010 scanner, the driver saved the settings in the configuration file along the path **%AppData%\Roaming\Canon\G3010 Series ** Taking into account the above, do I need to change the location where the settings are saved, or should I stick with this solution? -- https://gitlab.winehq.org/wine/wine/-/merge_requests/8778#note_113599

1 0

2025

2024

2023

2022

wine-gitlab