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

[Bug 59774] New: Age of Empires III: The Asian Dynasties crashes in the beginning cinematics
by WineHQ Bugzilla May 29, 2026

May 29, 2026

http://bugs.winehq.org/show_bug.cgi?id=59774 Bug ID: 59774 Summary: Age of Empires III: The Asian Dynasties crashes in the beginning cinematics Product: Wine Version: 11.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: scottkidman(a)protonmail.com Distribution: Mint Created attachment 80983 --> http://bugs.winehq.org/attachment.cgi?id=80983 Output for Age of Empires III: The Asian Dynasties When the game starts, and is in the process of showing the video clips, it crashes and then shows the message dialogue "Initialisation failed." Attached is the output. I am running Linux Mint 22.3 and the game is the original early 2000s CD-ROM versions. Further more, I did use Winetricks to integrate d3dx9, directplay,and l3codecx so as to accommodate for other games in the prefix. I tried the older expansion Warchiefs and that crashed as well. A regression test will be available for the asking. -- 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 14

[Bug 59522] New: explorerframe: ITaskbarList3 SetProgressValue/SetProgressState stubs - could use native desktop backends
by WineHQ Bugzilla May 29, 2026

May 29, 2026

http://bugs.winehq.org/show_bug.cgi?id=59522 Bug ID: 59522 Summary: explorerframe: ITaskbarList3 SetProgressValue/SetProgressState stubs - could use native desktop backends Product: Wine Version: 11.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: explorerframe Assignee: wine-bugs(a)list.winehq.org Reporter: Robert-Gerigk(a)online.de Distribution: --- ITaskbarList3::SetProgressValue() and SetProgressState() in dlls/explorerframe/taskbarlist.c are currently stubs (FIXME + return S_OK). This causes Issues with .NET/WPF applications that use the Windows 7+ taskbar progress API. Some appplications (e.g. WPF apps using TaskbarItemInfo) deadlock or behave incorrectly when the COM call chain around these methods interacts with the UI thread. Wine already implements plattform-specific desktop integration in several places: - macOS: Full Cocoa integration (NSStatusBar, NSDockTile) in winemac.drv - X11: EWMH hints including _NET_WM_STATE_DEMANDS_ATTENTION in winex11.drv - Wayland: xdg-toplevel-icon-v1 protocol in winewayland.drv - DBus: Production clients for BlueZ and UDisks in winebth.sys and mountmgr.sys A natural Extension would be implementing taskbar progress via the com.canonical.Unity.LauncherEntry DBus interface, wich is supported by KDE Plasma, GNOME, and other Linux desktop environments. Firefox and LibreOffice already use this interface for native taskbar progress. Proposed mapping: TBPF_NOPROGRESS -> progress-visible: false TBPF_NORMAL -> progress-visible: true, progress: value TBPF_INDETERMINATE -> progress-visible: true, progress: 0.0 TBPF_ERROR -> urgent: true TBPF_PAUSED -> progress-visible: true (no direct equivalent) The implementation would follow the existing DBus pattern from mountmgr.sys/dbus.c (dlopen/dlsym, graceful degradation when libdbus-1 is unavailable). I'd be willing to work on a Linux/DBus patch if there's interest. Looking for feedback on: 1. Is this the right component (explorerframe) or should this be handled in the platform drivers (winex11.drv, winewayland.drv)? 2. How should the .desktop file association be resolved? (DBus needs an application:// URI) 3. Any concerns about adding a libdbus-1 dependency to explorerframe? I'm currently working on getting KNX ETS 6.4 (a .NET/WPF application) running under Wine and ran into several issues along teh way, this being one of them. The application uses TaskbarItemInfo for progress display wich leads to Problems in the COM/UI thread interaction. ETS 6.4 does run on Linux now, but only trough launch scripts, .dll patches, registry workarounds, and a heavily patched Wine prefix (winetricks dotnet48 + manual fixes) - it would be great to reduce those workarounds over time. I am mostly a solo devloper with an electrical engineering background and fairly new to collaborative development on Gitlab/GitHub, so I'd appreciate any Guidance on the right approach for this - happy to learn. -- 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 12

