wine-bugs August 2025

wine-bugs@winehq.org

1 participants
376 discussions

[Bug 53573] New: Warcraft III Reforged 1.33.0.19194 has black main menu
by WineHQ Bugzilla 22 Sep '25

22 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=53573 Bug ID: 53573 Summary: Warcraft III Reforged 1.33.0.19194 has black main menu 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: kolAflash(a)kolahilft.de Distribution: --- Created attachment 72950 --> https://bugs.winehq.org/attachment.cgi?id=72950 STDOUT/STDERR log when warcraft-iii-reforged-1.33.0.19194 is starting an switching to black main menu Last night (2022-08-18) Blizzard released an update for Warcraft III Reforged from version 1.32.x to 1.33.0.19194. Since then the main menu of the game is just black! But I can hear the sound of the main menu. I attached a STDOUT/STDERR log. Version 1.32.x of the game was running fine using wine-staging-7.14. (didn't test any other wine version before) Wine versions I just tried: wine-staging-7.14 wine-staging-7.15 wine-devel-7.15 OS: Debian-11 Wine: https://dl.winehq.org/wine-builds/debian/ GPU: Radeon RX 590 Neither standard Wine D3D11 OpenGL based implementation (WineD3D) nor DXVK is working. Maybe slightly related: Warcraft III: staying in menus quickly gobs all system memory https://github.com/doitsujin/dxvk/issues/1866 -- 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 17

[Bug 57192] New: X11DRV_SetCursorPos breaks when xinput "Coordinate Transformation Matrix" is customized
by WineHQ Bugzilla 21 Sep '25

21 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=57192 Bug ID: 57192 Summary: X11DRV_SetCursorPos breaks when xinput "Coordinate Transformation Matrix" is customized Product: Wine Version: 9.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: mk939(a)ymail.com Distribution: --- Created attachment 77083 --> https://bugs.winehq.org/attachment.cgi?id=77083 WINEDEBUG=+cursor,+win wine minetest.exe | trimmed to one repetition of the bugged SetCursorPos call Discovered by testing Minetest 5.9.0 [1] in Wine. In-game, the cursor is always moved to the center. However, when the xinput "Coordinate Transformation Matrix" parameter, the cursor moves to unpredictable positions (bottom right corner, for example). The game becomes unplayable. I think it's caused by "X11DRV_SetCursorPos" because skipping "NtUserSetCursorPos" entirely does avoid this issue. The cursor position is no longer centred, but the game does not look as glitchy any more. System specifications: * Ubuntu 22.04, X11, xfce4 * amdgpu driver Reproduced in Wine 9.1, Wine 9.17 and Proton 9.0-2. Reproduced with * Wine's virtual desktop on and off * Window manager decorations on and off (winecfg) * Window manager control on and off (winecfg) Steps to reproduce: 1. xinput list 2. Remember the xinput <ID> of the mouse (Virtual core pointer -> HID) 3. xinput --set-prop <ID> 'Coordinate Transformation Matrix' 1.1 0 0 0 1.1 0 0 0 1 4. Join a world in Minetest and try to play This problem does not occur when the Transformation Matrix is set to "1.0 0 0 0 1.0 0 0 0 1". It also does not occur on Windows due to lack of xinput and X11 in the first place. [1] https://github.com/minetest/minetest/releases/download/5.9.0/minetest-5.9.0… -- 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 24951] New: Call of Duty / UO: Jerky freelook
by wine-bugs＠winehq.org 21 Sep '25

21 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=24951 Summary: Call of Duty / UO: Jerky freelook Product: Wine Version: 1.3.6 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gav616(a)gmail.com At the main menu: When the cursor is moveed around it 'seems' to be at a very low framerate and it jerks about. In-game: When freelooking around, the game seems to stay at the correct rate but the mouse movements are jerked and misinterpreted. It looks like the FPS is dropping to 5 when the jerks occur, but the FPS remains constant through the jerks. Audio is not effected. -- 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.

2 18

[Bug 54227] New: Altium Designer 20.x - 22.x slowness in 2D schematics editor - possibly GDI font rendering problem
by WineHQ Bugzilla 21 Sep '25

