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

[Bug 56860] New: Universal Audio Connect: Plugin / App downloads fails due to missing "tar" utility
by WineHQ Bugzilla July 19, 2026

July 19, 2026

https://bugs.winehq.org/show_bug.cgi?id=56860 Bug ID: 56860 Summary: Universal Audio Connect: Plugin / App downloads fails due to missing "tar" utility Product: Wine-staging Version: 9.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: eoinoneill1991(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Trying to debug why UA Connect didn't work on my wine installation, I think I found the source of my problem. Here's a log excerpt of the utility "UA Cloud Helper" which seems to be responsible for downloading and extracting applications. 17.33.39.205039(+2) AuthDownload(a)ERROR UAContextLowP BundleExtractionFailed('uaudio_polymax'): 'auth.download_extraction_tar_error' uaudio_polymax.lunacomponent/algo.bundle.tgz 17.33.39.205110(+70) AuthDownload(a)warn Main Auth_DownloadMgr::CancelDownload: id='uaudio_polymax' 17.33.39.219965(+14855) AuthDownload(a)ERROR Main ExtractAndStage - failed for uaudio_polymax 17.33.53.997567 AuthDownload(a)warn Main Auth_DownloadMgr::DownloadPlugin: id='uaudio_polymax', ver.='', disk path='' 17.33.55.334587 AuthDownload(a)ERROR UAContextLowP processTarExtract - 'tar' utility is not found! Process paths: "C:\windows\system32" "C:\windows" "C:\windows\system32\wbem" "C:\windows\system32\WindowsPowershell\v1.0" Basically, my understanding of this error is that the application cannot find an adequate "tar" extraction utility when checking the directories listed above. There might be a way around this if someone clever enough with wine can help direct me, but otherwise this might be a bug and could be related to issues people have had with other VST download utilities. -- 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 4

[Bug 45237] New: Dragon Naturally Speaking 15 fails to install with customactions error
by wine-bugs＠winehq.org July 19, 2026

July 19, 2026

https://bugs.winehq.org/show_bug.cgi?id=45237 Bug ID: 45237 Summary: Dragon Naturally Speaking 15 fails to install with customactions error Product: Wine Version: 3.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: susancragin(a)earthlink.net Distribution: --- Created attachment 61466 --> https://bugs.winehq.org/attachment.cgi?id=61466 backtrace Dragon Naturally Speaking 15 fails to install. What I did: NS15 needs the following: WMI, dotnet452, and Windows above 2003, preferably Windows 7. First I installed Windows PowerShell core using these directions: https://docs.microsoft.com/en-us/powershell/scripting/setup/installing-powe… Then I created a 64-bit wineprefix. Installed dotnet 452 using winetricks 452 installs but then sets the wine version to either XP or 2003, neither of which will run NS15. So... winecfg Windows 7 Then the installation works. It requests that powershell be activated, and that seems to work. It recognizes that the installed dotnet is inadequate, and installs its own. And then it starts to install the program. What makes this confusing is that Natspeak 12.5 also uses dotnet452, and the same things happen, but NS12.5 installs and runs fine. This is the first error message I got Expression: [mscorlib recursive resource lookup bug] Description: Infinite recursion during resource lookup within mscorlib. This may be a bug in mscorlib, or potentially in certain extensibility points such as assembly resolve elements or CultureInfo names. Resource name: ArgumentNull_Generic -- 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 9

[Bug 59210] New: Black textures in Kao the Kangaroo (2022)
by WineHQ Bugzilla July 19, 2026

July 19, 2026

http://bugs.winehq.org/show_bug.cgi?id=59210 Bug ID: 59210 Summary: Black textures in Kao the Kangaroo (2022) Product: Wine Version: 11.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: cweiske(a)cweiske.de Distribution: --- Created attachment 80104 --> http://bugs.winehq.org/attachment.cgi?id=80104 screenshot with black textures When playing "Kao the Kangaroo" (2022 version), many of the textures are black. The kangaroo itself is ok, the floor textures as well, but most of the environment has black textures. Graphics card is a SAPPHIRE AMD Radeon RX 7600 PULSE 8GB, running on Debian 12 with wine staging 11.0-rc4. I'm using version 1.6.0 bought from GOG: https://www.gog.com/de/game/kao_the_kangaroo_2022 -- 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 4

