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

[Bug 56697] New: _kbhit ignores the last event in the queue
by WineHQ Bugzilla 15 Aug '25

15 Aug '25

https://bugs.winehq.org/show_bug.cgi?id=56697 Bug ID: 56697 Summary: _kbhit ignores the last event in the queue Product: Wine Version: 9.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)winehq.org Reporter: qsniyg(a)protonmail.com Distribution: --- Created attachment 76482 --> https://bugs.winehq.org/attachment.cgi?id=76482 kbhit_test.c Discovered this bug while writing an implementation for timeout.exe. Run the attached kbhit_test program under wineconsole to replicate the error. -- 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 10

[Bug 57115] New: CEF sample application "Draggable" test fails
by WineHQ Bugzilla 15 Aug '25

15 Aug '25

https://bugs.winehq.org/show_bug.cgi?id=57115 Bug ID: 57115 Summary: CEF sample application "Draggable" test fails Product: Wine Version: 9.16 Hardware: x86-64 URL: https://cef-builds.spotifycdn.com/cef_binary_127.3.5%2 Bg114ea2a%2Bchromium-127.0.6533.120_windows64_client.t ar.bz2 OS: Linux Status: NEW Keywords: download, source Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: imwellcushtymelike(a)gmail.com Distribution: Ubuntu Created attachment 77007 --> https://bugs.winehq.org/attachment.cgi?id=77007 Wine 9.16 console output The Draggable test in the Chromium Embedded Framework sample application allows the application itself to be moved when dragging inside a supplied red box. Under Windows 10 this works as expected. Under Wine 9.16 this has no effect. $ wine cefclient.exe --url=https://tests/draggable Nothing new is printed in the console while testing this. -- 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 2

[Bug 57783] New: Approach will not run in a virgin 10.0 wineprefix
by WineHQ Bugzilla 15 Aug '25

15 Aug '25

https://bugs.winehq.org/show_bug.cgi?id=57783 Bug ID: 57783 Summary: Approach will not run in a virgin 10.0 wineprefix 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: ToddAndMargo(a)zoho.com Distribution: --- Created attachment 77980 --> https://bugs.winehq.org/attachment.cgi?id=77980 debugg message on crash What a disaster! Please correct. I need my accounting system back. SmartSuite-N99.8.0208.0800 Fedora 41 wine-stable-10.0.0-1.1.x86_64 winehq-stable-10.0.0-1.1.x86_64 Lotus Approach will not run in a fresh WINEPREFIX under WineHQ Stable 10.0, unless you have leftover stuff from a prior wine install. But that would not be a fresh WINEPREFIX. Both Approach and WordPro were selected on a customer install and a fulkl install too after wiping the .wine directory and starting fresh The following error occurs at the end of installation from the smart suite ISO. regedit: Unable to open the registry key 'HKEY_CURRENT_USER\Software\Lotus\SmartSuite'. and regedit: Unable to open the registry key 'HKEY_CURRENT_USER\Software\Lotus\ScreenCam'. Only Approach and WordPro were selected on a customer install. When starting Approach: $ cd /home/todd/.wine/drive_c/lotus/approach $ wine ./approach.exe The following pop occurs "Lotus Approach: Couldn't load Lotus Dialog DynaLink" Pressing okay, opens a Program Error box and presents this error in the command line: wine: Unhandled exception 0xe06d7363 in thread 24 at address 7B5F7448 (thread 0024), starting debugger... I will attach the full debug message message. I have one for one checked a qemu-kvm Windows 10 install of Approach against my wine registry and they are identical Many thanks -T -- 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 8

[Bug 52844] New: Call of Duty: Black Ops II stucks with a black screen after intro
by WineHQ Bugzilla 15 Aug '25

15 Aug '25

https://bugs.winehq.org/show_bug.cgi?id=52844 Bug ID: 52844 Summary: Call of Duty: Black Ops II stucks with a black screen after intro Product: Wine Version: 7.6 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Created attachment 72240 --> https://bugs.winehq.org/attachment.cgi?id=72240 log wine-7.6-211-ge254680ed15 -- 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 10

[Bug 56246] New: Regarding the color depth of BMP in the SavePicture method: the value is unstable.
by WineHQ Bugzilla 15 Aug '25

15 Aug '25

https://bugs.winehq.org/show_bug.cgi?id=56246 Bug ID: 56246 Summary: Regarding the color depth of BMP in the SavePicture method: the value is unstable. Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: taka(a)bahamut7.com Distribution: --- Created attachment 75953 --> https://bugs.winehq.org/attachment.cgi?id=75953 Difference in color depth between Wine and Windows Thank you for the great software. In Windows 10/11, the SavePicture method saves in "24-bit color" even if the display's color setting is "32-bit color". In Wine, if the display's color setting is "32bit color", the picture is saved in "32bit color" and the Windows software throws an error. In Debian, for some reason, it is saved with the value "0". Due to this difference, some software may not work. -- 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 11

[Bug 57116] New: Crash during codecs test on CEF sample application
by WineHQ Bugzilla 15 Aug '25

15 Aug '25

