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

[Bug 57662] New: Cashbooks Complete does not render correctly
by WineHQ Bugzilla Feb. 25, 2026

Feb. 25, 2026

https://bugs.winehq.org/show_bug.cgi?id=57662 Bug ID: 57662 Summary: Cashbooks Complete does not render correctly Product: Wine-staging Version: 10.0-rc5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winehq.tabloid372(a)passmail.net CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- The binary is free to download here: https://www.acclaimsoftware.com.au/download/ with no significant depends (access runtime is all). The main window renders using `DISPLAY=:0 wine ..` once a `XWayland&` instance is running otherwise using the native wayland drv backend to `wine-10.0-rc5 (Staging)` results in multiple windows being created that do not show anything. Overall this is a extremely simple program so it is unclear why it doesn't run, I couldn't see anything obvious in the logs. Only a excessive number of `vkd3d:0150:fixme:fold_cast Cast from uint to int2.` prints. -- 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 38

[Bug 15346] New: Winamp disappears when you move it's location
by wine-bugs＠winehq.org Feb. 24, 2026

Feb. 24, 2026

http://bugs.winehq.org/show_bug.cgi?id=15346 Summary: Winamp disappears when you move it's location Product: Wine Version: 1.1.5 Platform: All OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: homerhomer(a)gmail.com Created an attachment (id=16178) --> (http://bugs.winehq.org/attachment.cgi?id=16178) DwmSetWindowAttribute error Sort of a silly bug, basically once winamp is up and running, if you click on the title bar and move it around winamp disappears. To make sure that the bug happens make sure to swirl it around a couple of times. ( A Swirly if you will ) Attached I also noticed this when running winamp manually at startup. This may be related. but then I move winamp and it disappears I don't get any more error messages. So I'm not sure. I appreciate the good work Thank you I'm running Ubuntu 8.04, Wine 1.1.5, AMD64 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

3 48

[Bug 49583] New: Assassin's Creed Odyssey displays black bars on top and bottom.
by WineHQ Bugzilla Feb. 24, 2026

Feb. 24, 2026

https://bugs.winehq.org/show_bug.cgi?id=49583 Bug ID: 49583 Summary: Assassin's Creed Odyssey displays black bars on top and bottom. Product: Wine Version: 5.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: GloriousEggroll(a)gmail.com Distribution: --- Created attachment 67739 --> https://bugs.winehq.org/attachment.cgi?id=67739 AC Odyssey black bar fix It's been a long known issue that AC: Odyssey renders with black bars on the top and bottom of the screen (see screenshot 1). Derek Lesho came up with a stub patch that both fixed this -and- allowed STEEP to run (it would not display previously). That patch can be found here: https://github.com/GloriousEggroll/proton-ge-custom/blob/5.12-GE-1/patches/… Recently, the relevant function QueryDisplayConfig was implemented, however it did not contain some of the changes Derek's patch adds. This allowed steep to work, however AC: Odyssey still retained the black bar issue. I modified Derek's patch by adding the relevant parts to QueryDisplayConfig, and removing the relevant flag checks (Derek's patch did this previously), and this allowed AC: Odyssey to render properly without the black bars. (see screenshot 2). The patch is hacky but may provide more information towards fixing this properly. -- 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 9

[Bug 58325] New: wined3d swapchain use-after-free
by WineHQ Bugzilla Feb. 24, 2026

Feb. 24, 2026

http://bugs.winehq.org/show_bug.cgi?id=58325 Bug ID: 58325 Summary: wined3d swapchain use-after-free Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: yshuiv7(a)gmail.com Distribution: --- Releasing the swapchain brings us to wined3d_swapchain_cleanup, which destroys the front/back buffer textures. Texture destruction is async, happening on the device's command stream. This means these textures can be destroyed way after the swapchain itself. But we did set `texture->swapchain` to `NULL` before queuing their destruction, so that bit is fine. The problem is in texture_resource_unload. Here we try to acquire the context, which goes adapter_gl_acquire_context -> wined3d_context_gl_acquire -> wined3d_context_gl_activate -> wined3d_context_gl_update_window. And here we try to access `context_gl->c.swapchain->win_handle`, which unfortunately points to the swapchain that was just freed. I am unsure what's the fix for this. Do we hold a refcount of the swapchain in the context? Do we clear `context->swapchain` when a swapchain is being freed? Should we release the front/back buffer synchronously? Or something 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.

2 3

[Bug 45882] New: (Overwatch, several source games) Raw Mouse input not working
by wine-bugs＠winehq.org Feb. 24, 2026

Feb. 24, 2026

