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

[Bug 60163] New: AutoCAD 2007 LT - Installation ended prematurely because of an error
by WineHQ Bugzilla Aug. 14, 2026

Aug. 14, 2026

http://bugs.winehq.org/show_bug.cgi?id=60163 Bug ID: 60163 Summary: AutoCAD 2007 LT - Installation ended prematurely because of an error Product: Wine Version: 11.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)list.winehq.org Reporter: kyle.kcsoftwares(a)gmail.com Target Milestone: --- Distribution: --- Created attachment 81794 --> http://bugs.winehq.org/attachment.cgi?id=81794 Error message AutoCAD 2007 LT https://archive.org/details/cd-1_20230515_202305 Fails with "Installation ended prematurely because of an 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.

1 5

[Bug 55233] New: A-Train PC Classic - UI is incorrectly sized and cannot switch between selected windows.
by WineHQ Bugzilla Aug. 14, 2026

Aug. 14, 2026

https://bugs.winehq.org/show_bug.cgi?id=55233 Bug ID: 55233 Summary: A-Train PC Classic - UI is incorrectly sized and cannot switch between selected windows. Product: Wine Version: 8.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: hibbsncc1701(a)gmail.com Distribution: --- The UI windows in A-Train PC Classic are unusable. Note: This game was ported from the Nintendo 3DS, and most / all of it's UI is intact. "UI windows" are essentially the game's menu / dialog box interface. (Called "windows" here as that's what the game's configuration INI file calls them.) Attempting to start a new game the first time causes each window to fill the entire application window and draw on top of each other. With only the top most window receiving user input. For the second attempt to start a new game, the windows are correctly sized / placed but only the most recently drawn window accepts user input with no way to switch to an inactive window. This breaks the game as the first requirement of the player is to use an inactive window's "Enter Company Name" button. The game's configuration INI file contains options for setting each window's origin X/Y coordinates, width and height. However editing these values manually seems to result in a deadlock. With the game continuing to update the application window (minimize / partial hide / etc.) but otherwise refusing user input after showing the company logos. Attempting to use a known good configuration file from Windows also doesn't work. As the game seemingly ignores it with no visible window behavior change from when starting a new game. As described above. -- 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 53561] New: Command and Conquer 3 Kane's Wrath Installer fails during component selection.
by WineHQ Bugzilla Aug. 14, 2026

Aug. 14, 2026

https://bugs.winehq.org/show_bug.cgi?id=53561 Bug ID: 53561 Summary: Command and Conquer 3 Kane's Wrath Installer fails during component selection. 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: hibbsncc1701(a)gmail.com Distribution: --- Created attachment 72925 --> https://bugs.winehq.org/attachment.cgi?id=72925 +msi log of CNC3 Kane's Wrath install attempt. When installing the game in Advanced install type mode (to change the destination install directory) the installer fails to continue past the component selection screen, displaying the error: "At least one language pack must be selected" The default component selection includes the language pack, and even deselecting and re-selecting it does not fix the error. Making the installer unable to proceed. This can be worked around by using the "Recommended" install type, but that means the user must manually change the game's installation directory after the game is installed. It should also be noted that changing the install directory causes the installer to display "_BrowseProperty" as the selected path after closing the folder selection dialog. The original game Command and Conquer 3 also has the same installer bug. An +msi log is attached. -- 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 7

[Bug 60121] New: Multi Theft Auto serial validation error
by WineHQ Bugzilla Aug. 13, 2026

Aug. 13, 2026

