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

[Bug 44567] New: Deus Ex: Human Revolution doesn't exit, hangs
by wine-bugs＠winehq.org Jan. 18, 2026

Jan. 18, 2026

https://bugs.winehq.org/show_bug.cgi?id=44567 Bug ID: 44567 Summary: Deus Ex: Human Revolution doesn't exit, hangs Product: Wine Version: 3.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: emailofchris(a)gmail.com Distribution: Other Created attachment 60535 --> https://bugs.winehq.org/attachment.cgi?id=60535 The output of launching Steam, then DX:HR; clicking Exit in the game menu, then ending the process (sigterm). The game freezes up when I click Exit, so I have to send SIGTERM to the process. Using Wine on Solus (Gallium Nine enabled). -- 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 10

[Bug 59231] New: Not LT & RT on some old PC video games.
by WineHQ Bugzilla Jan. 18, 2026

Jan. 18, 2026

http://bugs.winehq.org/show_bug.cgi?id=59231 Bug ID: 59231 Summary: Not LT & RT on some old PC video games. Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: jeremy.bezairie(a)gmail.com Distribution: --- I think component is dinput & xinput but I can't select both so -unknown. Since Proton uses Wine, see https://github.com/ValveSoftware/Proton/issues/9373 . -- 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 59268] New: crashes in 16-bit XP-era application on wow64
by WineHQ Bugzilla Jan. 18, 2026

Jan. 18, 2026

http://bugs.winehq.org/show_bug.cgi?id=59268 Bug ID: 59268 Summary: crashes in 16-bit XP-era application on wow64 Product: Wine Version: 11.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: andyrox28(a)clowmail.com Distribution: --- Created attachment 80197 --> http://bugs.winehq.org/attachment.cgi?id=80197 errors and trace for page fault I have an old 16-bit Win XP dictionary application running on kernel 5.15.193 under wow64. It's amazing to be able to run this thing with Wine 11.0 on an oldish 64-bit system (with propriatery Nvidia 340.108 x11-only driver). Unfortunately in this case it still seems quite unstable due to different types of errors (see attachment). The same application works fine on a similar native 32-bit 5.15.193 installation with Intel i915 driver. -- 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 58729] New: various bugs in Jedi Knight - Dark Forces II Demo (macOS)
by WineHQ Bugzilla Jan. 18, 2026

Jan. 18, 2026

