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

[Bug 59767] New: loader/wine.desktop enables programs to escape Flatpak sandboxes in many if not most situations
by WineHQ Bugzilla July 5, 2026

July 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=59767 Bug ID: 59767 Summary: loader/wine.desktop enables programs to escape Flatpak sandboxes in many if not most situations Product: Wine Version: 11.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: loader Assignee: wine-bugs(a)list.winehq.org Reporter: arraybolt3(a)gmail.com Distribution: --- This is kind of a weird bug as it doesn't have anything to do with Windows applications in particular, but rather with how Wine registers itself with the system. loader/wine.desktop registers Wine as a MIME handler for a number of different Windows-related executable file formats (EXEs, MSIs, and Batch files. Linux doesn't recognize these files as programs (unless they have their executable bit set and are registered with binfmt-misc of course), so it will attempt to "open" these files with Wine. Wine will then run arbitrary code within these programs with the privileges of whatever program launched Wine. On the surface, this doesn't sound like a problem, but it becomes an issue because sandboxed code under Linux can usually use D-Bus to open files in their default application *outside of the sandbox*. Since the default application to open EXE files in is Wine, anything that can open arbitrary files outside of the sandbox can now escape the sandbox by writing an EXE file somewhere and then "opening" it with Wine. There are two ways I know of to do this: * Some file managers handle the org.freedesktop.FileManager1.ShowFolders method call by opening the "folders" they are told to open with their default application. Of course, there is no guarantee that the "folders" actually are folders; if the sandboxed app passes a file name in this call, those file managers will open the specified files in their default application. If Wine is installed, and one of the "folders" specified is an EXE file, the application can now run arbitrary code outside of the sandbox. (I reported this bug to an affected file manager over 90 days ago.) * xdg-desktop-portal-gtk intentionally allows applications to open arbitrary files outside of a sandbox, via the org.freedesktop.portal.OpenURI.OpenFile D-Bus method. If there are multiple applications that can open the same file type, it will usually open a dialog asking what application to open the file in, but if there is only one handler for a file type on the system, it will immediately open the file with its default handler. Handlers for EXE files other than Wine are relatively rare (lxqt-archiver is one, oddly enough), so there is a very good chance that a sandboxed app can just write an EXE file to the disk, then open it with xdg-desktop-portal-gtk and have code execution outside the sandbox. (I reported this privately to the Flatpak developers over 90 days ago.) Arguably, neither of these issues are security vulnerabilities in xdg-desktop-portal or file managers. The `xdg-mime` manpage warns: Security Note: Never set a handler that will blindly execute code or commands from the file being handled. Such behavior will sooner than later lead to unintended code execution i.e. through a curious user trying to inspect a freshly downloaded file but running it by accident. Keeping opening and executing separate actions helps with people protecting themselves from malware, the default handler is an opener, not a runner. Therefore I believe this is an issue with Wine. -- 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 24

[Bug 59129] New: Parallel Port Tester fails to detect the parallel port's base I/O address
by WineHQ Bugzilla July 5, 2026

July 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=59129 Bug ID: 59129 Summary: Parallel Port Tester fails to detect the parallel port's base I/O address Product: Wine Version: 11.0-rc1 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: wmi&wbemprox Assignee: wine-bugs(a)list.winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Steps to reproduce: 1. Use a computer with a motherboard-attached or PCI-attached parallel port. USB-attached parallel ports do not have base I/O addresses and Parallel Port Tester ignores them. 2. Ensure that /dev/lp0 exists and works outside of Wine, for example by connecting the parallel port to a printer or to an LED tester, running `echo hello > /dev/lp0`, and seeing the word printed on the printer or seeing different LEDs light up on the tester. 3. (Optional) Figure out what the base address of the parallel port is by looking at DEVNAME in /sys/class/printer/lp0/device/ppdev/parport0/uevent, then reading the first number in /proc/sys/dev/parport/<DEVNAME>/base-addr. You will need to convert the value to hexadecimal and prepend "0x" if you want to manually enter it into Parallel Port Tester. 4. Run `wine ParallelPortTesterSetup-1.0.0.2.exe` 5. Run `wine 'C:\Program Files (x86)\Parallel Port Tester\ParallelPortTester.exe'` 6. Click the drop-down labeled "Port" in the lower-right corner of the window. When my desktop computer is booted into Windows and I click the drop-down in Parallel Port Tester, it offers "LPT3 (0xEFF8)" as an option. When the same computer is booted into Linux and I run Parallel Port Tester on Wine, the drop-down is empty. However, if I run it on Wine with https://gitlab.com/alexhenrie/ioperm and enter the parallel port's base address manually, the program correctly displays the states of the parallel port's pins and can manipulate them. That means that the main part of the program works, it's just failing to automatically detect the port. The author helpfully wrote up an explanation of what the program does to find parallel ports and their base addresses: https://www.downtowndougbrown.com/2014/11/detecting-parallel-ports-and-thei… $ sha256sum ParallelPortTesterSetup-1.0.0.2.exe 9e9b399dd92ac48433af2061eb8491d1d68a6134eaeab2efcdcd36361e723d09 -- 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 44920] New: Starcraft II Arcade Crash during load
by wine-bugs＠winehq.org July 5, 2026