http://bugs.winehq.org/show_bug.cgi?id=60121 Bug ID: 60121 Summary: Multi Theft Auto serial validation error Product: Wine Version: 11.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: EpicTux123(a)proton.me Target Milestone: --- Distribution: --- Created attachment 81684 --> http://bugs.winehq.org/attachment.cgi?id=81684 80 mb log file from me # THE ISSUE There exists a modification for the game "Grand Theft Auto: San Andreas" called "Multi Theft Auto", available online at https://multitheftauto.com/ . It makes it possible to play the game online with others, something that the original game does not have the possibility to. Some bad actors, however, sometimes use cheat like god mode, infinite money and so on. To fix it, the developers ban such bad actors, but to avoid the bad actors from simply creating a new account and using a VPN (ban evasion), they also uniquely register the device serial based on the unique identifiers of hardware components, but mainly the storage device, be it a SATA HDD or a NVME SSD. This is their anti-cheat/anti-device spoofing system, which is proprietary. The rest of the code is open-source, available at https://github.com/multitheftauto/mtasa-blue , but the relevant code for this issue is a proprietary network module. Wine apparently fails at getting such serial from the Linux system, resulting in the app not working as expected and closing with serial validation error. On Windows, it works as expected, be it with any type of storage (filesystem is always NTFS, in this case). # THE DEVELOPERS' RECOMMENDATIONS https://help.multitheftauto.com/sa/trouble/serial-validation/#-linux To fix the issue, the developers recommend running the native Linux server binary (server, not client) to then generate such serial IDs automagically and keep them in sync with the client (the mod's client is Windows-only, but can work via Wine). It requires root in order to read some system paths. However, that has not been successful for me. Apparently, after running the server, there is supposed to be an automatic magic communication between the Linux server -> MTA client (the latter being via Wine, and the former being Linux native), but it did not happen in my case, even without sandboxing. # THE INCONSISTENCIES It is a gamble; 50% of people get it to work, and 50% do not, and the latter is my case. I asked one of the Multi Theft Auto developers if their anti-device spoofing mechanism discriminates against device type or if it really only cares about the serial being valid. The latter is the answer: it only cares about serial numbers. # A WEIRD WORKAROUND Some people in the community have found that if you plug in a SATA drive such as a USB stick or external SATA HDD, the serial validation works as expected, but that has not been my case; it was still not working. This is not relevant either, because on Windows it works with a single NVME-only device without any issues, but I am mentioning it because some people have found it to work with that. It is something related to not having certain types of storage/disks; see https://wiki.multitheftauto.com/wiki/Client_on_Linux_Manual#Known_issues:~:… for a community explanation (that page is somewhat outdated, but the part I linked may be relevant for the information it gives). The workaround did not work for me. So, I dug further into what is the problem. # WMI: THE POTENTIAL PROBLEM In https://github.com/multitheftauto/mtasa-blue/issues/4097 such issue is discussed at length, but what has been its main subject is the talk about Windows Management Instrumentation (WMI) and how Wine exposes storage devices and their IDs to the app. The main comment is this one https://github.com/multitheftauto/mtasa-blue/issues/4097#issuecomment-42591… (please read it starting from there as it has relevant information), talking about how the issue happens. The person there also made a small program to replicate how Wine gets the serial for the app ( https://github.com/Zephkek/serial_test ), trying to replicate the query from Wine. # TO REPRODUCE THE ISSUE 1. Buy a copy of the game GTA SA. See https://wiki.multitheftauto.com/wiki/Where_to_buy_GTASA for details. (Note: the game is abandonware. To buy it, you have to buy the full new trilogy as well, but de-listed version also exists on Steam if you had it earlier, or in the high seas if you want to search there). 2. Acquire the modification, MTA, at https://multitheftauto.com/ (main Download button, Win10 version), at no cost. 3. Create a clean Wine prefix (note: in my case it was Wine from Arch Linux with WOW64 enabled), with those verbs installed from winetricks: allfonts fontsmooth=rgb d3dx9_42 d3dcompiler_42 d3dcompiler_43 d3dcompiler_47 (needed to avoid launch issues). 4. Run the mod installer inside the Wine prefix. Uncheck everything in the installer except for "Game client" (do not check what cannot be unchecked, of course). 5. Do not change default mod install directory. 6. Change game directory to your copy of GTA SA (can be in your /home outside the prefix, no problem). If the copy is not version 1.0, MTA will automatically downgrade it to v1.0 (Steam is v3.0, for example). 7. After installing, open the game with its wineprefix. Mod's EXE is located in "C:/Program Files (x86)/MTA San Andreas 1.6/Multi Theft Auto.exe". 8. If it gives you warn about anti-virus, check the checkbox and proceed (you can safely ignore it). 9. Game opens to the main menu, and after 10 seconds exists with invalid serial error. Tip: run the mod with WINEDEBUG="+wmic,+wbemprox,+mountmgr,+volume,+file" for debug. I am not entirely sure the case is WMI but that is my best guess at the moment. # SYSTEM INFORMATION I am able to reproduce this issue with the following system: Operating System: Arch Linux KDE Plasma Version: 6.7.3 KDE Frameworks Version: 6.28.0 Qt Version: 6.11.1 Kernel Version: 7.1.5-arch1-2 (64-bit) Graphics Platform: Wayland Package "wine" from Arch Linux official repository. Version "11.14-2". ("wine-mono" and "wine-gecko" packages also installed, but probably not relevant.) System with only one NVME SSD installed and nothing else. I also attached a log file from my test of the problem with the same debug flags I recommended earlier. -- 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 11