[Bug 57329] New: Desktop files generated by Wine do not conform to the Desktop Entry Specification
by WineHQ Bugzilla May 29, 2026

May 29, 2026

https://bugs.winehq.org/show_bug.cgi?id=57329 Bug ID: 57329 Summary: Desktop files generated by Wine do not conform to the Desktop Entry Specification Product: Wine Version: 9.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: meator.dev(a)gmail.com Distribution: --- Desktop files generated by Wine do not conform to the latest (and older) version to of the Desktop Entry Specification, primarily the Exec key specification: https://specifications.freedesktop.org/desktop-entry-spec/1.5/exec-variable… For example, this is how the desktop file for Notepad++ looks like (located at /home/meator/.local/share/applications/wine/Programs/Notepad++.desktop): [Desktop Entry] Name=Notepad++ Exec=env WINEPREFIX="/home/meator/.wine" wine C:\\\\ProgramData\\\\Microsoft\\\\Windows\\\\Start\\ Menu\\\\Programs\\\\Notepad++.lnk Type=Application StartupNotify=true Path=/home/meator/.wine/dosdevices/c:/Program Files/Notepad++ Icon=7ABC_notepad++.0 StartupWMClass=notepad++.exe I will ignore the `env WINEPREFIX="/home/meator/.wine"` part of Exec now. The Exec key parsing is done in two rounds (that's why there are so many backslashes). The first round is common to all keys of type string, localestring and iconstring (which includes the Exec key). The standard mandates: > The escape sequences \s, \n, \t, \r, and \\ are supported for values of type string, localestring and iconstring, meaning ASCII space, newline, tab, carriage return, and backslash, respectively. This is how the command line looks after undoing the first layer of escapes: > wine C:\\users\\meator\\AppData\\Roaming\\Microsoft\\Windows\\Start\ Menu\\Programs\\Microsoft\ Office\ PowerPoint\ Viewer\ 2003.lnk Then the Exec quoting continues. The standard mandates: > Quoting must be done by enclosing the argument between double quotes and escaping the double quote character, backtick character ("`"), dollar sign ("$") and backslash character ("\") by preceding it with an additional backslash character. Implementations must undo quoting before expanding field codes and before passing the argument to the executable program. Reserved characters are space (" "), tab, newline, double quote, single quote ("'"), backslash character ("\"), greater-than sign (">"), less-than sign ("<"), tilde ("~"), vertical bar ("|"), ampersand ("&"), semicolon (";"), dollar sign ("$"), asterisk ("*"), question mark ("?"), hash mark ("#"), parenthesis ("(") and (")") and backtick character ("`"). The first problem is that the second argument is not enclosed in double quotes, so all escapes in it are unspecified. The second problem is that `\ ` space escape is used, which is not specified (this is the most severe problem). It is specified as a "reserved character", but not as a character requiring a backslash escape. Because of these issues, fully conformant desktop file parsers will fail to parse desktop files generated by Wine. This is how a fixed Notepad++ desktop file looks like: [Desktop Entry] Name=Notepad++ Exec=env "WINEPREFIX=/home/meator/.wine" wine "C:\\\\ProgramData\\\\Microsoft\\\\Windows\\\\Start Menu\\\\Programs\\\\Notepad++.lnk" Type=Application StartupNotify=true Path=/home/meator/.wine/dosdevices/c:/Program Files/Notepad++ Icon=7ABC_notepad++.0 StartupWMClass=notepad++.exe I have also quoted `WINEPREFIX=/home/meator/.wine` in whole, because the entire argument should be quoted according to the standard (but I consider this issue to be less important). System info =========== OS: Void Linux Wine version: wine-9.20 (downloaded through package manager) Notepad++ download: https://github.com/notepad-plus-plus/notepad-plus-plus/releases/download/v8… -- 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 6