July 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=44920 Bug ID: 44920 Summary: Starcraft II Arcade Crash during load Product: Wine Version: 3.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: antonio.e.russo(a)gmail.com Distribution: --- Created attachment 61011 --> https://bugs.winehq.org/attachment.cgi?id=61011 WINEDEBUG=warn+all log of crash (gzipped) Starcraft II is a moving target. After the most recent patch, I was unable to use wine-staging 2.21, which had been working excellently for me. Wine 3.5 has trouble: loading the "Hero Attack 3X" (popular) arcade game, the game crashes. I've attached a "WINEDEBUG=warn+all" log, and can help debug. I checked "use 32-bit version", and I am using a clean prefix. -- 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.

4 26

[Bug 26011] New: BitLocker.exe not working with wine
by wine-bugs＠winehq.org July 5, 2026

July 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=26011 Summary: BitLocker.exe not working with wine Product: Wine Version: 1.3.13 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: paloseco(a)gmail.com Created an attachment (id=33174) --> (http://bugs.winehq.org/attachment.cgi?id=33174) Log of the BitLocker.exe errors when trying to load USB Removable BitLocker.exe is a tool for reading/writing partitions or USB removable media encrypted with the BitLocker application included with Windows 7 Ultimate (similar to TrueCrypt). The pendrives encrypted include the portable application to read/write from windows xp platform. >From winecfg I've created a new drive pointing to the folder where the USB Removable is mounted, but doesn't work due to unimplemented features. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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 39303] New: Cannot copy schematics between different windows / ltspice
by wine-bugs＠winehq.org July 4, 2026

July 4, 2026

https://bugs.winehq.org/show_bug.cgi?id=39303 Bug ID: 39303 Summary: Cannot copy schematics between different windows / ltspice Product: Wine Version: 1.7.51 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dieter.jurzitza(a)t-online.de Distribution: --- Trying to copy parts or an entire schematic between two schematics in two windows from within ltspice does not work. I can easily select components to copy, I can copy them within one single schematic, but I cannot copy them between two different schematics in a single ltspice instance (what works without issues using plain windows, but who is using plain windows :-)) Thank you for looking into this, take care Dieter Jurzitza -- 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 56726] New: Ability to disable wine builtin title bar and borders
by WineHQ Bugzilla July 4, 2026

July 4, 2026

https://bugs.winehq.org/show_bug.cgi?id=56726 Bug ID: 56726 Summary: Ability to disable wine builtin title bar and borders Product: Wine Version: 9.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: Deresiant(a)protonmail.ch Distribution: --- Currently when running applications through wine on the wayland driver, those windows have a titlebar and border (I think these called window decorations?) which are provided by wine and can be configured in winecfg. There isn't a method to disable these window decorations completely. -- 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 59296] New: Installed Adobe InDesign CS5.5 with no issue, but program crashes right after starting, attaching file with details.
by WineHQ Bugzilla July 2, 2026

July 2, 2026

http://bugs.winehq.org/show_bug.cgi?id=59296 Bug ID: 59296 Summary: Installed Adobe InDesign CS5.5 with no issue, but program crashes right after starting, attaching file with details. Product: Wine Version: 11.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: rucafiorio(a)proton.me Distribution: --- Created attachment 80234 --> http://bugs.winehq.org/attachment.cgi?id=80234 Error details Adobe Photoshop 5,1 works fine, fyi. -- 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 9

[Bug 59745] New: Wine crashes when a custom window is created to show information
by WineHQ Bugzilla July 2, 2026

July 2, 2026

http://bugs.winehq.org/show_bug.cgi?id=59745 Bug ID: 59745 Summary: Wine crashes when a custom window is created to show information Product: Wine Version: 11.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: matthias0178+wine(a)gmail.com Distribution: --- Created attachment 80922 --> http://bugs.winehq.org/attachment.cgi?id=80922 Source code of the test program I created a program using C and the Windows API. This program was designed to create and display a specific window containing help text rendered via GDI. As soon as the user pressed any key on the keyboard or clicked with the mouse, the special window was supposed to be destroyed and the application terminated. Since this program functioned flawlessly on Windows but crashed under Wine immediately after displaying and destroying the special window, I developed a small test program that demonstrates the bug. This test program logs to the command line what occurs when the same task is executed in a simplified manner. I have attached the source code for this tiny test program. You may copy, modify and distribute it without restrictions to the extent permitted by law. On the Debian 13 console, the console output is not the same as in the console of Windows 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.

1 13

[Bug 53812] New: Text does not show in Some APPs with native wine7.19
by WineHQ Bugzilla July 2, 2026

July 2, 2026

https://bugs.winehq.org/show_bug.cgi?id=53812 Bug ID: 53812 Summary: Text does not show in Some APPs with native wine7.19 Product: Wine Version: 7.19 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: 399989567(a)qq.com Distribution: --- Created attachment 73324 --> https://bugs.winehq.org/attachment.cgi?id=73324 how to reproduce problem I filed a bug(# Bug 53739) with the font display issue before, because I was doing some font replacements (seems to involve dwrite).This problem appears to be the same as the previous one, but it's not the same problem. This problem occurs in different sections of QQ, DingTalk, and corporate WeChat. For example, some fonts on the landing page of QQ are not displayed； some fonts are not displaye when sending a message on the meeting interface of corporate WeChat. Among them, the problem of QQ is the easiest to reproduce(even if you don't have an account, you can reproduce it), so I will use QQ to explain the problem below. 「Problem Description In general」—— use native unmodified wine In general, the font of QQ can be displayed normally on my virtual machine, but it cannot be displayed normally on my physical machine，with the same Language Environment and System installation scene > $ echo LANG = zh_CN.UTF-8 > System installation scene：debian-live-11.4.0-amd64-kde.iso > System installation scene download URL:https://drive.google.com/file/d/14FJVpGkLNTJrDlU9SQW38eSIFlr_qjUB/view?… 「The machine I use」 M1: "physical machine" debian-11.4.0-KDE M2: "virtual machine" debian-11.4.0-KDE 「 Problem Description 」 I just downloaded the source code of wine 7.19 and make it. I click to add an account, the font display of QQ fails on M1, but successed on M2. By use WINEDEBUG=+relay,I find when text show on M2, APPs called API:ScriptTextOut,and then text show successed. But on M1, APPs called API:ExtTextOutW, and then text show fails. I just started to suspect that QQ has different versions installed on different machines, so I packaged all the files of QQ installed on the virtual machine into a zip file, and then took this file to the physical machine to run, but the text still cannot be show on the physical machine. I don't know why QQ calls different APIs on the physical machine and the virtual machine to output text, so I'm asking for your help. What channel should I use to check my environment？nls?locale? 「Reproduce Problem」 The picture(how_to_..._proble,.png) shows the operation process QQ downloardURL:https://im.qq.com/download QQ Version:9.6.7 -- 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 14

[Bug 39006] New: ISAXAttributes.getLocalName should only return an empty string for namespace attributes that are not xmlns
by wine-bugs＠winehq.org July 2, 2026

July 2, 2026

https://bugs.winehq.org/show_bug.cgi?id=39006 Bug ID: 39006 Summary: ISAXAttributes.getLocalName should only return an empty string for namespace attributes that are not xmlns Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: msxml3 Assignee: wine-bugs(a)winehq.org Reporter: ott(a)mirix.org Distribution: --- According to the specification the local name if a namespace propery is only an empty string if it is exactly "xmlns": "For "xmlns", this value is empty." (https://msdn.microsoft.com/en-us/library/ms757865%28v=vs.85%29.aspx) This makes sense because it would be impossible to get the namespace prefix otherwise. -- 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 2