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

[Bug 59775] German umlauts won't be handled correctly by typing

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59775 --- Comment #38 from AndyF <andreas.franz(a)arcor.de> --- Issue still exists on 11.15 -- 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.

Aug. 10, 2026

[Bug 55653] Logitech Extreme 3d Joystick has axes mapped incorrectly

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=55653 y5kXCS6RgtQp <jacobbrett+winehqbugs(a)jacobbrett.id.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jacobbrett+winehqbugs@jacob | |brett.id.au -- 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.

Aug. 10, 2026

[Bug 60153] Chip's Challenge 1: background music stops playing after restarting or completing a level

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=60153 --- Comment #1 from Patrick Hoffer <Patrick.M.Hoffer(a)gmail.com> --- Created attachment 81770 --> http://bugs.winehq.org/attachment.cgi?id=81770 Audio Info This is my audio driver/hardware and kernel -- 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.

Aug. 10, 2026

[Bug 60153] New: Chip's Challenge 1: background music stops playing after restarting or completing a level

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=60153 Bug ID: 60153 Summary: Chip's Challenge 1: background music stops playing after restarting or completing a level Product: Wine Version: 11.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mfplat Assignee: wine-bugs(a)list.winehq.org Reporter: Patrick.M.Hoffer(a)gmail.com Target Milestone: --- Distribution: --- Created attachment 81769 --> http://bugs.winehq.org/attachment.cgi?id=81769 Wine 11.15 log Chip's Challenge 1 Steam AppID: 346850 PE32 executable for MS Windows 6.00 (GUI), Intel i386 wine-devel-11.15-1.1.x86_64 The game requires Steamworks, so I installed and ran the Windows Steam client inside the same Wine prefix and installed Chip's Challenge through that Steam client. Distribution: Nobara Linux Host architecture: x86_64 Audio stack: PipeWire using Wine's PulseAudio driver (winepulse.drv) Sound hardware / driver: See attached (wine-audio-info.txt) Prefix / configuration The issue was reproduced using a newly created Wine prefix: ~/.wine-chips-upstream No native Windows DLLs or DLL overrides were added. Wine was run from the unmodified WineHQ development package. Steps to reproduce Start the Windows Steam client using Wine 11.15. Launch Chip's Challenge from Steam. Start a level. Confirm that the background music is playing. Restart the level. The same issue can also occur after completing a level and proceeding to another level. Expected result Background music should start playing normally again after restarting or changing levels. Actual result Background music plays correctly when the first level starts. After restarting the level, the background music no longer plays. Sound effects continue to work normally. The game itself continues running and remains playable. Additional observations The game uses Media Foundation / MFPlay for its MP3 background music. In the Wine debug trace, the first successful playback reaches the expected playback sequence, including: media_player_CreateMediaItemFromURL media_player_SetMediaItem media_player_Play mfsession_Start MF_TOPOSTATUS_STARTED_SOURCE audio renderer clock start IAudioClient::Start After restarting the level, the game again: creates the same MP3 media item, calls SetMediaItem, calls Play, and calls IMFMediaSession::Start. However, the second playback attempt does not reach MF_TOPOSTATUS_STARTED_SOURCE, the audio renderer clock is not started again, and there is no second IAudioClient::Start. This may indicate a Media Foundation / MFPlay Media Session state or topology transition problem, but I am reporting the observable application behavior rather than assuming the exact cause. Other testing The same user-visible behavior also occurs with: Proton 9.0-4 Proton 10.0-4 Proton Experimental GE-Proton 7-1 current GE-Proton These are listed only as supplemental information. The WineHQ reproduction described above was performed with upstream Wine 11.15-devel. I also tested forcing the host PipeWire graph to 44.1 kHz; this did not change the behavior. The game's MP3 files were also temporarily converted from 44.1 kHz to 48 kHz to eliminate the Media Foundation resampling path as a variable. The music still stopped after restarting the level. Debug output A complete Wine terminal/debug log from the upstream Wine 11.15 reproduction is attached separately. The trace was captured with: WINEDEBUG=+mfplat,+mfplay,+mf,+winegstreamer,+mmdevapi,+pulse,+dmo,+timestamp The log is attached as plain text / compressed text rather than pasted into this report. -- 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.