[Bug 51318] New: MSOffice 2010 - context menu either does not appear or appears in top-left hand corner
by WineHQ Bugzilla Aug. 13, 2026

Aug. 13, 2026

https://bugs.winehq.org/show_bug.cgi?id=51318 Bug ID: 51318 Summary: MSOffice 2010 - context menu either does not appear or appears in top-left hand corner Product: Wine Version: 6.0.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: poprocks(a)gmail.com Distribution: --- I am running Slackware64-current. I have encountered a bug with MSOffice 2010 (Word and Excel, at least) whereby right-clicking either does not work at all (typically if no text is highlighted) or the context menu appears, but in the top-left-hand corner of the screen as opposed to at the mouse cursor. I have reproduced this on WINE 6.0.1 and 6.1. I can reproduce on Plasma5 and fluxbox. It does not occur on WINE 4.0 or 4.0.4. Possible regression? -- 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 3

[Bug 58145] New: Out of Ctrl 1.2: game doesn't launch, gives error
by WineHQ Bugzilla Aug. 13, 2026

Aug. 13, 2026

http://bugs.winehq.org/show_bug.cgi?id=58145 Bug ID: 58145 Summary: Out of Ctrl 1.2: game doesn't launch, gives error Product: Wine Version: 10.6 Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cemer99797(a)isorax.com Created attachment 78425 --> http://bugs.winehq.org/attachment.cgi?id=78425 Wine-devel 10.6 terminal log The game Out of Ctrl 1.2 doesn't launch and gives the following error in a pop-up window on launch: Error Failed to initialize player Details: Failed to initialize graphics. Make sure you have DirectX 11 installed, have up to date drivers for your graphics card and have not disabled 3D acceleration in display settings. InitializeEngineGraphics failed tested using Gcenx's wine-devel 10.6 build (https://github.com/Gcenx/macOS_Wine_builds/releases/tag/10.6) with GStreamer 1.26.0 download link (20 MB) (choose "OutOfCtrl_v1_2_EXE.zip"): https://miknugget.itch.io/out-of-ctrl shas256: 5d26c746c4e85b98af2f1f9fb4a4daeed837deb49427bf108935545f8958dba9 I'm using macOS 11 -- 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 27

[Bug 56350] New: Python programs fail to play sound
by WineHQ Bugzilla Aug. 13, 2026

Aug. 13, 2026

https://bugs.winehq.org/show_bug.cgi?id=56350 Bug ID: 56350 Summary: Python programs fail to play sound Product: Wine Version: 9.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: crypt32 Assignee: wine-bugs(a)winehq.org Reporter: galacticaledge(a)protonmail.com Distribution: --- Created attachment 76076 --> https://bugs.winehq.org/attachment.cgi?id=76076 Most of the errors that occur when trying to play a sound seems to be related to the crypt API Python programs fail to play any sound due to errors in the crypt library. If anyone wants to conveniently test and debug this issue, I wrote a simply Python program for this. Simply run the program, open a txt file (which the program will convert each line into speech when the "Next Line" button is played), and watch it fail to play sound and cause the "Next Line" button to stop working until a new file is selected. I have also confirmed this is a Wine issue since the program works perfectly fine on a Windows install. https://drive.google.com/file/d/1RjB0n5tAP1-7xPUf8Zjk_QzIyya7vZ6e/view?usp=… -- 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 9