http://bugs.winehq.org/show_bug.cgi?id=58729 Bug ID: 58729 Summary: various bugs in Jedi Knight - Dark Forces II Demo (macOS) Product: Wine Version: 10.14 Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cemer99797(a)isorax.com This is a new bug report following my previous bug report (bug# 58156). In the previous bug report, the game Jedi Knight - Dark Forces II Demo could not launch at all on macOS, with the following error: > "err:module:loader_init "smackw32.DLL" failed to initialize, aborting" As of Wine-devel 10.14, this game is now playabale again but only with workaround and caveats. (comments cross-posted as well in bug# 58156) my system: macOS 11 game demo download page (choose Download this File > Agree > Jedi Knight Demo.zip): https://community.pcgamingwiki.com/files/file/1308-jedi-knight-dark-forces-… sha256: 7bc013918cf79879a086a10c27306f2f3511852726f4b4a9fec09668ed221d18 ---- To play the game, you have to launch the JEDI.EXE launcher app (not the JKDEMO.EXE game app) and click "Play Jedi Knight Demo"... After clicking "Play Jedi Knight Demo": 1. the game app will be launched to an all-black fullscreen and tries to change the screen resolution 2. the game app will minimize itself to the macOS Dock after 1 to 3 seconds 3. the same error pop-up as in my first post will show up: > Unable to start the Jedi Knight Demo game program. Try running JK.EXE where you installed the Demo directly. Also make sure you have the latest DirectX drivers installed on your system. Clicking the minimized game app from the macOS Dock (grayscale Jedi icon) will return the game app to fullscreen, with an all-black fullscreen and the intro video music playing in the background. Pressing Esc will skip the all-black intro video and correctly load the main menu and the game is playable! Press the equals key to increase the game viewport to fill the screen. ### NOTES: 1. if you choose "Cutscenes" from the main menu and press OK to play the Splash movie (intro movie), it will now play correctly 2. if you switch out of (Cmd-Tab) and return to the game from: * the all-black intro video (before pressing Esc to skip): the game correclty returns to the all-black intro video * the main menu: the main menu will now be all black, but the sounds still play when clicking your mouse and pressing Esc * the correctly-playing intro video from the Cutscenes menu: the game returns to an all-black intro video, but if you skip it (Esc), the main menu will display correctly * gameplay: the game viewport will be all the way off-screen to the top of the screen, meaning only the bottom 20% of the game can be seen (press the equals key to increase the in-game viewport). If you press Esc the pause menu still appears correctly * the pause menu, activated for the first time from gameplay: the game returns to an all-black pause menu, and pressing Esc returns the game viewport being off-screen to the top as before * the pause menu, activated for a second time from gameplay: the pause menu correctly reappears, but after returning to gameplay, the game viewport is still off to the top of the screen 3. if you close all macOS Terminal windows (which normally exits all wine processes), the game app will still be running, but the error pop-up will be killed. The game can be exited by force-quitting the wine processes in macOS Activity Monitor or Force Quit dialog I also bisected this with Wine-devel 10.12 and 10.13, and they both give the same error as in my first post: > "smackw32.DLL" failed to initialize, aborting so this was fixed in Wine-devel 10.14 I am using the official WineHQ/Gcenx binary from Homebrew/GitHub: https://formulae.brew.sh/cask/wine(a)devel https://github.com/Gcenx/macOS_Wine_builds/releases/download/10.14/wine-dev… -- 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 10

[Bug 58145] New: Out of Ctrl 1.2: game doesn't launch, gives error
by WineHQ Bugzilla Jan. 18, 2026

Jan. 18, 2026

http://bugs.winehq.org/show_bug.cgi?id=58145 Bug ID: 58145 Summary: Out of Ctrl 1.2: game doesn't launch, gives error Product: Wine Version: 10.6 Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cemer99797(a)isorax.com Created attachment 78425 --> http://bugs.winehq.org/attachment.cgi?id=78425 Wine-devel 10.6 terminal log The game Out of Ctrl 1.2 doesn't launch and gives the following error in a pop-up window on launch: Error Failed to initialize player Details: Failed to initialize graphics. Make sure you have DirectX 11 installed, have up to date drivers for your graphics card and have not disabled 3D acceleration in display settings. InitializeEngineGraphics failed tested using Gcenx's wine-devel 10.6 build (https://github.com/Gcenx/macOS_Wine_builds/releases/tag/10.6) with GStreamer 1.26.0 download link (20 MB) (choose "OutOfCtrl_v1_2_EXE.zip"): https://miknugget.itch.io/out-of-ctrl shas256: 5d26c746c4e85b98af2f1f9fb4a4daeed837deb49427bf108935545f8958dba9 I'm using macOS 11 -- 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 23

[Bug 58265] New: regression in Wine >=10.7 for DXVK DLL override on macOS
by WineHQ Bugzilla Jan. 18, 2026

Jan. 18, 2026