21 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=54227 Bug ID: 54227 Summary: Altium Designer 20.x - 22.x slowness in 2D schematics editor - possibly GDI font rendering problem Product: Wine-staging Version: 7.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kepszlok(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 73773 --> https://bugs.winehq.org/attachment.cgi?id=73773 Wine's output This is a problem that affects all Altium Designer versions from 20.x to current, with all wine-staging versions of 7.xx branch. See AD compatibility reports: 20.x https://appdb.winehq.org/objectManager.php?sClass=version&iId=38478 21.x https://appdb.winehq.org/objectManager.php?sClass=version&iId=40170 22.x https://appdb.winehq.org/objectManager.php?sClass=version&iId=40683 All of them shows slowness in the 2D schematics editor, while the 3D PCB editor works fine. Using the schematics editor, this message appears in constantly: 0118:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style 0000000001647F70. (the schematics editor itself working fine, just unusably slow) Possible reason: "probably because X2 uses GDI font rendering by default and lacks option to turn it off" -- 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 54670] New: 16-bit applications fail in wow64 mode
by WineHQ Bugzilla 21 Sep '25

21 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=54670 Bug ID: 54670 Summary: 16-bit applications fail in wow64 mode Product: Wine Version: 8.0 Hardware: x86-64 OS: Linux Status: NEW Keywords: download, Installer, wow64 Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Debian $ wineserver -k ; rm -rf ~/.wine ; WINE=/opt/oldwownew/wine-8.0/bin/wine winetricks -q icodecs ------------------------------------------------------ Executing load_icodecs Executing cabextract -q -d /home/austin/.wine/dosdevices/c:/windows/temp/codinstl/ /home/austin/.cache/winetricks/icodecs/codinstl.exe Executing cd /home/austin/.wine/dosdevices/c:/windows/temp/codinstl/ Executing /opt/oldwownew/wine-8.0/bin/wine setup.exe /s 0284:err:environ:init_peb starting L"C:\\windows\\syswow64\\winevdm.exe" in experimental wow64 mode 0284:fixme:wow:wow64_NtSetLdtEntries 0107 02d0323f 0100f338 0000 00000000 00000000: stub 0284:err:module:LdrInitializeThunk "krnl386.exe16" failed to initialize, aborting 0284:err:module:LdrInitializeThunk Initializing dlls for L"C:\\windows\\syswow64\\winevdm.exe" failed, status c0000005 ------------------------------------------------------ -- 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 15

[Bug 58584] New: msvcp140: Multiple modern applications using C++ Concurrency crash in CONCRT140.dll on startup
by WineHQ Bugzilla 20 Sep '25

20 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58584 Bug ID: 58584 Summary: msvcp140: Multiple modern applications using C++ Concurrency crash in CONCRT140.dll on startup Product: Wine Version: 10.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: msvcp Assignee: wine-bugs(a)winehq.org Reporter: waser(a)waser.tech Distribution: --- This report details a consistent, immediate startup crash in `CONCRT140.dll` affecting modern S.T.A.L.K.E.R. engine forks. These engines are based on the open-source **Open X-Ray 1.6**, which itself works flawlessly under Wine. The crash only appears in these newer, more advanced forks which leverage the MSVC concurrency runtime for performance. This strongly indicates the issue lies within Wine's implementation of these APIs, not a bug in the engines themselves. This is effectively a regression, as the baseline engine works while the newer, concurrency-enabled versions do not. **Existing Related Bugs:** This issue appears to be a new, highly reproducible test case for known problems in Wine's concurrency support. We are filing this as a new report due to the unique test case and the specific failure point (constructor vs. destructor), but it is likely caused by the same underlying issues as: - **Bug 52899:** Notes that `CONCRT140.dll` requires `CreateEventExW` from `kernel32`. This is the most likely root cause. - **Bug 41749:** Shows a crash in the destructor for `Concurrency::details::_TaskCollection`. Our crash occurs in the *constructor* of this same object, demonstrating a different failing code path. Our report provides two clear methods to reproduce this crash, including one that is fully free and requires no commercial software. --- ### **Primary Reproduction Steps (IX-Ray on S.T.A.L.K.E.R.: Call of Pripyat)** *(Steps 1-5 as in previous draft)* 6. **Run the Game with Debug Logging:** Launch the game using its main executable with full debug channels enabled. ```bash WINEDEBUG=+all wine Stalker-COP.exe &> stalker_cop_crash_all.log WINEDEBUG=+seh,+loaddll wine Stalker-COP.exe &> stalker_cop_crash_seh.log ``` 7. **Result:** The process will crash immediately. The game's own crash log (in `_appdata_ixray_/logs`) and the attached Wine debug logs will show a fatal error in `CONCRT140.dll`. --- ### **Alternative Reproduction Steps (AOEngine on S.T.A.L.K.E.R. Anomaly)** This method is fully free and requires no commercial game assets. 1. **Download S.T.A.L.K.E.R. Anomaly:** Download the standalone game from its [ModDB page](https://www.moddb.com/mods/stalker-anomaly/downloads). 2. **Download AOEngine:** Download the latest AOEngine release from its [ModDB addons page](https://www.moddb.com/mods/stalker-anomaly/addons/aoengine). 3. **Install AOEngine:** Extract the contents into the Anomaly game's `bin` directory, overwriting `AnomalyDX11.exe`. 4. **Create a Clean Wine Prefix:** ```bash export WINEPREFIX=~/.wine_anomaly rm -rf $WINEPREFIX && wineboot -u ``` 5. **Install Runtimes:** ```bash winetricks -q vcrun2022 d3dcompiler_47 ``` 6. **Run the Game with Debug Logging:** Launch the game using the Anomaly launcher. ```bash WINEDEBUG=+all wine AnomalyLauncher.exe &> anomaly_crash_all.log WINEDEBUG=++seh,+loaddll wine AnomalyLauncher.exe &> anomaly_crash_seh.log ``` (Within the launcher, disable AVX, select DX11, disable the shader cache, and click Play). 7. **Result:** The exact same crash behavior as the IX-Ray method will be observed. The game's crash log will be in `_appdata_/logs` and the full Wine log will be `anomaly_crash_*.log`. --- **Expected Behavior:** The game launcher should appear, and the game should launch to the main menu successfully, as it does on Windows and as the baseline Open X-Ray 1.6 engine does under Wine. **Logs:** Three files will be attached for the primary reproduction case: 1. `stalker_cop_crash_seh.log`: A small log with `+seh,+loaddll` for quick initial review. 2. `stalker_cop_crash_all.log.bz2`: The complete `+all` debug log, compressed with bzip2 due to its large size. 3. `ixray-2025.08.10-02.37.21-waser.log`: The game's own crash log from its `_appdata_ixray_/logs` directory. **References:** - **IX-Ray GitHub (Open Source Engine):** https://github.com/ixray-team/ixray-1.6-stcop - **GE-Proton Issue #197 (Full History):** https://github.com/GloriousEggroll/proton-ge-custom/issues/197 -- 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 25

[Bug 42858] New: Stuttering sound setting the OS to Windows 7 and higher on FreeBSD
by wine-bugs＠winehq.org 20 Sep '25

20 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=42858 Bug ID: 42858 Summary: Stuttering sound setting the OS to Windows 7 and higher on FreeBSD Product: Wine Version: 2.4 Hardware: x86-64 OS: FreeBSD Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: adrien_fernandes2(a)hotmail.com On every games I try, when I set to Windows XP, the sound is working correctly but if I set to Windows 7 and higher, the sound will stutter, whatever the game you are trying. It's a bit annoying when you have to set the OS to Windows 7 like with Enter the Gungeon to make it work. I tried Resident Evil Revelations and Enter the Gungeon, they both have the same problem so I guess it's something related to FreeBSD (maybe more BSD OS) -- 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 48272] New: Crackling and slower audio on Ubisoft's Assassin's Creed 1 & Far Cry 3 games
by WineHQ Bugzilla 20 Sep '25