[Bug 60161] New: riched20: colour table entries using \ctint/\cshade or theme colour keywords are parsed as three entries, shifting all \cfN indices
by WineHQ Bugzilla Aug. 12, 2026

Aug. 12, 2026

http://bugs.winehq.org/show_bug.cgi?id=60161 Bug ID: 60161 Summary: riched20: colour table entries using \ctint/\cshade or theme colour keywords are parsed as three entries, shifting all \cfN indices Product: Wine Version: 11.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: richedit Assignee: wine-bugs(a)list.winehq.org Reporter: wehrwolfmann(a)gmail.com Target Milestone: --- Distribution: --- Created attachment 81788 --> http://bugs.winehq.org/attachment.cgi?id=81788 inimal reproducer: three RTF colour tables that must render identically. Wine's RTF reader only accepts \red, \green and \blue inside \colortbl. Any other control word that the RTF specification allows in a colour table entry -- \ctint, \cshade and the theme colour keywords \cmaindarkone, \cmainlightone, \caccentone ... -- is not recognised, so ReadColorTbl() terminates the entry early, emits "err:richedit:ReadColorTbl malformed entry", and starts a *new* colour entry at the next token. Consequences: 1. One source entry turns into several colour table entries, so every \cfN in the document afterwards selects the wrong colour. 2. The bogus entries are created with rtfCRed/CGreen/CBlue = -1, i.e. "use the default colour", so the affected text ends up with CFE_AUTOCOLOR instead of the colour the document asked for. The relevant code is dlls/riched20/reader.c, ReadColorTbl(): if (!RTFCheckCM (info, rtfControl, rtfColorName)) cp->rtfCRed = cp->rtfCGreen = cp->rtfCBlue = -1; else { ... do { switch (info->rtfMinor) { case rtfRed: ... case rtfGreen: ... case rtfBlue: ... } RTFGetToken (info); } while (RTFCheckCM (info, rtfControl, rtfColorName)); } if (info->rtfClass == rtfEOF) break; if (!RTFCheckCM (info, rtfText, ';')) ERR ("malformed entry\n"); The keyword table in the same file (lines 1847-1849 of current master) knows exactly three colour table keywords: { rtfColorName, rtfRed, "red", 0 }, { rtfColorName, rtfGreen, "green", 0 }, { rtfColorName, rtfBlue, "blue", 0 }, \ctint, \cshade and the theme colour keywords do not appear anywhere in reader.c, so they are classified as unknown control words and break the entry apart. This is not a corner case: it is the shape Word (2007 and newer) and WordPad write for any document that uses theme colours, and it is what Inno Setup installers ship as their licence text. It is the likely cause of the long-standing "err:richedit:ReadColorTbl malformed entry" messages, e.g. in bug 20482. STEPS TO REPRODUCE Build and run the attached riched_colortbl.c (x86_64-w64-mingw32-gcc riched_colortbl.c -o riched_colortbl.exe -lgdi32 -luser32). It streams three RTF documents into a RichEdit 2.0 control with EM_STREAMIN and then reads the effective text colour of the single character back with EM_GETCHARFORMAT. All three documents request the same colour -- pure red -- and per the RTF specification must render identically: A {\rtf1\ansi\deff0{\fonttbl{\f0 Arial;}} {\colortbl;\red255\green0\blue0;}\cf1 X\par} B {\rtf1\ansi\deff0{\fonttbl{\f0 Arial;}} {\colortbl;\ctint255\cshade255\red255\green0\blue0;}\cf1 X\par} C {\rtf1\ansi\deff0{\fonttbl{\f0 Arial;}} {\colortbl;\red0\green0\blue0; \cmaindarkone\ctint255\cshade255\red255\green0\blue0;}\cf2 X\par} CURRENT BEHAVIOUR (wine-11.15, 64-bit, clean prefix, no overrides) expected for every line: crTextColor=0x0000ff (R=255 G=0 B=0) A plain colortbl stream error=0 textlen=1 effects=0x04000001 crTextColor=0x0000ff (R=255 G=0 B=0) B \ctint\cshade stream error=0 textlen=1 effects=0x44000001 crTextColor=0x007fff (R=255 G=127 B=0) [CFE_AUTOCOLOR] C Word theme colour stream error=0 textlen=1 effects=0x44000001 crTextColor=0x007fff (R=255 G=127 B=0) [CFE_AUTOCOLOR] with WINEDEBUG=+richedit: err:richedit:ReadColorTbl malformed entry (5x for the three documents) EXPECTED BEHAVIOUR All three lines report crTextColor=0x0000ff without CFE_AUTOCOLOR, and no "malformed entry" message is printed: \ctint, \cshade and the theme colour keywords are part of a single colour table entry and do not create entries of their own. SUGGESTED FIX Add the missing colour table keywords to the keyword table in dlls/riched20/reader.c and skip them in ReadColorTbl() instead of terminating the entry: * \ctintN and \cshadeN (tint/shade applied to the following \red\green\blue) * the theme colour keywords \cmaindarkone, \cmainlightone, \cmaindarktwo, \cmainlighttwo, \caccentone ... \caccentsix, \chyperlink, \cfollowedhyperlink, \cbackgroundone, \cbackgroundtwo, \ctextone, \ctexttwo Only the following \red/\green/\blue values need to be stored; the tint/shade factors and the theme name do not change which colour the entry resolves to for the purposes of \cfN lookup. -- 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 55685] New: FlatOut 2 crashes due to HLSL syntax error 'unexpected NEW_IDENTIFIER'
by WineHQ Bugzilla Aug. 12, 2026