Aug. 10, 2026

[Bug 60152] WineWayland driver doesn't work anymore in Wine 11.15

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=60152 --- Comment #4 from Benjamin Legendre <legendre.benjamin(a)gmail.com> --- For information i'm using KDE/Plasma 6.7.4. -- 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.

Aug. 10, 2026

[Bug 60152] WineWayland driver doesn't work anymore in Wine 11.15

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=60152 --- Comment #3 from Benjamin Legendre <legendre.benjamin(a)gmail.com> --- Same issue for me on Arch Linux. Upgraded from os package from 11.14 to 11.15. Tested as well on a new prefix, same issue. Per default it falls back to X11 (through Xwayland). If forced it does not starts at all. See attachment logs : "Logs revealing broken wayland driver with wine 11.15" -- 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.

Aug. 10, 2026

[Bug 60152] WineWayland driver doesn't work anymore in Wine 11.15

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=60152 Benjamin Legendre <legendre.benjamin(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |legendre.benjamin(a)gmail.com --- Comment #2 from Benjamin Legendre <legendre.benjamin(a)gmail.com> --- Created attachment 81768 --> http://bugs.winehq.org/attachment.cgi?id=81768 Logs revealing broken wayland driver with wine 11.15 -- 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.

Aug. 10, 2026

[Bug 53799] FFXIV Endwalker Benchmark no audio and crashes in xaudio2_7 on exit

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=53799 Jupiter Vuorikoski <zapotah(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zapotah(a)gmail.com --- Comment #8 from Jupiter Vuorikoski <zapotah(a)gmail.com> --- I ran into this a few days ago after getting my new scarlett 16i16 and indeed, this has to do with the fact that winepulse.drv panics when there are >8 channels on the audio device on the system. This causes practically every game to crash. Some more modern approach than the static channel assumptions should propably be considered... Someone could also update the description of this bug since it is not about ffxiv but a more general winepulse.drv 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.

Aug. 10, 2026

[Bug 60121] Multi Theft Auto serial validation error

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=60121 --- Comment #10 from EpicTux123 <EpicTux123(a)proton.me> --- Sorry, I meant "game's mod" * in the previous comment, and not "game mode". -- 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.

Aug. 10, 2026

[Bug 60121] Multi Theft Auto serial validation error

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=60121 --- Comment #9 from EpicTux123 <EpicTux123(a)proton.me> --- (In reply to Hans Leidekker from comment #8) > (In reply to EpicTux123 from comment #7) > > > If Wine correctly reports your serial number then I don't see a Wine bug. > > > > Well, the same setup (having only a NVME drive) on Windows works, but in > > Wine it does not. The bug here is that it does not work, simple as that. > > > > It is probably not working in the sense that the proprietary code is > > requesting such serial in a way that may be legacy or something, which Wine > > maybe does not have support for. (It is just a guess from me, not something > > confirmed.) > > You said it works for some people which suggests that some version of Wine > does support it. You should try comparing your system with one where it does > work. Hmm, I think I have something to ponder for this issue: from the random amount I gathered of feedback from random people, the common scenario to make it work appears to be: Use Debian or a Debian-based distro (preferably Ubuntu; maybe Linux Mint can also work?) and have a SATA drive. My situation is Wine on Arch Linux and a NVME drive only. I have told the devs about this issue and one of them said he is looking into it as the problem is more complex than initially thought. As it seems, it could still be a Wine issue, since people running the game's mod server as root (shenanigans) to validate the serial seems to work. I think the culprit here is the game mode and not Wine, but I am not sure if Wine does not have even 1% of guilt in this case. That is the information I have for know. -- 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.

Aug. 10, 2026