20 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=48272 Bug ID: 48272 Summary: Crackling and slower audio on Ubisoft's Assassin's Creed 1 & Far Cry 3 games Product: Wine Version: 4.21 Hardware: x86-64 OS: FreeBSD Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: adrien_fernandes2(a)hotmail.com Created attachment 65940 --> https://bugs.winehq.org/attachment.cgi?id=65940 Output of Wine 4.21 running Assassin's Creed So here it is, it might be a bit long and I'll try to be as precise as I can to explain the problem. First, list of tested games : Far Cry 2 : No audio problem ✔ Crysis : No audio problem ✔ XIII : No audio problem ✔ Far Cry 3 : Crackling audio ✖ Assassin's Creed : Crackling audio ✖ I ran all the games set on DirectX 9 and I built Wine to use Open Sound System for audio (if this is important). Assassin's Creed 1's prefix is set to WinXP and Far Cry 3's one is set to Win7 (because of Uplay). The problem is that the audio on Far Cry 3 and Assassin's Creed is weirdly crackling and slower than it should be but, not EVERY sounds in the game are making the audio crackles. On Assassin's Creed, it's when a lot of people are around me and everytime I use the eagle vision. In the menu or when outside the Animus (in the present time of the game where there are only three people and a tiny room), the audio works well. Also, an important point is that neither Assassin's Creed nor Far Cry 3 are slowed down to fit the slowed down audio issue. They both work very well when it happens which is causing a strange issue I'll describe AND SHOW below. I'm using a GTX 765m to play which is not bad for old games like these. "Your computer certainly isn't powerful enough to run the game !" you say... Well, you are not totally wrong, I could have better hardware but, in the past, when I was playing these games on Windows then, later, on GNU/Linux, I never met this problem. The two differences are that I'm playing, for the first time, Assassin's Creed _ON_FREEBSD_ and we are now almost in 2020. My last Assassin's Creed session was on GNU/Linux in 2016. Wine changed so much in almost 4 years ! But let me remind you that only two of the five games mentioned above are having issue. all my native FreeBSD games (OpenMorrowind, Xonotic, Minetest, Tales of Maj'Eyal, Quake II from Yamagi's source code etc...), videos read with mpv, music listened with moc and even Firefox are all working well without crackling or slowed down audio. And three tested games on Wine with OSS are working perfecly. I could have tested more games but I think three is good enough. So here is the "show" I mentioned in the beginning. I took a video of Assassin's Creed's problem. I recorded it with my phone so... sorry for the poor quality but you can see the problem : https://www.youtube.com/watch?v=f5rhg-PwFeU In this video, you can see two people speaking together. In the normal game, one speak and, when finished, the other answer. They _NEVER_ speak above the other. In my Assassin's Creed, the game is running well but the audio is slowed down which creates a desyncing between the slowed down voice played and the mouth of the character. And, because the game is running well beside this issue, one didn't finish his sentence and the other will start his speech over the first one (it shouldn't happen). I found a longplay video of the game which is certainly played on Windows. I copied the video link to start at the exact same moment as the one I recorded from my computer and you can see how the game should normally behave : https://youtu.be/1gGz6vf35T0?t=2991 About the crackling audio issue, it can be heard by the end of my video when I use the eagle vision. For Far Cry 3, don't even need to run the game to hear crackling and slowed down audio. I also took a video of the problem, it speaks for itself : https://www.youtube.com/watch?v=JkOXvy_42jc The original theme can be listened here : https://youtu.be/rfAeL4JfHj8?t=10 I copied the video to start at the same time of my video of Far Cry 3, in the menu. What you can notice is that the normal music is faster than in my video, it's the same problem than with Assassin's Creed 1. I fetched the output of Wine when running Assassin's Creed 1. It repeatedly says two things so I cut it into "head -n 50" and "tail -n 50". I watched the long output and nothing is different between the first 50 and last 50 lines. I hope I was clear enough, English isn't my native language so I apologize if I didn't use it correctly. -- 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 54285] New: Mostly UE4 games failing to start when trying to use faudio by wine itself
by WineHQ Bugzilla 20 Sep '25

