wine-bugs August 2025

wine-bugs@winehq.org

1 participants
105 discussions

[Bug 58586] New: Wine Stable plays havoc with my non-posix shell (fish)
by WineHQ Bugzilla 10 Aug '25

10 Aug '25

http://bugs.winehq.org/show_bug.cgi?id=58586 Bug ID: 58586 Summary: Wine Stable plays havoc with my non-posix shell (fish) Product: Packaging Version: unspecified Hardware: aarch64 OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: yoyolives(a)yahoo.com CC: dimesio(a)earthlink.net Steps to reproduce: 1. Install fish and set it as your default shell. 2. Double click the Wine Stable app. The problem stems from this file: https://github.com/wine-compholio/wine-packaging/blob/master/packaging-wine… which executes an Applescript in the user's default shell. I could provide a patch but the only build script I can see is for a linux cross compile, so I haven't been able to test it 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.

1 0

[Bug 58585] New: unnamed keymap layout leads to null pointer dereference in find_xkb_layout_variant
by WineHQ Bugzilla 10 Aug '25

10 Aug '25

http://bugs.winehq.org/show_bug.cgi?id=58585 Bug ID: 58585 Summary: unnamed keymap layout leads to null pointer dereference in find_xkb_layout_variant Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: lompikvoila(a)gmail.com Distribution: --- Created attachment 79112 --> http://bugs.winehq.org/attachment.cgi?id=79112 gdb backtrace Using the winewayland would abruptly exit at launch. Running wine64 under gdb uncovers a segv happening in find_xkb_layout_variant's strcmp (see attachement, due to name being NULL). As per the documentation(https://xkbcommon.org/doc/current/group__components.html#ga50…, xkb_keymap_layout_get_name can return null if the layout does not have any name(or if there is an error). This is problematic as find_xkb_layout_variant does not handle the case where name is NULL. Returning false in find_xkb_layout_variant if name is NULL fixes the issue. -- 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 0

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

10 Aug '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 13

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

10 Aug '25

http://bugs.winehq.org/show_bug.cgi?id=58583 Bug ID: 58583 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: --- Created attachment 79107 --> http://bugs.winehq.org/attachment.cgi?id=79107 The game's own crash log from its `_appdata_ixray_/logs` directory. 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)** *(As in previous draft, but with the same logging commands)* --- **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 2

[Bug 44966] New: [ER: The Game] A style error occurred while verifying the reading of the license agreement.
by wine-bugs＠winehq.org 10 Aug '25

10 Aug '25

https://bugs.winehq.org/show_bug.cgi?id=44966 Bug ID: 44966 Summary: [ER: The Game] A style error occurred while verifying the reading of the license agreement. Product: WineHQ Apps Database Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: appdb-unknown Assignee: wine-bugs(a)winehq.org Reporter: ilya(a)ilin.pp.ua Distribution: --- Created attachment 61088 --> https://bugs.winehq.org/attachment.cgi?id=61088 Screenshot When installing the game, the possibility of accepting the license agreement is conceived only if it is fully read (textarea should scroll to the bottom). But in wine it does not work. wine 3.5 openSUSE Tumbleweed Game download: (registry don't need) https://firedrop.com/4bfe735821e6bfcb or http://www.theisozone.com/downloads/pc/windows-games/er---the-game (Black Download button) Patches: https://www.gamewatcher.com/games/er/downloads 0030:err:ole:TLB_ReadTypeLib Loading of typelib L"C:\\Program Files (x86)\\Common Files\\InstallShield\\Professional\\RunTime\\IsProBE.tlb" failed with error 2 0030:fixme:ntdll:NtLockFile I/O completion on lock not implemented yet 0030:fixme:apphelp:ApphelpCheckInstallShieldPackage stub: 0x33dd3c L"M:\\data1.hdr" 0030:err:richedit:ReadStyleSheet skipping optional destination 0030:err:richedit:ReadStyleSheet skipping optional destination 0030:err:richedit:ReadStyleSheet skipping optional destination -- 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 12

[Bug 56137] New: Overwatch 2 fails to save highlight video files
by WineHQ Bugzilla 09 Aug '25

09 Aug '25

https://bugs.winehq.org/show_bug.cgi?id=56137 Bug ID: 56137 Summary: Overwatch 2 fails to save highlight video files Product: Wine Version: 9.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: forestix(a)nom.one Distribution: --- When attempting to save an Overwatch 2 highlight video as an mp4 file (the default format), it fails with this error message: SAVING ERROR An unknown error has occurred. (6-04) Steps to reproduce: - play a game (easiest way is via Play: Training: Practice vs. AI: Casual) - after the game is over, return to the main menu - click username button (top right corner) - click history tab (top edge) - click highlights tab (left edge) - click a highlight from "today's top 5" - click save button (bottom edge) - select movie format: mp4 - click save button Note that this is a different kind of failure than the one with .webm format (bug 56059). -- 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 58582] New: Rainmeter 4.5.23: crashes on X11 after refreshing default skin Clock.ini
by WineHQ Bugzilla 09 Aug '25

