September 2024 - 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 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 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 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

[Bug 49822] New: vatSys: crashes on run, unhandled Reflection.TargetInvocationException
by WineHQ Bugzilla July 19, 2026

July 19, 2026

https://bugs.winehq.org/show_bug.cgi?id=49822 Bug ID: 49822 Summary: vatSys: crashes on run, unhandled Reflection.TargetInvocationException Product: Wine Version: 5.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: blue(a)blu3wolf.com Distribution: --- Created attachment 68157 --> https://bugs.winehq.org/attachment.cgi?id=68157 console output from running the installed program vatSys installs normally, but crashes on run, throwing a TargetInvocationException. Can be downloaded from https://vatsys.sawbe.com/downloads/vatSysSetup.zip -- 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 14980] New: Powerpoint 2007 fails to start
by wine-bugs＠winehq.org July 18, 2026

July 18, 2026

http://bugs.winehq.org/show_bug.cgi?id=14980 Summary: Powerpoint 2007 fails to start Product: Wine Version: 1.1.3 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dimesio(a)earthlink.net Created an attachment (id=15589) --> (http://bugs.winehq.org/attachment.cgi?id=15589) Console from 1st attempt to run Powerpoint Powerpoint 2007 fails to start in 1.1.3 on openSUSE 10.3, installed to a clean wineprefix with no overrides. The first time trying to run Powerpoint, the splash screen appears briefly, then Powerpoint just shuts down. The second time, a dialog box appears with the message "PowerPoint failed to start correctly last time. Starting PowerPoint in safe mode will help you correct or isolate a startup problem in order to successfully start the program. Some functionality may be disabled in this mode. Do you want to start PowerPoint in safe mode?" If I click yes, the splash screen appears briefly, then Powerpoint shuts down. The third time, a dialog box appears with the message "PowerPoint failed to launch in safe mode. Do you want to start Detect and Repair?" If I click yes, it just shuts down. This cycle repeats for subsequent attempt to run the program. -- 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 65

[Bug 52105] New: Handle to \Device\NamedPipe\ cannot be used as the RootDirectory for NtCreateNamedPipeFile
by WineHQ Bugzilla July 17, 2026

July 17, 2026

https://bugs.winehq.org/show_bug.cgi?id=52105 Bug ID: 52105 Summary: Handle to \Device\NamedPipe\ cannot be used as the RootDirectory for NtCreateNamedPipeFile Product: Wine Version: 6.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: jinoh.kang.kr(a)gmail.com CC: jacek(a)codeweavers.com Regression SHA1: 2600ecd4edfdb71097105c74312f83845305a4f2 Distribution: --- Commit 2600ecd4edf (server: Use a separated object for each opened named pipe device file., 2018-10-29) split the role of the named pipe device and the named pipe file. However, in doing so, it changed the semantics of opening \Device\NamedPipe\. In particular, it is no longer possible to use a handle to \Device\NamedPipe\ as RootDirectory when creating a named pipe. This bug makes Cygwin's named pipe creation (https://github.com/cygwin/cygwin/blob/4f47e64b11ed8d47c62fa89e9b971f44b7e9a…) loop forever. -- 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 22

[Bug 55242] New: iperf 2.0.8 will not quit with CTRL+C
by WineHQ Bugzilla July 17, 2026

July 17, 2026

https://bugs.winehq.org/show_bug.cgi?id=55242 Bug ID: 55242 Summary: iperf 2.0.8 will not quit with CTRL+C Product: Wine Version: 8.12 Hardware: x86-64 URL: https://web.archive.org/web/20190523161058/https://ipe rf.fr/download/windows/iperf-2.0.8-win32.zip OS: Linux Status: NEW Keywords: download, source Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: imwellcushtymelike(a)gmail.com Distribution: Ubuntu When iperf is run in dual mode it will not exit after hitting CTRL+C. $ wine iperf.exe -c 127.0.0.1 -d -t 1 -P 5 007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 connect failed: Connection refused ------------------------------------------------------------ connect failed: Connection refused Server listening on TCP port 5001 TCP window size: 128 KByte (default) ------------------------------------------------------------ connect failed: Connection refused ------------------------------------------------------------ Client connecting to 127.0.0.1, TCP port 5001 connect failed: Connection refused TCP window size: 16.0 KByte (default) ------------------------------------------------------------ [264] local 127.0.0.1 port 5001 connected with 127.0.0.1 port 53058 ^CWaiting for server threads to complete. Interrupt again to force quit. Pressing CTRL+C has no effect and the app has to be SIGKILLed. $ sha1sum iperf-2.0.8-win32.zip f312bf6ab7de3b1921cae7f4953aed0ce6b17afa iperf-2.0.8-win32.zip iperf -s will exit with CTRL+C though. It also doesn't produce any "connection failed" messages. Source: https://iperf.fr/download/source/iperf-2.0.8-source.tar.gz -- 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