[Bug 49720] New: Family Tree Maker 2017 installer fails after numerous "fixme" console messages
by WineHQ Bugzilla May 29, 2026

May 29, 2026

https://bugs.winehq.org/show_bug.cgi?id=49720 Bug ID: 49720 Summary: Family Tree Maker 2017 installer fails after numerous "fixme" console messages Product: Wine Version: 5.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: andrewemt(a)hotmail.com Distribution: --- Created attachment 67981 --> https://bugs.winehq.org/attachment.cgi?id=67981 terminal output log from wine command-line invocation of FTMinstaller When trying to install a legal copy of Family Tree Maker 2017 on Fedora Core 31 (kernel 5.7.11-100.fc31.x86_64) using the Fedora distro's version of Wine 5.14, after getting most of the way through the install, after "copying files" (according to the install wizard), it suddenly stops and displays a dialog stating that the installation failed) after the terminal window that executed the wine command spews a series of fixme errors. Attached is the terminal window log showing all the fixme errors from Wine. The current working directory was my personal directory under drive_c/users, which is where I copied the Family Tree Maker install program FTM2017.EXE. The large gaps of blank lines in the log were me adding carriage returns in the terminal to separate different windows in the InstallShield wizard. The last clump appeared while the InstallShield file copy progress window was showing, followed by the installation failure window. -- 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 59539] New: Querying namespace nodes via XPath's namespace:: axis returns NULL for all nodes. selectSingleNode("namespace::prefix") returns S_FALSE/NULL and selectNodes("namespace::*") returns an empty list, even when the namespace is in scope.
by WineHQ Bugzilla May 29, 2026

May 29, 2026

http://bugs.winehq.org/show_bug.cgi?id=59539 Bug ID: 59539 Summary: Querying namespace nodes via XPath's namespace:: axis returns NULL for all nodes. selectSingleNode("namespace::prefix") returns S_FALSE/NULL and selectNodes("namespace::*") returns an empty list, even when the namespace is in scope. Product: Wine Version: 11.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msxml3 Assignee: wine-bugs(a)list.winehq.org Reporter: hkarlsson(a)gmail.com Distribution: --- When building chrome through wine it fails on some commands involving javascript. I've narrowed it down to a super simple tiny repro which works fine on windows but fails on wine. Here's the error on wine: 0128:err:msxml:create_node Called for unsupported node type 18 FAIL: node is null Create a test.js file that has this content: var doc = new ActiveXObject("Msxml2.DOMDocument.6.0"); doc.loadXML('<root xmlns:ns="http://example.com/ns"/>'); var node = doc.documentElement.selectSingleNode("namespace::ns"); WScript.Echo(node == null ? "FAIL: node is null" : "PASS: " + node.nodeName + "=" + node.nodeValue); Then run it with cscript.exe. On windows it returns: PASS: xmlns:ns=http://example.com/ns on wine it returns: FAIL: node is null -- 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 58887] New: Opening screen of Photolemur 3 has 'tofu' characters between letters on three lines
by WineHQ Bugzilla May 29, 2026

May 29, 2026

http://bugs.winehq.org/show_bug.cgi?id=58887 Bug ID: 58887 Summary: Opening screen of Photolemur 3 has 'tofu' characters between letters on three lines Product: Wine Version: 10.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: superian(a)gmail.com Distribution: --- Created attachment 79551 --> http://bugs.winehq.org/attachment.cgi?id=79551 Terminal output when running the program After installation, running Photolemur 3 version 1.1's opening screen has 'tofu' characters between letters on three lines. Adding a font to Wine's Windows/Font folder does not cure this. I cannot find a download link for the setup program, but I will keep looking. shasum256 Photolemur_3_Win_Setup.exe 4e185aa8358af73b1f0cdfd8d9709e0bbe7aceb20886577e923ebf19bb53d3c7 -- 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 23

