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

[Bug 9127] Multiple applications require system stream support in the MPEG-I splitter (Drome Racers, Ninki Seiyuu no Tsukukurikata)
by WineHQ Bugzilla Oct. 3, 2025

Oct. 3, 2025

http://bugs.winehq.org/show_bug.cgi?id=9127 --- Comment #125 from Zeb Figura <z.figura12(a)gmail.com> --- (In reply to Bob from comment #124) > This issue is still reproducible in Wine 10.14. > After the error message is shown, the cutscene audio works with a black > screen. > The terminal shows: > > 01a8:err:quartz:autoplug Failed to add filter, hr 0x80004005. Please ensure that your 32-bit GStreamer plugins are installed and try again. -- 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 7115] Need for Speed III installer fails in Win9X mode, reporting "Could not get 'HardWareKey' value" (active PnP device keys in 'HKEY_DYN_DATA\\Config Manager\\Enum' missing)
by WineHQ Bugzilla Oct. 3, 2025

Oct. 3, 2025

http://bugs.winehq.org/show_bug.cgi?id=7115 Zeb Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |b2acf5d8568026715101d4509bb | |e043889f0aca1 Status|STAGED |RESOLVED CC| |z.figura12(a)gmail.com Resolution|--- |FIXED --- Comment #29 from Zeb Figura <z.figura12(a)gmail.com> --- Fixed upstream by b2acf5d8568026715101d4509bbe043889f0aca1. -- 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 58736] New: Commandos: Behind Enemy Lines screen rotated, when playing on Xephyr/Wayland with KWin_x11
by WineHQ Bugzilla Oct. 3, 2025

Oct. 3, 2025

http://bugs.winehq.org/show_bug.cgi?id=58736 Bug ID: 58736 Summary: Commandos: Behind Enemy Lines screen rotated, when playing on Xephyr/Wayland with KWin_x11 Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: nintyfan19(a)gmail.com Distribution: --- Created attachment 79358 --> http://bugs.winehq.org/attachment.cgi?id=79358 Logs from GDI Game is launched incorrectly. Screen is rotated. I do not known if GDI is broken or something else. I attached GDI logs, cause I think it is most suspicious. -- 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 57547] New: All HIDRAW devices stop working after pressing extra button on Logitech G903 mouse
by WineHQ Bugzilla Oct. 3, 2025

Oct. 3, 2025

https://bugs.winehq.org/show_bug.cgi?id=57547 Bug ID: 57547 Summary: All HIDRAW devices stop working after pressing extra button on Logitech G903 mouse Product: Wine Version: 10.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: hid Assignee: wine-bugs(a)winehq.org Reporter: dixonte+winehq(a)stc-networks.com Distribution: --- Created attachment 77615 --> https://bugs.winehq.org/attachment.cgi?id=77615 WINEDEBUG=+hid,+plugplay,+dinput,+rawinput WINEPREIF=$HOME/Games/star-citizen /usr/lib/wine-staging-10.0_rc2/bin/wine control I have my G903 configured such that pressing one of the extra buttons emulates pressing F14 on a keyboard. I have also built a foot pedal using a microcontroller that does the same thing. I use this for push-to-talk in Discord. When I press the extra button on my mouse, this seems to cause an error in wine that stops all HIDRAW devices from working until I restart wineserver. Oddly and importantly, the foot pedal does not cause the same issue. (I'm vaguely aware this mouse is what Logitech calls 'HID++', so I wouldn't be surprised if they are doing something weird that is tripping wine up.) I've attached a log of reproducing the issue by running 'wine control' with WINEDEBUG=+hid,+plugplay,+dinput,+rawinput Now that I know how to do it I can reproduce the issue 100% of the time. -- 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 33

[Bug 35648] New: Anthem Room Correction 2 v1.0.1: crash when connecting to A/V receiver in auto mode
by wine-bugs＠winehq.org Oct. 2, 2025

Oct. 2, 2025

http://bugs.winehq.org/show_bug.cgi?id=35648 Bug ID: 35648 Summary: Anthem Room Correction 2 v1.0.1: crash when connecting to A/V receiver in auto mode Product: Wine Version: 1.7.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tristan.schmelcher(a)gmail.com Created attachment 47607 --> http://bugs.winehq.org/attachment.cgi?id=47607 Console output The application Anthem Room Correction 2 v1.0.1 crashes when trying to connect to an A/V receiver if run in automatic mode (with "/Auto" specified on the command line). The application also fails in manual mode at the same spot, but it doesn't crash; instead it hangs with 100% CPU usage. The console output with stack trace from the crash in automatic mode is attached. The application can be downloaded at http://anthemav.com/downloads/ARC-2%20Setup.zip, but you must have an Anthem A/V receiver in order to get this far in it. I am happy to carry out suggested testing/debugging. 74dc2107ca936dddbd0fc6abbb2baf74e387c163 ARC-2 Setup.zip -- 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 8

[Bug 58734] New: How to disable usage of wayland and use x11 (xwayland) instead
by WineHQ Bugzilla Oct. 2, 2025

Oct. 2, 2025

