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

[Bug 58276] New: pulse.c should silence_buffer after calloc
by WineHQ Bugzilla 22 Jun '25

22 Jun '25

http://bugs.winehq.org/show_bug.cgi?id=58276 Bug ID: 58276 Summary: pulse.c should silence_buffer after calloc Product: Wine Version: 8.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winepulse.drv Assignee: wine-bugs(a)winehq.org Reporter: jxvhulzowyrobfwwze(a)nbmbb.com Distribution: --- When pulse_write is “prebuffering … frames of silence,” it uses calloc to zero out a buffer, then immediately calls pa_stream_write. This isn’t correct for an unsigned 8-bit (u8) stream, since the neutral value should be 128 instead of zero. This causes noticeable clicking whenever the sender stops or resumes playback. (For example, old games that play occasional WAV files as sound effects.) The issue can be reproduced using Sound Recorder from Win3.1 and an 8-bit mono WAV file. Play the same sound over and over until it starts clicking/popping. I’m not sure if this scenario (the end of a WAV file) should even trigger “buffer underrun” logic at all, since it’s an intentional gap. But regardless of the reason for the underrun, there should be a silence_buffer call there. I tested this in Wine 8, but confirmed the logic is the same in the latest version. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 58198] New: Wine missing WH_JOURNALPLAYBACK, required by VB SendKeys
by WineHQ Bugzilla 22 Jun '25

22 Jun '25

http://bugs.winehq.org/show_bug.cgi?id=58198 Bug ID: 58198 Summary: Wine missing WH_JOURNALPLAYBACK, required by VB SendKeys Product: Wine Version: 8.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user16 Assignee: wine-bugs(a)winehq.org Reporter: jxvhulzowyrobfwwze(a)nbmbb.com Distribution: --- Wine doesn’t implement WH_JOURNALPLAYBACK, which is required by the Visual Basic SendKeys function. This makes the game “Mordor: The Depths of Dejenol” unplayable after entering the dungeon. I’ve confirmed with 32-bit Wine 8 and 16-bit VB3, but the logic seems unchanged in more recent Wine (and VB) versions. Microsoft eventually released a VB6 runtime that reimplemented SendKeys using SendInput instead of WH_JOURNALPLAYBACK, but that only fixes VB6 binaries. https://archives.miloush.net/michkap/archive/2007/09/10/4850360.html https://web.archive.org/web/20130615064311/http://blogs.msdn.com/b/michkap/… The story gets worse for programs that invoke DoEvents after SendKeys. Since DoEvents “first clears all pending keystrokes from the SendKeys function,” it enters an endless loop waiting for PeekMessage to return the expected WH_JOURNALPLAYBACK messages. CPU usage goes to 100%, and it’s easy to run out of stack space if DoEvents is invoked repeatedly. https://nolongerset.com/how-doevents-works/ Thankfully, running with WINEDEBUG=warn emits a clear message, “SetWindowsHookEx16 hook type 1 broken in Win16” pointing us to https://gitlab.winehq.org/wine/wine/-/blob/master/dlls/user.exe16/hook.c This game is particularly creative, using SendKeys as some sort of input filter. Many keyboard and mouse inputs are apparently translated to SendKeys calls. I don’t fully understand the logic, except that the game is unplayable without it. I can’t say whether it’s worth fixing this or not. At the very least, it’s helpful to know why this game doesn’t work, without having to keep trying each new Wine release. The free demo of “Mordor: The Depths of Dejenol” can be downloaded from https://www.decklinsdemise.com/mordor.htm -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 56695] New: Unreal Engine game checks for a specific VC runtime regkey
by WineHQ Bugzilla 22 Jun '25