20 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=54285 Bug ID: 54285 Summary: Mostly UE4 games failing to start when trying to use faudio by wine itself Product: Wine Version: 7.0.1 Hardware: x86-64 OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: P2 Component: xaudio2 Assignee: wine-bugs(a)winehq.org Reporter: Alexander88207(a)Protonmail.com Created attachment 73852 --> https://bugs.winehq.org/attachment.cgi?id=73852 Sea of Thieves Hello, since the update to wine 7 it is not possible to run mostly Unreal Engine 4 games. In the log there were indications that something might be wrong with the xaudio 2_7 dll. So I just applied faudio via winetricks and the games work again. Unfortunately this is not a permanent solution as there is a bug on platforms like Mac OS, FreeBSD that if you use native,buildin xaudio the sound does not work correctly in terms of stuttering and slightly distorted sound. As far as I know the games worked correctly in Wine 6.0.1. Unfortunately it is not possible for me to test more in wine-devel because the port is very often defective and also just once again not working. (Last version tested was 7.21 and it was there too) Thanks in advance! -- 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 44817] New: Some software protection schemes need ntdll.NtSetLdtEntries implementation
by wine-bugs＠winehq.org 20 Sep '25

20 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=44817 Bug ID: 44817 Summary: Some software protection schemes need ntdll.NtSetLdtEntries implementation Product: Wine Version: 3.4 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, to track https://github.com/wine-staging/wine-staging/tree/master/patches/ntdll-NtSe… The stub was added with bug 26268 ("Multiple applications need ntdll.ZwSetLdtEntries stub (kwiksupport.me, Ragnarok Online patcher)"). Unfortunately there is no further information/details *which* copy-protection scheme needs and actual implementation. No applications/games are mentioned. --- quote --- 1. Some copy protections call NtSetLdtEntries(0x000f) and then with 'retf' instruction jump to that selector expecting that it works (the tests show that NtSetLdtEntries(0x000f,0x001f) should succeed). In order to make this work a limitation to set only selectors > LDT_FIRST_ENTRY (512) in wine_ldt_set_entry() was removed. 2. wine_ldt_set_entry() was made to always mark modified selector entries as WINE_LDT_FLAGS_ALLOCATED, otherwise get_selector_entry() server call returns entries without that flag set and NtQueryInformationThread(ThreadDescriptorTableEntry) fails. --- quote --- $ wine --version wine-3.4 Regards -- 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 5

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs August 2025