Aug. 12, 2026

https://bugs.winehq.org/show_bug.cgi?id=55685 Bug ID: 55685 Summary: FlatOut 2 crashes due to HLSL syntax error 'unexpected NEW_IDENTIFIER' Product: vkd3d Version: 1.9 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: hlsl Assignee: wine-bugs(a)winehq.org Reporter: gijsvrm(a)gmail.com Distribution: --- Created attachment 75206 --> https://bugs.winehq.org/attachment.cgi?id=75206 log + shader 0024:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4. 0024:err:d3dcompiler:D3DCompile2 Shader log: 0024:err:d3dcompiler:D3DCompile2 <anonymous>:11:1: E5000: syntax error, unexpected NEW_IDENTIFIER 0024:err:d3dcompiler:D3DCompile2 Attached is an archive including a vkd3d & +d3dcompiler log and the relevant dumped shader. This might be related to bug 54872, but I'm not sure. -- 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

[Bug 50382] New: Lego Star Wars Saga needs native d3dcompiler_47
by WineHQ Bugzilla Aug. 12, 2026

Aug. 12, 2026

https://bugs.winehq.org/show_bug.cgi?id=50382 Bug ID: 50382 Summary: Lego Star Wars Saga needs native d3dcompiler_47 Product: Wine Version: 6.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d-util Assignee: wine-bugs(a)winehq.org Reporter: j-r(a)online.de Distribution: --- After installing Lego Star Wars Saga (GOG version) into a fresh 32 bit prefix, the game starts up fine including sound and controls, but with the exception of backgrounds and some effects nothing (logo, menu, in game characters etc) is displayed or replaced by grey boxes. winetricks d3dcompiler_47 fixes that problem. (An older App DB report using wine 3.3 mentions the same problem and fixing it by installing d3d9.) There is no console output indicating a problem in that area (recreating the test with wine 3.3 gives plenty of d3dcompiler error messages; perhaps they have been silenced since then?). Since the other d3dcompiler related bugs I checked all seemed to have d3dcompiler error messages I opened this new report, though it very likely still is a duplicate. Please advise which debug channels to turn on to generate a useful log. -- 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 24