22 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=56695 Bug ID: 56695 Summary: Unreal Engine game checks for a specific VC runtime regkey Product: Wine Version: 9.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: tools Assignee: wine-bugs(a)winehq.org Reporter: galtgendo(a)o2.pl Distribution: --- Created attachment 76479 --> https://bugs.winehq.org/attachment.cgi?id=76479 registry key being checked for An Unreal Engine game checks for a VC++ runtime libs by checking for a specific registry key created during install of that runtime upon startup. Consider adding that key. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 58400] New: Signature invalid
by WineHQ Bugzilla 21 Jun '25

21 Jun '25

http://bugs.winehq.org/show_bug.cgi?id=58400 Bug ID: 58400 Summary: Signature invalid Product: WineHQ.org Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: tmcconnell168(a)gmail.com Distribution: --- I get this for Debian when I try to run the "APT UPDATE" command: Warning: https://download.opensuse.org/repositories/home:/strycore/Debian_12/./InRel…: Policy will reject signature within a year, see --audit for details Audit: https://download.opensuse.org/repositories/home:/strycore/Debian_12/./InRel…: Sub-process /usr/bin/sqv returned an error code (1), error message is: Error: Policy rejected packet type Caused by: Signature Packet v3 is not considered secure since 2026-02-01T00:00:00Z Debian 13 (Trixie or testing) command = 'apt update --audit' to get full output. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 54567] New: comdlg32: Find/Replace: Flags became invalid after EN_KILLFOCUS.
by WineHQ Bugzilla 21 Jun '25

21 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=54567 Bug ID: 54567 Summary: comdlg32: Find/Replace: Flags became invalid after EN_KILLFOCUS. Product: Wine Version: 8.0-rc5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comdlg32 Assignee: wine-bugs(a)winehq.org Reporter: katayama.hirofumi.mz(a)gmail.com Distribution: --- Created attachment 74109 --> https://bugs.winehq.org/attachment.cgi?id=74109 the patch to fix this bug The flags value became invalid after EN_KILLFOCUS. It caused a bug that FR_DOWN is cleared when the user set focus to edt1 and close the find/replace dialog. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 58254] New: Clip Studio Paint 4 shuts down immediately when using compatibility mode for Windows 10 or 11.
by WineHQ Bugzilla 21 Jun '25

21 Jun '25

http://bugs.winehq.org/show_bug.cgi?id=58254 Bug ID: 58254 Summary: Clip Studio Paint 4 shuts down immediately when using compatibility mode for Windows 10 or 11. Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mar.asdoria(a)gmail.com Distribution: --- Created attachment 78597 --> http://bugs.winehq.org/attachment.cgi?id=78597 backtrace file In Operating System: Kubuntu 25.04 Kernel Version: 6.14.0-15-generic (64-bit) Using Clip Studio Paint 4: https://www.clipstudio.net/en/dl/ (Free trial download) The program manages to launch, displays a black screen and then crashes with the error code "winedbg attached to pid 0408" on the console as the only prompt. The program works well under compatibility mode for Windows 8.1, including all app features (excluding the Asset store), menus, filters and 3D tools. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 58064] New: Unreal 2 hangs with a black screen when switching to 1440X900 resolution
by WineHQ Bugzilla 21 Jun '25

21 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=58064 Bug ID: 58064 Summary: Unreal 2 hangs with a black screen when switching to 1440X900 resolution Product: Wine Version: 10.5 Hardware: x86-64 URL: https://community.pcgamingwiki.com/files/file/265-unre al-ii-the-awakening-single-player-demo/?do=download&cs rfKey=dbe29bc7b5c23e8ee79b15e743414902 OS: Linux Status: NEW Keywords: download, regression Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: rbernon(a)codeweavers.com Regression SHA1: ab2b7ebfcd78f6a74068a5a79d90ee6fcf235a12 Distribution: ArchLinux Unreal 2 starts in 1024X768 resolution and switching between 640X480, 800X600 or 1024X768 modes works properly, however when I try to switch to 1440X900 in the video options menu, the game hangs with a black screen and Unreal2.exe is consuming 100% CPU. 1440X900 is the max. resolution that my monitor supports. Used to work before commit ab2b7ebfcd78f6a74068a5a79d90ee6fcf235a12 winex11: Use win32u generic wgl(Get|Set)PixelFormat(WINE). The same commit causes similar issue (black screen and game .exe pegging the CPU) when trying to start the following games: Art of Murder: Cards of Destiny https://store.steampowered.com/app/836770/Art_of_Murder__Cards_of_Destiny/ Art of Murder - Hunt for the Puppeteer https://store.steampowered.com/app/832540/Art_of_Murder__Hunt_for_the_Puppe… Chronicles of Mystery: The Scorpio Ritual https://store.steampowered.com/app/34800/Chronicles_of_Mystery_The_Scorpio_… OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 570.133.07 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 58401] New: system.fill_battery_state: support battery drivers that expose energy_* instead of charge_* attributes of power_supply_class
by WineHQ Bugzilla 20 Jun '25