http://bugs.winehq.org/show_bug.cgi?id=58265 Bug ID: 58265 Summary: regression in Wine >=10.7 for DXVK DLL override on macOS Product: Wine Version: 10.7 Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cemer99797(a)isorax.com Created attachment 78608 --> http://bugs.winehq.org/attachment.cgi?id=78608 macOS Terminal log, wine-devel 10.7 On macOS, there is a bug (https://bugs.winehq.org/show_bug.cgi?id=58145) that can be worked around with a DXVK DLL override (for d3d11.dll) in Wine-devel 10.6 and lower, but this workaround stops working in Wine-devel 10.7 (also tested not working in 10.8) repost of my comment from that previous bug: regression in wine-devel 10.7 - DXVK DLL workaround stops working There's new regression in wine-devel 10.7: now the DXVK DLL override workaround doesn't work, the app always gives the original error pop-up window with the same message. Attached is the macOS Terminal log after copying Gcenx's 32-bit `d3d11.dll` from his DXVK-macOS package to the same directory as the OutOfCtrl.exe executable. When tested with wine-devel 10.6, it still works. > % cp /Users/toastybug/dxvk-macOS/x32/d3d11.dll /Users/toastybug/Windows_Apps/OutOfCtrl_v1_2_EXE/ > % cd /Users/toastybug/Windows_Apps/OutOfCtrl_v1_2_EXE/ > % WINEDEBUG=module WINEDLLOVERRIDES="d3d11=n" wine OutOfCtrl.exe tested using Gcenx's wine-devel 10.7 build (https://github.com/Gcenx/macOS_Wine_builds/releases/tag/10.7) with GStreamer 1.26.1 on macOS 11.7.10 and Gcenx's DXVK-macOS v1.10.3-20230507-repack (https://github.com/Gcenx/DXVK-macOS/releases/tag/v1.10.3-20230507-repack) -- 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 11

[Bug 59273] New: bad d3d streaming buffer flash range tracking
by WineHQ Bugzilla Jan. 18, 2026

Jan. 18, 2026

http://bugs.winehq.org/show_bug.cgi?id=59273 Bug ID: 59273 Summary: bad d3d streaming buffer flash range tracking Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)list.winehq.org Reporter: trass3r(a)gmail.com Distribution: --- In Dungeon Keeper 2 I noticed bad performance due to: > fixme "Doing a copy of a mapped buffer (expect performance issues)" I took a perf trace and most of the time was spent copying 512KB of streaming buffer back and forth just for a few vertices for every DrawIndexedPrimitive. It always maps the whole streaming buffer even though it tracks the changed parts and flushes them correctly: https://gitlab.winehq.org/wine/wine/-/commit/793ac83d5b7fc0bc440714b218d607… wow64_map_buffer does skip the copy if you use GL_MAP_INVALIDATE_* flags but wined3d fails to properly set these flags. But then you still have the copy at unmap which happens cause it doesn't track the flush range calls done by wined3d. https://github.com/wine-mirror/wine/compare/master...Trass3r:wine:map-buffe… -- 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 57988] New: BigPEmu 1.18: D3D12 rendering issues
by WineHQ Bugzilla Jan. 18, 2026

Jan. 18, 2026

https://bugs.winehq.org/show_bug.cgi?id=57988 Bug ID: 57988 Summary: BigPEmu 1.18: D3D12 rendering issues Product: Wine Version: 10.3 Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cemer99797(a)isorax.com Created attachment 78238 --> https://bugs.winehq.org/attachment.cgi?id=78238 intro with D3D12 In BigPEmu (an Atari Jaguar emulator), .png images are not loaded/rendered correctly when using the D3D12 renderer Steps to reproduce: 1. launch BigPEmu 1.18 as follows and note how the intro animation looks using the default OpenGL renderer: wine ~/BigPEmu_v118/BigPEmu.exe 2. use backspace/enter to navigate backward/forward in BigPEmu, go to main menu > Input > Input Device 1 > Set Bindings, and note how the controller image looks in the top right 3. change to D3D12 renderer: go back to the main menu > Video > Video Plugin > BigPEmu_Video_D3D12 4. exit and relaunch BigPEmu, note how the intro looks, and once inside the app note how the background looks. Go back to the Set Bindings menu and note how the controller image looks. Check the attached screenshots tested with BigPEmu 1.18 for Windows x64 download link: https://www.richwhitehouse.com/jaguar/builds/BigPEmu_v118.zip archive.org link: https://archive.org/download/bigpemu-v1.00/BigPEmu_v118.zip SHA-256: 9863390fca342e7c6bff0d7dc7d70d181bdff92796aa8d262d91e8fc909104b2 tested on macOS 11.7.10 Intel CPU (Haswell), integrated Intel GPU (HD Graphics 5000) Wine Devel 10.3 from homebrew -- 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 19