https://bugs.winehq.org/show_bug.cgi?id=57116 Bug ID: 57116 Summary: Crash during codecs test on CEF sample application Product: Wine Version: 9.16 Hardware: x86-64 URL: https://cef-builds.spotifycdn.com/cef_binary_127.3.5%2 Bg114ea2a%2Bchromium-127.0.6533.120_windows64_client.t ar.bz2 OS: Linux Status: NEW Keywords: download, source Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: imwellcushtymelike(a)gmail.com Distribution: Ubuntu Created attachment 77008 --> https://bugs.winehq.org/attachment.cgi?id=77008 Wine 9.16 console output Running the Codecs test on the Chromium Embedded Framework sample application causes a crash, but winedbg is unable to provide any further details (also the OK button from winedbg doesn't work). The application itself does not close and continues to run. Run with: wine cefclient.exe --url=https://shaka-player-demo.appspot.com/support.html -- 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 6

[Bug 58459] New: Doom 3: BFG Edition fails to start
by WineHQ Bugzilla 15 Aug '25

15 Aug '25

http://bugs.winehq.org/show_bug.cgi?id=58459 Bug ID: 58459 Summary: Doom 3: BFG Edition fails to start Product: Wine Version: 10.11 Hardware: x86-64 URL: https://store.steampowered.com/app/208200/DOOM_3/ OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: rbernon(a)codeweavers.com Regression SHA1: a897aad823f5ea76949a0171f34984f4ebf1ced1 Distribution: --- Created attachment 78913 --> http://bugs.winehq.org/attachment.cgi?id=78913 terminal output Doom 3: BFG Edition crashes immediately on start. Doesn't affect the original Doom 3 version. Present since commit a897aad823f5ea76949a0171f34984f4ebf1ced1 win32u: Keep track of the most recent window GL drawable. Starts properly with the previous commit. OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 575.64.03 X.Org X Server 1.21.1.18 -- 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 44066] New: mintty/msys2 doesn't work since wine 2.5.0 (named pipes)
by wine-bugs＠winehq.org 15 Aug '25

15 Aug '25

https://bugs.winehq.org/show_bug.cgi?id=44066 Bug ID: 44066 Summary: mintty/msys2 doesn't work since wine 2.5.0 (named pipes) Product: Wine-staging Version: 2.22 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: andrey.gursky(a)e-mail.ua CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Hi! According to [1], I'm opening a new issue. msys2 (based on Cygwin up to 2.5.x) does work on wine-staging. Since 2.5.0 mintty starts but has no visible output. You can work only blindly (ctrl+d closes the session). Actually I've expected that since wine 2.5 msys2 will work not only on wine-staging but also on wine. Unfortunately the opposite has happened. Regards, Andrey [1] https://bugs.winehq.org/show_bug.cgi?id=17195#c189 -- 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.

2 8

[Bug 58477] New: regreession - some VST plugins fails
by WineHQ Bugzilla 15 Aug '25

15 Aug '25

http://bugs.winehq.org/show_bug.cgi?id=58477 Bug ID: 58477 Summary: regreession - some VST plugins fails Product: Wine Version: 10.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: xj(a)wp.pl Distribution: --- Some VST plugins fails on wine-10.11 e.g. Ignite studio PTEq-X and The Anvil I made bisect and it came out that culprit is: commit a897aad823f5ea76949a0171f34984f4ebf1ced1 (HEAD) Author: Rémi Bernon <rbernon(a)codeweavers.com> Date: Sat May 31 12:33:51 2025 +0200 win32u: Keep track of the most recent window GL drawable. It fails like that: 0118:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style 00007AEA9C2F7190. 0118:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style 00007AEA9C2F7190. 0118:fixme:d2d:d2d_device_context_Flush iface 00007AEA9C2EB480, tag1 0000000000000000, tag2 0000000000000000 stub! 0128:err:seh:call_seh_handlers invalid frame 00000001002FE0F8 (00007AEA9D382000-00007AEA9D480000) 0128:err:seh:NtRaiseException Exception frame is not in stack limits => unable to dispatch exception. -- 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 58425] New: video/x-h264 alignment=au caps causes artifacts and crashes with nal-aligned streams
by WineHQ Bugzilla 15 Aug '25

15 Aug '25

http://bugs.winehq.org/show_bug.cgi?id=58425 Bug ID: 58425 Summary: video/x-h264 alignment=au caps causes artifacts and crashes with nal-aligned streams Product: Wine Version: 10.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winegstreamer Assignee: wine-bugs(a)winehq.org Reporter: mkrsym1(a)gmail.com Distribution: --- Multiple applications try to playback nal-aligned streams, but Wine always sets the alignment caps to au. This causes h264parse to work incorrectly, which in turn leads to various unpleasant effects, depending on the decoder used. Some examples: - libav's avdec_h264 is the most tolerant one, and only displays brief image artifacts when au-alignment is broken. - OpenH264 displays major image and temporal artifacts on au-alignment break, sometimes hangs. - NVIDIA's nvh264dec immediately crashes the entire application on au-alignment break. This issue is completely fixed by not setting the alignment caps at all and letting h264parse do it's job, as done in this commit: https://github.com/ValveSoftware/wine/commit/0304a42 Not sure why it's set in the first place. Maybe that patch can be merged into Wine master, or is there something that I'm missing? -- 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