09 Aug '25

http://bugs.winehq.org/show_bug.cgi?id=58582 Bug ID: 58582 Summary: Rainmeter 4.5.23: crashes on X11 after refreshing default skin Clock.ini Product: Wine Version: unspecified Hardware: x86-64 URL: https://github.com/rainmeter/rainmeter/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: castelei(a)yahoo.com Regression SHA1: 980a2e3c65bee1422adbe06fead768669835e3e1 Distribution: --- Created attachment 79106 --> http://bugs.winehq.org/attachment.cgi?id=79106 WINEDEBUG=+synchronous,+seh Rainmeter 4.5.23 Reproduction: 1) Click on the Rainmeter icon on the system tray to open the 'Manage Rainmeter' window. 2) Click on the 'Active skins' drop-down list and select illustro\Clock\Clock.ini 3) Click the 'Refresh' button to the right. This X11 error prints as the application crashes if run without +synchronous: X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 139 (RENDER) Minor opcode of failed request: 4 (RenderCreatePicture) Serial number of failed request: 15285 Current serial number in output stream: 15292 Found this regression on a merged patch newer than 10.12 (the newest development release at this time) while working on an unrelated 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.

1 3

[Bug 58542] New: Dual GPU 32-Bit PhysX
by WineHQ Bugzilla 09 Aug '25

09 Aug '25

http://bugs.winehq.org/show_bug.cgi?id=58542 Bug ID: 58542 Summary: Dual GPU 32-Bit PhysX Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: audioprof2002(a)hotmail.com Distribution: --- Batman Arkham Asylum v1.1 32-Bit PhysX has 3 modes: OFF, Normal, High. Normal & Off work ok. PhysX works, but Not High "Dual GPU", Windows driver allows to force PhysX to a single GPU, Dual GPU or CPU. Linux driver 470 does Not. Problem #1. instead of using Dual GPU on Linux or a single GPU, PhysX falls back to CPU PhysX in Linux. Problem #2. CPUs are very slow for 32-Bit, Batman Arkham Asylum PhysX High, requires 1-core 100% CPU load, gives 15fps on modern CPU´s. Problem #3. Nvidia deleted 32-Bit PhysX support in hardware since 2016-Q4, IF you install a 2017 GPU like P1000, in Windows, Activate/Force PhysX GPU, Does Not work. Only work with 2016-Q2 & older GPUs. im confused where could be the problem... Linux Nvidia 470 driver? Wine? winetricks? ¿how does Wine handle 32-Bit PhysX requests? block diagram? signal path? more details here: https://github.com/juanpc2018/Batman-Arkham-Asylum-Game-of-the-Year-Edition… -- 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 58490] New: MusicBee: tab dragging still does not work
by WineHQ Bugzilla 09 Aug '25

09 Aug '25

http://bugs.winehq.org/show_bug.cgi?id=58490 Bug ID: 58490 Summary: MusicBee: tab dragging still does not work Product: Wine Version: 10.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: v_winebugs(a)outlook.com Distribution: --- Bug 52078 was solved thanks to the drag and drop helpers being stubbed, however WINE still does not allow for tab dragging with MusicBee, so I'm adding it as a separate bug report. How to reproduce: On MusicBee, attempt to drag a tab. Expected behaviour: MusicBee should allow me to drag the tab and drop it to move it. Actual behaviour: A prohibited cursor shows up and the tab is unable to be dragged. Tested on WINE Staging 10.11 on Arch Linux -- 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 58552] New: Yabridge plugins GUI is not located on the exact location of the GUI element (WINE 10.12)
by WineHQ Bugzilla 09 Aug '25

09 Aug '25

http://bugs.winehq.org/show_bug.cgi?id=58552 Bug ID: 58552 Summary: Yabridge plugins GUI is not located on the exact location of the GUI element (WINE 10.12) Product: Wine Version: 10.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: akidevera0(a)gmail.com Distribution: --- hi, i use vanilla OS debian unstable. i have a problem on wine version 10, Where the GUI is not located in the exact gui element. i keep clicking on the empty places, it makes a sound. i don't know why its like that, but i hope you can fix it. I'm suffering installing wine 9.0 since the older packages is not available in the newer versions of Vanilla/Debian. I hope this can be fixed sooner. -Yuji Chen, Vanilla OS 2 (Debian Sid) -- 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 20

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