[Bug 59555] New: Star Wars: Knights of the Old Republic - Rendering failure with active framebuffer effects
by WineHQ Bugzilla May 29, 2026

May 29, 2026

http://bugs.winehq.org/show_bug.cgi?id=59555 Bug ID: 59555 Summary: Star Wars: Knights of the Old Republic - Rendering failure with active framebuffer effects Product: Wine Version: 11.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: accounts.winehq(a)vv221.fr Distribution: --- Up to WINE 10.0, framebuffer effects could be enabled in Star Wars: Knights of the Old Republic with no adverse effect on rendering. With WINE 11.5 it leads to a failure to render the game world (including any geometry, models, etc.). Text dialogues and other 2D interface pieces can be seen, with some heavy flickering effect. When trying to take a screenshot I only get a solid black image, even when text dialogue could be seen on the actual game screen. The actual gameplay seems to work fine, this is almost certainly only a rendering error. I have not tested other WINE builds yet, but I am going to do that to get a better idea of where the regression is hiding. -- 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 56482] New: basically i tried running vocaloid 6 and it does not run and shows error
by WineHQ Bugzilla May 29, 2026

May 29, 2026

https://bugs.winehq.org/show_bug.cgi?id=56482 Bug ID: 56482 Summary: basically i tried running vocaloid 6 and it does not run and shows error Product: Wine Version: 9.3 Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: angad.ranhotra(a)gmail.com Created attachment 76252 --> https://bugs.winehq.org/attachment.cgi?id=76252 backtrace basically i tried running vocaloid 6 and it does not run and shows 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.

2 8

[Bug 43597] New: DaVinci Resolve 12.5.6 doesn't start
by wine-bugs＠winehq.org May 29, 2026

May 29, 2026

https://bugs.winehq.org/show_bug.cgi?id=43597 Bug ID: 43597 Summary: DaVinci Resolve 12.5.6 doesn't start Product: Wine Version: 2.15 Hardware: x86 URL: https://www.blackmagicdesign.com/products/davinciresol ve/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Created attachment 59011 --> https://bugs.winehq.org/attachment.cgi?id=59011 Console output Just finish the install, main program should be at "drive_c/Program Files (x86)/Blackmagic Design/DaVinci Resolve/Resolve.exe". When running, click "Skip tour" and then "Skip and start right now". Program closes after a failed assert. When running the file through the lnk file created on my desktop, the assert isn't there, but it still doesn't start. Tested with both wine-2.15 and wine-2.15 staging. Alternative link if you don't want to register: http://www.computerbild.de/download/DaVinci-Resolve-14604869.html (It's a german site, but just click the red download button, and then 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.

3 5

[Bug 48370] New: Virtual Magnifying Glass (Dynamic Mode) crashes on Mac OS X
by WineHQ Bugzilla May 29, 2026

May 29, 2026

https://bugs.winehq.org/show_bug.cgi?id=48370 Bug ID: 48370 Summary: Virtual Magnifying Glass (Dynamic Mode) crashes on Mac OS X Product: Wine Version: 5.0-rc2 Hardware: x86-64 URL: http://magnifier.sourceforge.net/ OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tobbi.bugs(a)googlemail.com Created attachment 66118 --> https://bugs.winehq.org/attachment.cgi?id=66118 crash information +++ This bug was initially created as a clone of Bug #48369 +++ $ openssl sha256 Vmg3.6_install.exe SHA256(Vmg3.6_install.exe)= 2a22bd41b07b0589880c1ac822ff89de274da050631e2571c0bd9da4697ffdf7 $ wine --version wine-5.0-rc2 Steps to reproduce: 1. Install Virtual Magnifying Glass and start it. 2. Click "Dynamic Mode". Results: Wine crashes. -- 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