https://bugs.winehq.org/show_bug.cgi?id=45882 Bug ID: 45882 Summary: (Overwatch, several source games) Raw Mouse input not working Product: Wine Version: 3.16 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: florian98.rg(a)gmail.com Distribution: --- Playing Overwatch I've noticed that the game still uses mouse pointer speed even though on Windows it uses Raw Mouse input exclusively. I've tried this on any branch of Wine (staging, esync, whatsoever) and the problem still persists. This also happens in Valve games where you can enable Raw Mouse Input, e.g. Team Fortress 2 etc. This does not happen with the native ports of said games that use SDL to get mouse input. I already disabled any mouse acceleration in GNOME whatsoever (using the "Flat" Profile), however the problem persists. Is it possible to rewrite Wine to get Mouse input via SDL2 instead? That would help pave way for Wayland etc. Thanks -- 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.

3 34

[Bug 46534] New: Just Cause 4 crashes on startup
by wine-bugs＠winehq.org Feb. 24, 2026

Feb. 24, 2026

https://bugs.winehq.org/show_bug.cgi?id=46534 Bug ID: 46534 Summary: Just Cause 4 crashes on startup Product: Wine Version: 4.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ramy0zahran(a)gmail.com Distribution: --- Created attachment 63387 --> https://bugs.winehq.org/attachment.cgi?id=63387 JC4backtrace Unhandled exception: page fault on read access to 0xffffffffffffffff in 64-bit code (0x0000000141926167). -- 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.

3 19

[Bug 53574] New: MSYS2 "pacman -Sy" fails key lookup
by WineHQ Bugzilla Feb. 23, 2026

Feb. 23, 2026

https://bugs.winehq.org/show_bug.cgi?id=53574 Bug ID: 53574 Summary: MSYS2 "pacman -Sy" fails key lookup Product: Wine Version: 7.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: joel(a)airwebreathe.org.uk Distribution: --- Created attachment 72951 --> https://bugs.winehq.org/attachment.cgi?id=72951 Log of console interaction With a fresh Msys2 installation, pacman fails to run, because it keeps producing "key lookup failed" errors. The user is prompted to with the following message: error: mingw32: key "5F944B027F7FE2091985AA2EFA11531AA0AA7F57" is unknown :: Import PGP key 5F944B027F7FE2091985AA2EFA11531AA0AA7F57? [Y/n] Y However, if the user selects "yes", pacman simply asks the same question again after a short delay, in an infinite loop. -- 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 6

[Bug 57484] New: VKB Joystick not detected in Wine 9.22 but works in 9.21
by WineHQ Bugzilla Feb. 23, 2026

Feb. 23, 2026

https://bugs.winehq.org/show_bug.cgi?id=57484 Bug ID: 57484 Summary: VKB Joystick not detected in Wine 9.22 but works in 9.21 Product: Wine Version: 9.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: joseph+winehq(a)xaosnet.net Distribution: --- I am using Wine-Staging from the WineHQ Repos on Ubuntu 24.04, and with Staging 9.22, my VKB Gunfighter Left is not detected if hidraw is enabled, but is detected with Staging 9.21, or if I check the box to disable hidraw. I reproduced this with a fresh wine prefix as well as an updated one. I've seen reports that this is also impacting some VKB Gladiator users as well on the Star Citizen Linux Users Group discord. -- 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 14

[Bug 31899] New: No keyboard input in La-Mulana remake
by wine-bugs＠winehq.org Feb. 23, 2026

Feb. 23, 2026

http://bugs.winehq.org/show_bug.cgi?id=31899 Bug #: 31899 Summary: No keyboard input in La-Mulana remake Product: Wine Version: 1.5.14 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: twwinwood(a)gmail.com Classification: Unclassified Created attachment 41993 --> http://bugs.winehq.org/attachment.cgi?id=41993 Output of "env WINEDEBUG=-all,+keyboard,+key,+dinput,+message wine LaMulanaWin.exe" Per the AppDB entry for version 1.1.1.1, the game works as far as the menu screen but cannot be played due to the lack of response to keyboard input. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

3 26

[Bug 35907] New: Caps Lock state gets confused with multiple processes/threads
by wine-bugs＠winehq.org Feb. 23, 2026

Feb. 23, 2026

http://bugs.winehq.org/show_bug.cgi?id=35907 Bug ID: 35907 Summary: Caps Lock state gets confused with multiple processes/threads Product: Wine Version: 1.7.15 Hardware: x86 OS: Mac OS X Status: NEW Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: ken(a)codeweavers.com Open two instances of Notepad in the same prefix: wine notepad & wine notepad & With one Notepad window active, turn Caps Lock on. Switch to the other Notepad window. Type some text. Notice it's not capitalized, although it should be. Turn Caps Lock off. Type some text. Notice that it is capitalized, although it shouldn't be. Switch back to the first Notepad window. Type some text. Notice that it is capitalized, although it shouldn't be. -- 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.

3 15