[Bug 57975] New: screen shaders don't work in BigPEmu.exe
by WineHQ Bugzilla Jan. 18, 2026

Jan. 18, 2026

https://bugs.winehq.org/show_bug.cgi?id=57975 Bug ID: 57975 Summary: screen shaders don't work in BigPEmu.exe Product: Wine Version: 10.0 Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cemer99797(a)isorax.com BigPEmu is an Atari Jaguar emulator, it runs Atari Jaguar games fine under Wine Stable 10.0 on macOS 11. The problem is there is a "screen effects" feature (which are like screen shaders in RetroArch, used to emulate old CRTs, etc) which doesn't work. By default, BigPEmu uses OpenGL (BigPEmu main menu > Video > Video Plugin > BigPEmu_Video_OpenGL) but can also be changed to use D3D12 which will cause it crash at startup on macOS 11. Steps to reproduce: 1. launch BigPEmu 1.18 with the following options (also opens a console): wine ~/BigPEmu_v118/BigPEmu.exe * -conout 2. use backspace/enter to navigate backward/forward in BigPEmu, go back to the main menu, then Video > Screen Effect > choose any screen effect 3. an error message pops up: "Failed to set the selected screen effect. It may be incompatible with your hardware or video plugin. You can enable logging and check the log for more details." 4. check the console which shows this error: "[1;31mError: Graphics hardware isn't equipped to run screen effects. If this error occurs with SM5.0-compatible hardware, try updating your graphics drivers." tested with BigPEmu 1.18 for Windows x64 download link: https://www.richwhitehouse.com/jaguar/builds/BigPEmu_v118.zip SHA-256: 9863390fca342e7c6bff0d7dc7d70d181bdff92796aa8d262d91e8fc909104b2 tested on macOS 11.7.10 Intel CPU (Haswell), integrated Intel GPU (HD Graphics 5000) Wine Stable 10.0 with GStreamer 1.24.12 from homebrew -- 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 25

[Bug 59270] New: [WIKI] Update install instructions for Ubuntu 25.04/25.10 due to apt changes
by WineHQ Bugzilla Jan. 18, 2026

Jan. 18, 2026

http://bugs.winehq.org/show_bug.cgi?id=59270 Bug ID: 59270 Summary: [WIKI] Update install instructions for Ubuntu 25.04/25.10 due to apt changes Product: Wine-staging Version: unspecified Hardware: Other OS: other Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: b1779506(a)trbvn.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com https://gitlab.winehq.org/wine/wine/-/wikis/Debian-Ubuntu The current instructions in the "WineHQ repository" section cause an installation failure on Ubuntu 25.10 (and 24.04+) due to strict key format enforcement by newer apt versions. The specific command "wget ... | gpg --dearmor -o ...winehq-archive.key" creates a binary keyring file but saves it with a .key extension. apt now rejects this mismatch with the error: "The key(s) in the keyring /etc/apt/keyrings/winehq-archive.key are ignored as the file has an unsupported filetype," because it expects .key files to be ASCII armored (text) and .gpg files to be binary. Since the repository .sources files (e.g., winehq-questing.sources) are hardcoded to look for /etc/apt/keyrings/winehq-archive.key, the most compatible fix is to remove the gpg --dearmor step and save the key as plain ASCII text. I suggest modifying the "Download and add the repository key" command in the Wiki to the following: wget -O - https://dl.winehq.org/wine-builds/winehq.key | sudo tee /etc/apt/keyrings/winehq-archive.key > /dev/null -- 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