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 #37 from AndyF <andreas.franz(a)arcor.de> --- Steps to reproduce with VirtualBox: - install LinuxMint 22.3 Cinnamon Default with German localization - install WineHQ-stable (because staging-version fails on .NET4.8-setup) - install winetricks - install DotNet48 - install MailstoreClient - change WineHQ to staging-version - start Mailstore - press "ö" -> Error -- 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. 4, 2026

[Bug 55775] game made from unity is not play in-game video.

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=55775 --- Comment #47 from Stian Low <wineryyyyy(a)gmail.com> --- (In reply to Chunhao Hung from comment #44) > I just want to share my opinion. Thanks for feedback. > I understand that the MR-11398 workaround might break some applications, so I think it makes sense to make it opt-in through a config option, either an environment variable or a registry setting. Personally, I would prefer an environment variable. `WINE_D3D_CONFIG=no_create_flags=0x800` is implemented like the others so environment variable overrides registry when defined: [Software\\Wine\\Direct3D] "csmt"=dword:00000001 "no_create_flags"=dword:00000800 > This workaround seems to help video playback in a number of Unity games, so I think it is nice to have Unity games seem far more common and impacted by `D3D11_CREATE_DEVICE_VIDEO_SUPPORT` not failing vs vice versa for apps which may require `D3D11_CREATE_DEVICE_VIDEO_SUPPORT` not failing. I'm still seeking any apps that require `D3D11_CREATE_DEVICE_VIDEO_SUPPORT` so please let me know of any so that MR-11398 may be more thoroughly tested. > Because of that, I think it should only be treated as a temporary workaround, and it should be removable at any time once the proper implementation is done. Maybe it could also be documented on the Wine wiki with a clear note that it is temporary. I implemented in such a way to hopefully keep for long term debugging convenience purposes in case issues like Haven video bugs are ever encountered again which may allow users to find solutions without requiring dev efforts to discover cause of problems. Keeping long term potentially risks users reporting bugs due to misusing the feature but users savvy enough to use WINE_D3D_CONFIG seem to be aware of the impact such as changing `WINE_D3D_CONFIG=csmt=0x2` -- 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. 4, 2026

[Bug 60123] OutputDebugStringA/W payloads truncated at ~300 bytes in +debugstr/+seh channel output

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=60123 --- Comment #3 from Souyama <souyamadebnath(a)gmail.com> --- Anyway it's still a bug that the message is truncated and lost, instead of say split across frames like how it's in Windows. -- 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. 4, 2026

[Bug 60123] OutputDebugStringA/W payloads truncated at ~300 bytes in +debugstr/+seh channel output

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=60123 --- Comment #2 from Souyama <souyamadebnath(a)gmail.com> --- Under winedbg it's truncated to 255 characters. I understand trying to avoid buffer overflow but I was under the impression that those WINEDEBUG flags were to capture debug log outputs. I am trying to replicate this behaviour of capturing game logs. OG Reference code: https://github.com/WFCD/WFinfo/blob/master/WFInfo/LogCapture.cs Which I am replicating by making my binary launch the game with the WINEDEBUG env var set first. Can't the buffer size be made adjustible via another env var? Or if to remain fixed size increase to 4096? -- 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. 4, 2026

[Bug 59848] Please add WebP, AVIF and JXL support

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59848 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEW --- Comment #9 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- WEBP supported added https://gitlab.winehq.org/winehq/appdb/-/commit/f46ad2710ed427d50fd0dc87d80… Example with "Early Gameplay - Wine 11.14": https://appdb.winehq.org/screenshots.php?iAppId=&iVersionId=24516 I think it's a little too early for AVIF: https://caniuse.com/?search=avif Way too early early for JXL: https://caniuse.com/?search=jxl Something to revisit in the future, or maybe these should be separate reports? -- 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. 4, 2026

[Bug 60123] OutputDebugStringA/W payloads truncated at ~300 bytes in +debugstr/+seh channel output

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=60123 Souyama <souyamadebnath(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |souyamadebnath(a)gmail.com -- 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. 4, 2026

[Bug 60121] Multi Theft Auto serial validation error

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=60121 --- Comment #8 from Hans Leidekker <hans(a)meelstraat.net> --- (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. -- 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. 4, 2026

[Bug 60121] Multi Theft Auto serial validation error

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=60121 --- Comment #7 from EpicTux123 <EpicTux123(a)proton.me> --- (In reply to Hans Leidekker from comment #6) > (In reply to EpicTux123 from comment #5) > > > That's something different, it talks about a Linux native server program. > > > > From my understanding, that ls command is to say that if you don't have such > > entries then the serial validation will not work in Wine as well. But I > > can't be sure; the details of this are proprietary. > > No, Wine doesn't use those names. > > > What I know is that it works on Windows with NVME-only, and that Wine has > > the correct serial number (I can attest by using Linux native commands and > > verify it's the same number). > > 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.) I am also trying to work with the developers to improve the situation on Wine, but the fact is that in Wine it does not work when in Windows it does, so there is the bug. It is difficult, because it is a proprietary anti-cheat mechanism, so details of it cannot be talked in public. -- 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. 4, 2026

[Bug 60121] Multi Theft Auto serial validation error

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=60121 --- Comment #6 from Hans Leidekker <hans(a)meelstraat.net> --- (In reply to EpicTux123 from comment #5) > > That's something different, it talks about a Linux native server program. > > From my understanding, that ls command is to say that if you don't have such > entries then the serial validation will not work in Wine as well. But I > can't be sure; the details of this are proprietary. No, Wine doesn't use those names. > What I know is that it works on Windows with NVME-only, and that Wine has > the correct serial number (I can attest by using Linux native commands and > verify it's the same number). If Wine correctly reports your serial number then I don't see a Wine 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.

Aug. 4, 2026

[Bug 60121] Multi Theft Auto serial validation error

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=60121 --- Comment #5 from EpicTux123 <EpicTux123(a)proton.me> --- (In reply to Hans Leidekker from comment #4) > (In reply to EpicTux123 from comment #3) > > https://wiki.multitheftauto.com/wiki/Client_on_Linux_Manual#Known_issues:~: > > text=Serial%20Validation%20fails says the output of > > > > $ ls -l /dev/disk/by-id > > > > > > should contain at least any entry starting with "ata-" or "scsi-", which is > > not my case (everything starts with "nvme" only). > > That's something different, it talks about a Linux native server program. From my understanding, that ls command is to say that if you don't have such entries then the serial validation will not work in Wine as well. But I can't be sure; the details of this are proprietary. What I know is that it works on Windows with NVME-only, and that Wine has the correct serial number (I can attest by using Linux native commands and verify it's the same number). -- 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. 4, 2026