[Bug 55763] New: Electron projects using sudo-prompt think that permission was not granted
by WineHQ Bugzilla July 19, 2026

July 19, 2026

https://bugs.winehq.org/show_bug.cgi?id=55763 Bug ID: 55763 Summary: Electron projects using sudo-prompt think that permission was not granted Product: Wine Version: 8.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: skecthysites(a)gmail.com Distribution: --- Electron projects using sudo-prompt think that permission was not granted and behave as if the prompt was closed without granting permission. To reproduce: 1. Install wine-bug-demo from here: https://github.com/zurgeg/Wine-Bug/releases/tag/1.0.0 2. Extract linux-unpacked.tar.gz 3. Run wine-bug-demo 4. Note that it asks you for your user password 5. It will execute just fine once you enter your user password, then you can interrupt it 6. Install wine-bug-demo.Setup.1.0.0.exe 7. After installing, it will attempt to run, at which point it will crash with the error "User did not grant permission" -- 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 59308] New: PowerShell Execution Problem
by WineHQ Bugzilla July 19, 2026

July 19, 2026

http://bugs.winehq.org/show_bug.cgi?id=59308 Bug ID: 59308 Summary: PowerShell Execution Problem Product: Wine Version: unspecified Hardware: x86-64 OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)list.winehq.org Reporter: Alexander88207(a)Protonmail.com Hello, i have noticed that applications such as the Heroic Games Launcher are no longer functioning properly. (Last time it did was with Wine 9 Stable Release) Upon examining the console output, i observed that every command attempted results in the message: "0120:fixme:powershell:wmain argv". Moreover, i am unable to start PowerShell itself, as it only returns: 0120:fixme:powershell:wmain stub. 0120:fixme:powershell:wmain argv[0] L"C:\windows\system32\WindowsPowershell\v1.0\powershell.exe" I plan to perform a bisect analysis when i have more availability. Thanks. -- 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 2

[Bug 57542] New: Visual studio 2022 installer can't connect to the internet
by WineHQ Bugzilla July 19, 2026

July 19, 2026

https://bugs.winehq.org/show_bug.cgi?id=57542 Bug ID: 57542 Summary: Visual studio 2022 installer can't connect to the internet Product: Wine Version: 10.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: francisco278herrera(a)gmail.com Distribution: --- The installer for visual studio 2022 will open but it will not connect to the internet as it will say that nothing is available to install and there's nothing under developer news either. -- 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 25

[Bug 45480] New: LOUDPLAY: crashes when I launch application
by wine-bugs＠winehq.org July 19, 2026

July 19, 2026

https://bugs.winehq.org/show_bug.cgi?id=45480 Bug ID: 45480 Summary: LOUDPLAY: crashes when I launch application Product: Wine Version: 3.12 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mikhail.v.gavrilov(a)gmail.com Distribution: --- Created attachment 61835 --> https://bugs.winehq.org/attachment.cgi?id=61835 console logs $ wine --version wine-3.12 (Staging) -- 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 59682] New: Windrose server: UDP bind to specific IPv4 behaves like 0.0.0.0%iface, causing wrong source IP and multihoming conflicts
by WineHQ Bugzilla July 19, 2026

July 19, 2026

http://bugs.winehq.org/show_bug.cgi?id=59682 Bug ID: 59682 Summary: Windrose server: UDP bind to specific IPv4 behaves like 0.0.0.0%iface, causing wrong source IP and multihoming conflicts Product: Wine Version: 11.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)list.winehq.org Reporter: koekdendeniz(a)gmail.com Distribution: --- A Windows dedicated server application (WindroseServer-Win64-Shipping.exe) works correctly on native Windows, where binding to a specific IP via -Multihome=<IP> results in UDP sockets bound to that IP:PORT. Under Wine on Linux, the same server appears to bind correctly in Wine debug logs, but the resulting Linux UDP socket shows up as 0.0.0.0%iface:PORT instead of IP:PORT. This causes two problems: 1. Outgoing UDP replies use the wrong source IP (the host's main IP instead of the IP passed to -Multihome). 2. Multiple instances cannot use the same UDP port on different local IPs, because the socket effectively behaves like 0.0.0.0:PORT instead of IP_A:PORT and IP_B:PORT. Tested with: * host networking * multiple public IPv4 addresses assigned on the same host * command line using -Multihome=<IP> Expected result: UDP socket is bound to the specific IPv4 address, replies use that source IP, and multiple instances can bind the same UDP port on different local IPs. Actual result: UDP socket appears as 0.0.0.0%iface:PORT, replies use the wrong source IP, and same-port multi-IP hosting fails. -- 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 4

