January 2026 - Wine-Bugs - list.winehq.org

[Bug 59326] 2D surface render glitch in Wizardry 8 (ddraw/wined3d)

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59326 Béla Gyebrószki <gyebro69(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://archive.org/downloa | |d/Wiz8b/Wiz8NetDemoEB.exe Keywords| |download CC| |gyebro69(a)gmail.com --- Comment #1 from Béla Gyebrószki <gyebro69(a)gmail.com> --- A short demo version of the game is available, featuring a predefined (sample) party. This is sufficient to reproduce the graphical glitch appearing on the HP bar. https://archive.org/download/Wiz8b/Wiz8NetDemoEB.exe Wiz8NetDemoEB.exe (143 M) sha256: 4ddfe21561c0856e72fc2b722be9dbc727733696fe3e8563e703b60d85e547fc -- 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.

Jan. 30, 2026

[Bug 59056] Kontakt 8: fails to install: "FALSE"

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59056 bacon-joyous-vibes(a)duck.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bacon-joyous-vibes(a)duck.com --- Comment #1 from bacon-joyous-vibes(a)duck.com --- I can comfirm the bug. -- 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.

Jan. 30, 2026

[Bug 59339] New: Atlantis Sky Patrol: mutiple glitches when starting game

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59339 Bug ID: 59339 Summary: Atlantis Sky Patrol: mutiple glitches when starting game Product: Wine Version: 11.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: 225coburn(a)protonmail.com Distribution: --- Created attachment 80278 --> http://bugs.winehq.org/attachment.cgi?id=80278 warn+all log file As soon as you start a new game in Windowed Mode, the glitches start. The newspaper spins onto the screen way faster than it should. Then on the world map, once it focuses in on the first level dot, the text bounces at a very high speed, much higher than on Windows. Then the more major glitch(es): stalling issues. Clicking play to load in the level, and after clicking off the level name, the shooter takes a long time to fade in, and after every shot, especially shots that hit a wrong color on the spot board in the center, there is a very pronounced lag before you are allowed to shoot again. so much so that game playability is severely compromised. Exiting the game also takes a much longer time than it should, probably the same glitch. Since it's an older game I tried running with Windows version set to XP, the problems still occur. Attached is warn+all winedebug log, if it helps. -- 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.

Jan. 30, 2026

[Bug 35904] USB connection not recognized by Axon MultiClamp Commander 700B.

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=35904 --- Comment #6 from Alois Schlögl <alois.schloegl(a)gmail.com> --- Created attachment 80277 --> http://bugs.winehq.org/attachment.cgi?id=80277 retested MC700B with WINEDEBUG=WINEDEBUG=+usb,+wineusb,+plugplay,+hid,+rawinput,+dinput,+xinput,+input I'm not sure whether this is really a hidusb device (hidviz recognizes the device, but files when trying to access it). Therefore, I retested with extended set of WINEDEBUG flags. -- 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.

Jan. 30, 2026

[Bug 59333] VNyan leaks memory (race in __wine_syscall_dispatcher $rsp switching breaks Unity GC)

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59333 --- Comment #6 from Hoshino Lina <lina(a)lina.yt> --- It was just a suggestion, in case masking signals has too much overhead and full tracking of IP position too complex. I'm not really comfortable enough with the code to attempt a proper solution myself... there's a lot of subtlety in there (e.g. CFI) that I have no idea about. I hope someone else who knows the code better can pick this up. -- 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.

Jan. 30, 2026

[Bug 59333] VNyan leaks memory (race in __wine_syscall_dispatcher $rsp switching breaks Unity GC)

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59333 --- Comment #5 from Zeb Figura <z.figura12(a)gmail.com> --- I don't think a partial solution like that is particularly likely to be accepted. I could be wrong, though. -- 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.

Jan. 30, 2026

[Bug 59338] Menus fail to display after closing child dialog in DAZ Studio 4.24.0.4 (Qt popup recreated but not mapped/shown)

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59338 William Korb <korb(a)qisc.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |korb(a)qisc.com -- 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.

Jan. 30, 2026

[Bug 59338] Menus fail to display after closing child dialog in DAZ Studio 4.24.0.4 (Qt popup recreated but not mapped/shown)

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59338 --- Comment #1 from William Korb <korb(a)qisc.com> --- Happy to help bisect if needed. I can test intermediate dev builds reliably in my clean prefix with the exact repro steps (Window → Workspace → Select Layout → Cancel → Window menu fails to appear). Let me know if you want me to try specific commits or pre-built dev snapshots. -- 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.

Jan. 30, 2026

[Bug 59338] New: Menus fail to display after closing child dialog in DAZ Studio 4.24.0.4 (Qt popup recreated but not mapped/shown)

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59338 Bug ID: 59338 Summary: Menus fail to display after closing child dialog in DAZ Studio 4.24.0.4 (Qt popup recreated but not mapped/shown) Product: Wine Version: 11.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: korb(a)qisc.com Distribution: --- Created attachment 80276 --> http://bugs.winehq.org/attachment.cgi?id=80276 Log as detailed in description I was running WINE 11.0-rc4 prior to this week, and it was working fine. The issue started when I updated to 11.0 (I skipped rc5). Steps to reproduce in clean prefix (wineboot --init, no overrides, no env vars): 1. Install base DAZ Studio 4.24.0.4 (no content needed). 2. Launch DAZ. 3. Window → Workspace → Select Layout... → Cancel 4. Try to open Window menu again → menu does not appear (click has no effect). Log (+err,+warn,+qt,+focus,+menu,+popup) shows: - First menu open: system popup created (e.g., 0x10262/0x10264), all standard items inserted (&Restore, &Move, etc.), NtUserThunkedMenuInfo applied, default set, get_menu_state checks. - Dialog close: NtUserDestroyMenu destroys popup handles. - Second (and third) menu attempt: identical creation cycle (new handle, items inserted again, etc.). - But no MapNotify/Expose/visibility events for the second popup — menu never appears on screen. Setup: - Wine: wine-11.1 (apt install --install-recommends winehq-devel) - OS: Linux Mint 21.3 Cinnamon X11 w/ all latest updates applied - GPU: NVIDIA 590.48.01 driver - App: DAZ Studio 4.24.0.4 base install Tested: - Compositing off - Virtual desktop on/off - Qt env vars (QT_X11_NO_MITSHM=1, QT_AUTO_SCREEN_SCALE_FACTOR=0) - Windows version change (10 -> 7) - Focus mode switch (from sloppy to click and back) - No DLL overrides or custom env vars in clean prefix I then ran my test again with WINEDEBUG='+err,+warn,+qt,+focus,+menu,+popup' to produce the attached log. I interjected comments into the log to indicate where I took the actions described above. My comments are on lines that start with "***". -- 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.

Jan. 30, 2026

[Bug 59333] VNyan leaks memory (race in __wine_syscall_dispatcher $rsp switching breaks Unity GC)

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59333 --- Comment #4 from Hoshino Lina <lina(a)lina.yt> --- Yeah, I was thinking about that yesterday and it's not just SP. For the GC not to break, you need to make sure all registers are either preserved, or saved to the *user* stack, for any frames reported to user code. Otherwise the GC could miss some roots and free something it shouldn't. In practice, I think that means not clobbering any non-volatile registers while you are saving the frame. I think if you do that, and change the context code to something like: if (rip in __wine_syscall_dispatcher && rip during context save/restore sections) Just fake rip to be before/after the call so user does not observe it else if (is_inside_syscall()) Syscall path else Normal context path Then that would probably be reasonably fine? The user could observe volatile registers "magically" changing during the syscall in the corner cases but not much else. -- 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.

Jan. 30, 2026