20 Jun '25

http://bugs.winehq.org/show_bug.cgi?id=58401 Bug ID: 58401 Summary: system.fill_battery_state: support battery drivers that expose energy_* instead of charge_* attributes of power_supply_class Product: Wine Version: 10.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: rtdiasmendes(a)gmail.com Distribution: --- File: system.c Method: fill_battery_state( SYSTEM_BATTERY_STATE *bs ) Current implementation: - Assumes battery driver exposes: "charge_now", "charge_full", "voltage_now" and "current_now". - Populates SYSTEM_BATTERY_STATE with those attributes after converting to expected units Issue: - Some battery drivers expose different ABI-compliant attributes - In systems with those drivers, Wine is incapable of emulating windows behaviour Enhacement proposal: - Add support for drivers that expose different attributes Further reading: - https://docs.kernel.org/power/power_supply_class.html - https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-devices-power - https://github.com/torvalds/linux/blob/master/include/linux/power_supply.h - https://github.com/torvalds/linux/blob/master/drivers/power/supply/power_su… Note: Attribute "scope", while implemented in the kernel, is undocumented in the power_supply_class docs. Will later check if the rest of the documentation is up to date and raise the appropriate issue upstream. Until then, do not assume it correctly reflects the kernel implementation. Out-of-scope commentary: While Wine's behavior of querying /sys/class/power_supply/ on every NtPowerInformation() call correctly emulates the Windows API semantics, it has unintended performance implications on Linux. This is due to the fact that retrieving battery information from sysfs involves real filesystem I/O, including frequent failed lookups on systems that expose energy_* instead of charge_* attributes. Therefore, applications may call NtPowerInformation() without prioritizing caching or proper fallback logic as they expect the operation to have a lower-cost then it does on Linux - causing significant and unnecessary performance degradation. This may merit its own enhacement proposal if it results in noticeable performance degradation. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 55707] New: Wine seems to not be sending TVN_ITEMCHANGING and TVN_ITEMCHANGED notifications when a panel uses TVM_SELECTITEM to select a single item on a treeview
by WineHQ Bugzilla 20 Jun '25

20 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=55707 Bug ID: 55707 Summary: Wine seems to not be sending TVN_ITEMCHANGING and TVN_ITEMCHANGED notifications when a panel uses TVM_SELECTITEM to select a single item on a treeview Product: Wine Version: 8.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cadbusca(a)gmail.com Distribution: --- There is a very important component for the music player Foobar2000 (V2.0 32bits) called 'Album list panel' that was working fine until its version 1.0. Since version 2.0, a new feature was implemented which is: "The ability to select multiple items using Ctrl and Shift keys was added. This includes Shift-clicking, Ctrl-clicking, and holding Shift when pressing navigation keys." [on a treeview] and selecting a single or multiple items from the component treeview stopped working. I opened a PR on the component github repository at: https://github.com/reupen/album_list_panel/issues/179 and the developer pointed out that the issue may be caused by some issue with Wine not be sending TVN_ITEMCHANGING and TVN_ITEMCHANGED notifications when a panel uses TVM_SELECTITEM to select a single item of a treeview How to reproduce: 1) Install foobar2000 V2.0 32bits from https://www.foobar2000.org/download 2) Install the latest version of the following Foobar2000 components: https://yuo.be/columns-ui and https://yuo.be/album-list-panel 3) Insert a album-list-panel to foobar 4) Selecting one or more items on the treeview have no effect 5) More details including a small video of the issue can be seen here: https://github.com/reupen/album_list_panel/issues/179 I'm willing to test when a fix is available. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 58397] New: Missing power_supply class attributes for NtPowerInformation blocks threads and causes fps stutter
by WineHQ Bugzilla 20 Jun '25