[Bug 33008] New: UDP listening on specific IP address does not work properly
by wine-bugs＠winehq.org July 19, 2026

July 19, 2026

http://bugs.winehq.org/show_bug.cgi?id=33008 Bug #: 33008 Summary: UDP listening on specific IP address does not work properly Product: Wine Version: 1.5.24 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: decimusmaximus(a)seznam.cz Classification: Unclassified Wine updated from 1.5.6 to 1.5.24. My app uses UDP listening on specific address (not 0.0.0.0). It is running on machine with NAT, there are two interfaces with IP A.A.A.A (public) and IP B.B.B.B (private) My app is set to listen only on one IP address, IP A.A.A.A It works properly on Wine 1.5.6. Traffic from subnet B.B.B.B is NATed to A.A.A.A interface and application running in wine receives it correctly. After update to 1.5.24 it does not work anymore. Application does not receive data from private subnet B.B.B.B, however it works properly for traffic incoming on A.A.A.A interface. Please see attached schema. results of "netstat --listening" with Wine 1.5.6 it is listening on A.A.A.A address correctly. with Wine 1.5.24 it is listening on 0.0.0.0 (obviously incorrect, socket binding is set to A.A.A.A address in application and although it is saying 0.0.0.0 app does not receive any data from B.B.B.B network) This application has to be listening only on one interface and do not mix public and private addresses. In this case it is not accessible for clients in private network, so it is critical bug. Main strange thing is, that it is listening on all addresses 0.0.0.0 although socket binding in application is set to address A.A.A.A -- 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.

3 35

[Bug 56488] New: TCP socket appears to be in use but it is not
by WineHQ Bugzilla July 19, 2026

July 19, 2026

https://bugs.winehq.org/show_bug.cgi?id=56488 Bug ID: 56488 Summary: TCP socket appears to be in use but it is not Product: Wine Version: 4.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bugzilla400(a)gmail.com Distribution: --- I have a .net 3.5 application that runs fine on Windows but have a problem when running on Debian. The problem is a socket binding error "address already in use". CODE: System.Net.Sockets.SocketException: Unknown error (0x2740) at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Bind(EndPoint localEP) netstat and lsof commands don't show the socket that appears to be in use, so I assume it's not really in use. Furthermore the problem only happens, and it always happen, in the following circumstance. 1. The program A.exe listens successfully on the server socket <anyip>:<port>. 2. Then it start the program B.exe and close itself (closing the socket too). 3. Program B.exe do something and then starts again A.exe. 4. A.exe try to bind the server socket but in that case it fails with the error "address already in use". 5. Restart A.exe, now the binding success. To start the new process I'm using System.Diagnostic.Process. CODE: // This is only a generic example var process = new Process() { StartInfo = new ProcessStartInfo { FileName = "cmd", Arguments = "/c /usr/bin/bash -c \"/usr/bin/sleep 5 && /usr/bin/wine path/of/process/program.exe\"", UseShellExecute = false, WorkingDirectory = "the/working/dir", } } These are the socket states after each steps (netstat): 1. LISTEN 2. not listed due to socket is closed 3. not listed due to socket is closed 4. not listed due to socket is closed <- But I have got the error 5. LISTEN I suppose that the A and B processes close properly because I don't see them in htop anymore. There seems to be something left hanging. I've found that if I don't relaunch A.exe from B, but do it manually, everything works fine. I also noticed this behavior that I wasn't expecting: - if I use socket.Accept the socket is bound to the A.exe process, - if I use socket.BeginAccept the socket is bound to the winserver32 process Clearly if I simply close the A.exe application and restart it all works fine. -- 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