http://bugs.winehq.org/show_bug.cgi?id=58734 Bug ID: 58734 Summary: How to disable usage of wayland and use x11 (xwayland) instead Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: euloanty(a)live.com Distribution: --- After 9.22 it enforces wayland but it does not work correctly on my machine (like UI issues, keyboard issues, no touch support etc). How to disable it? -- 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 58733] New: widl gives a segmentation fault.
by WineHQ Bugzilla Oct. 2, 2025

Oct. 2, 2025

http://bugs.winehq.org/show_bug.cgi?id=58733 Bug ID: 58733 Summary: widl gives a segmentation fault. Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com Distribution: Debian I tried this command: ~/wine/tools/widl/widl -I ~/wine/include/ -L ~/wine/dlls/stdole2.tlb/ ~/wine/include/msinkaut.idl Result: Segmentation fault This command works for other idl files like wbemdisp.idl I found a hack to work around the crash is to make the 4 methods in msinkaut that contain IDataObject static; might be a pointer to the cause of the bug? diff --git a/include/msinkaut.idl b/include/msinkaut.idl index 743dec82a40..0bc6d5c79d5 100644 --- a/include/msinkaut.idl +++ b/include/msinkaut.idl @@ -656,20 +656,20 @@ cpp_quote("#endif /* _WINGDI_ */") [in] VARIANT PacketData, [in] VARIANT PacketDescription, [out, retval] IInkStrokeDisp **Stroke); - HRESULT ClipboardCopyWithRectangle( + static HRESULT ClipboardCopyWithRectangle( [in] IInkRectangle *Rectangle, [in] InkClipboardFormats ClipboardFormats, [in] InkClipboardModes ClipboardModes, [out, retval] IDataObject **DataObject); - HRESULT ClipboardCopy( + static HRESULT ClipboardCopy( [in] IInkStrokes *strokes, [in] InkClipboardFormats ClipboardFormats, [in] InkClipboardModes ClipboardModes, [out, retval] IDataObject **DataObject); - HRESULT CanPaste( + static HRESULT CanPaste( [in] IDataObject *DataObject, [out, retval] VARIANT_BOOL *CanPaste); - HRESULT ClipboardPaste( + static HRESULT ClipboardPaste( [in] long x, [in] long y, [in, unique] IDataObject *DataObject, -- 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 58566] New: Maxis games (Simcity2000, SimCopter, StreetsofSimCity) do not work anymore because smackw32.dll won't load, no matter how much it's pasted all over the file system. WoW64 (yes I know you'll just ignore this bug as won't fix: that's how opensource is now)
by WineHQ Bugzilla Oct. 2, 2025

Oct. 2, 2025

http://bugs.winehq.org/show_bug.cgi?id=58566 Bug ID: 58566 Summary: Maxis games (Simcity2000, SimCopter, StreetsofSimCity) do not work anymore because smackw32.dll won't load, no matter how much it's pasted all over the file system. WoW64 (yes I know you'll just ignore this bug as won't fix: that's how opensource is now) Product: Wine Version: 10.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: chaosesqueteam(a)sogetthis.com Distribution: --- This dll doesn't work on WoW: it's in the game dir, and I put it in systemwow64, system32, and system. Doesn't work. No maxis games can run. (also note: the 16 bit installer doesn't work at all since you don't allow 16 bit apps in wow64 mode, only 32, so all of the games everyone is using wine for can't be installed the normal way anymore since they use 16 bit installer binaries) 0640:err:environ:init_peb starting L"F:\\WIN95\\SC2K\\SIMCITY.EXE" in experimental wow64 mode 0640:fixme:wow:wow64_NtSetLdtEntries 1107 0488323f 0000f335 0000 00000000 00000000: stub 0640:err:module:loader_init "smackw32.dll" failed to initialize, aborting 0640:err:module:loader_init Initializing dlls for L"F:\\WIN95\\SC2K\\SIMCITY.EXE" failed, status c0000005 Ok so I'll be banned now for reporting a bug >WOW64: WONT FIX!!! >MAXIS 16 bit installer! WONT FIX >32 bit dll though and you got around the installer >WONT FIX AND BANNED!!! Opensource really sucks these days. I liked it when I was coding with my friends 20 years ago. This culture of bullshit didn't exist then, and ultra professionalism. We are hackers. Not professional software engineers. -- 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 4

[Bug 58613] New: wine cannot run WinAuth at all - no GUI, instant crash
by WineHQ Bugzilla Oct. 2, 2025

Oct. 2, 2025

http://bugs.winehq.org/show_bug.cgi?id=58613 Bug ID: 58613 Summary: wine cannot run WinAuth at all - no GUI, instant crash Product: Wine Version: 10.13 Hardware: aarch64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: owokkgccs0s8os0gk4o4gsk8wss0w0ww(a)ai.notifier.in Distribution: --- https://github.com/winauth/winauth 1. "wine /path/to/WinAuth.exe" -- 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 4

[Bug 58583] New: msvcp140: Multiple modern applications using C++ Concurrency crash in CONCRT140.dll on startup
by WineHQ Bugzilla Oct. 2, 2025

Oct. 2, 2025

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 3