20 Jun '25

http://bugs.winehq.org/show_bug.cgi?id=58397 Bug ID: 58397 Summary: Missing power_supply class attributes for NtPowerInformation blocks threads and causes fps stutter Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: rtdiasmendes(a)gmail.com Distribution: Mint Created attachment 78805 --> http://bugs.winehq.org/attachment.cgi?id=78805 logs mentioned in the bug Description Affected Application: - Tainted Grail: Fall of Avalon Observed Symptoms: - Frametime spikes from ~5ms to ~100ms occurring at ~1Hz intervals. - GPU frame dispatch (via DXVK) is delayed due to thread blocking in Wine’s battery status polling logic. Performance Analysis (see attached logs): - strace shows constant, repeated attempts to read nonexistent files in /sys/class/power_supply/BAT1/ - perf stat reveals ~8,270 openat() syscalls in 10 second window (on game title screen). - perf record/report shows significant thread time consumed inside NtPowerInformation-related logic in ntdll. Root Cause: - In dlls/ntdll/unix/system.c, the function fill_battery_state() (Linux version) hardcodes the use of attributes: "charge_now" "charge_full" and "current_now". - These attributes are not universally present in /sys/class/power_supply/. On some systems, particularly those using energy-based reporting (µWh), the ABI-compliant alternatives are: "energy_now", "energy_full" and "power_now". - Since Wine looks only for the "charge_*" files and fails to return expected information, the game loops the query constantly which results in openat() being used in a tight polling loop - blocking threads and causing intermittent CPU stalls that propagate to the GPU rendering pipeline. Solution 1: - Verify what attributes are present in the power_supply class. - Implement logic with supplied attributes. Solution 2: - Attempt to read the already-implemented files. - Fallback to "energy_*" if those are not present. I gather solution 1 has a more consistent impact across different systems, while solution 2 is more lightweight on systems with "charge_*" and heavier on others. Further reading: - https://docs.kernel.org/power/power_supply_class.html - https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-devices-power - https://github.com/torvalds/linux/blob/master/include/linux/power_supply.h - https://github.com/torvalds/linux/blob/master/drivers/power/supply/power_su… Note: Attribute "scope", while implemented in the kernel, is undocumented in the power_supply_class docs. Will later check if the rest of the documentation is up to date and raise the appropriate issue upstream. Until then, do not assume it correctly reflects the kernel implementation. Disclaimer: This issue was identified and reproduced using Proton-GE, Proton (Steam Runtime), Soda and Flatpak's build. I am reporting it here for visibility and discussion since it appears to originate from WineHQ’s upstream implementation of NtPowerInformation. Out-of-scope commentary: While Wine's behavior of querying /sys/class/power_supply/ on every NtPowerInformation() call correctly emulates the Windows API semantics, it has unintended performance implications on Linux. This is due to the fact that retrieving battery information from sysfs involves real filesystem I/O, including frequent failed lookups on systems that expose energy_* instead of charge_* attributes. Therefore, applications may call NtPowerInformation() without prioritizing caching or proper fallback logic as they expect the operation to have a lower-cost then it does on Linux - causing significant and unnecessary performance degradation. Will raise this for an enchancement in the proper channels. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 5