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

[Bug 59670] New: Feather Client Installer thinks it is already running.
by WineHQ Bugzilla April 23, 2026

April 23, 2026

http://bugs.winehq.org/show_bug.cgi?id=59670 Bug ID: 59670 Summary: Feather Client Installer thinks it is already running. Product: Wine Version: 11.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: turbojax07+wine(a)gmail.com Distribution: --- Created attachment 80760 --> http://bugs.winehq.org/attachment.cgi?id=80760 Wine logs Info: OS: Linux Mint 22 (Wilma) Ubuntu Codename: noble Wine Version: wine-11.6 -- 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 8

[Bug 59530] New: wine-mono ignores color setting from theme / registry
by WineHQ Bugzilla April 22, 2026

April 22, 2026

http://bugs.winehq.org/show_bug.cgi?id=59530 Bug ID: 59530 Summary: wine-mono ignores color setting from theme / registry Product: Framework Mono Version: main Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mono Assignee: wine-bugs(a)list.winehq.org Reporter: andreas.franz(a)arcor.de CC: madewokherd(a)gmail.com Distribution: --- I'm using WineHQ 11.4 on Linux Mint (cinnamon desktop) with an .NET-application called MailStore Client. Background-Color ("control"-color) seems to be taken from (ugly) classic theme - WineHQ is set to Aero, though. With installed MS .NET 4.8, it looks like on real Windows-machines. So, I assume, colors are hardcoded at wine-mono? Is there any ENV to change this behaviour? I found "FEATURE_WINDOWS_SYSTEM_COLORS" on source-code, which decides if wine-mono reads colors from windows-system. But it seems to be a compiler-flag? Any ideas? regards, Andy -- 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 7

[Bug 47660] New: Samsung Smart View crash on start
by wine-bugs＠winehq.org April 22, 2026

April 22, 2026

https://bugs.winehq.org/show_bug.cgi?id=47660 Bug ID: 47660 Summary: Samsung Smart View crash on start Product: Wine Version: 4.0.1 Hardware: x86-64 URL: https://www.samsung.com/br/support/smart-view/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: yoshimit(a)gmail.com Distribution: Mint Created attachment 65103 --> https://bugs.winehq.org/attachment.cgi?id=65103 Log from crash Installing Samsung Smart View and tried to run it. Got a crash with the information 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.

3 11

[Bug 52284] New: Factory I/O SPS-Software hangs
by WineHQ Bugzilla April 22, 2026

April 22, 2026

https://bugs.winehq.org/show_bug.cgi?id=52284 Bug ID: 52284 Summary: Factory I/O SPS-Software hangs Product: Wine Version: 7.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: maiktapwagner(a)aol.com Distribution: --- Hello everyone, I got a request from the ubuntuusers.de forum that one user had problems running this program and submitted an AppDB entry at https://appdb.winehq.org/objectManager.php?sClass=version&iId=40486 providing tests for 7.0rc1 and 7.0rc2 (queued) where as the console is spammed with 018c:fixme:d3d:wined3d_device_context_resolve_sub_resource Multisample resolve is not fully supported for typeless formats (dst_format WINED3DFMT_R8G8B8A8_TYPELESS, src_format WINED3DFMT_R8G8B8A8_TYPELESS, format WINED3DFMT_R8G8B8A8_UNORM). Steps to reproduce after installation: New → File → Drivers → Control I/O (opens up a grey window but nothing happens) -- 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 10

[Bug 50994] New: LogicCircuit: doesn't start on wine 6.6
by WineHQ Bugzilla April 22, 2026

April 22, 2026

https://bugs.winehq.org/show_bug.cgi?id=50994 Bug ID: 50994 Summary: LogicCircuit: doesn't start on wine 6.6 Product: Wine Version: 6.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dogewanderer(a)protonmail.com Distribution: --- Created attachment 69833 --> https://bugs.winehq.org/attachment.cgi?id=69833 Logs I installed LogicCircuit (x86 only it seems) https://github.com/eugenelepekhin/LogicCircuit When i tried to run it, it didn't. >From the logs i suppose this is related to NET 4.7.2 (minimum requirement for running LogicCircuit), which I installed, using this link https://dotnet.microsoft.com/download/dotnet-framework/thank-you/net472-off…, but didn't make any difference. All this wad done in a 64bit Prefix. Additionally i recived this output in my shell after the program stopped: 0090:err:rpc:I_RpcReceive we got fault packet with status 0x1c010003 -- 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 11

[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 April 22, 2026

April 22, 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 1

[Bug 34178] New: MiKTeX 2.9 (32-bit) fails to install
by wine-bugs＠winehq.org April 22, 2026

April 22, 2026

http://bugs.winehq.org/show_bug.cgi?id=34178 Bug #: 34178 Summary: MiKTeX 2.9 (32-bit) fails to install Product: Wine Version: 1.6 Platform: x86-64 URL: http://miktex.org/download OS/Version: Linux Status: NEW Keywords: download, Installer, source Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Blocks: 34172 Classification: Unclassified Noticed this while looking at bug 34172. I tried the 32-bit version, and get a separate, but potentially related issue. Download the installer from http://miktex.org/download Install as normal. Eventually it gives an error during install: ========== The operation could not be completed for the following reason: The operation failed for some reason. Details: C:\Program Files\MiKTeX 2.90\miktex/bin\initexmf.exe ========== austin(a)aw25 ~ $ sha1sum basic-miktex-2.9.4813.exe e8647f57fe866c00119ca8938785cacfaa5ca826 basic-miktex-2.9.4813.exe austin(a)aw25 ~ $ du -h basic-miktex-2.9.4813.exe 155M basic-miktex-2.9.4813.exe wine-1.6-178-g7944ca4 -- 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 12

[Bug 59671] New: Inconsistent FILE_ATTRIBUTE_REPARSE_POINT on container bind-mounts
by WineHQ Bugzilla April 22, 2026

April 22, 2026

http://bugs.winehq.org/show_bug.cgi?id=59671 Bug ID: 59671 Summary: Inconsistent FILE_ATTRIBUTE_REPARSE_POINT on container bind-mounts Product: Wine Version: 11.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: me(a)a2va.dev Distribution: --- Created attachment 80762 --> http://bugs.winehq.org/attachment.cgi?id=80762 Rust executable When running Wine inside a container where the working directory is a Linux mount point (bind-mounted), Wine identifies the directory as a symlink/reparse point, but fails to satisfy a DeviceIoControl request for FSCTL_GET_REPARSE_POINT. This causes Rust's std::fs::read_link to fail with ERROR_NOT_A_REPARSE_POINT (4390). ``` use std::env; use std::path::PathBuf; fn main() { let target = env::args().nth(1).unwrap_or_else(|| ".".to_string()); let path = PathBuf::from(&target); if path.is_symlink() { println!("Is symlink: {}", path.display()); path.read_link().unwrap(); } } ``` Output of the program: ``` Z:\home\a2va\Documents\temp\wine-readlink>wine-readlink.exe Is symlink: . thread 'main' (104) panicked at src\main.rs:10:26: called `Result::unwrap()` on an `Err` value: Os { code: 4390, kind: Uncategorized, message: "OS Error 4390 (FormatMess ageW() returned error 317)" } note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ``` Here is the Dockerfile, with the command to reproduce for both podman and docker. ```FROM fedora:43 RUN dnf install -y \ wine \ wine-core \ wine-common ENV WINEPREFIX=/opt/wineprefix RUN mkdir -p "$WINEPREFIX" RUN wineboot --init RUN wineserver -w # ENV WINEDEBUG=+relay,+file,+ioctl CMD ["wine", "cmd"] # podman build -f Dockerfile -t wine-repro:latest # podman run -it -w "$(pwd)" -v "$(pwd):$(pwd):rbind,z" wine-repro:latest # podman run -it -w "$(pwd)" -v "$(pwd):$(pwd):rbind,z" wine-repro:latest wine read-link.exe > wine.log 2>&1 # docker build -f Dockerfile -t wine-repro:latest . # docker run -it -w "$(pwd)" -v "$(pwd):$(pwd)" wine-repro:latest # docker run -it -w "$(pwd)" -v "$(pwd):$(pwd)" wine-repro:latest wine read-link.exe > wine.log 2>&1 ``` It's also reproducible in C, with CreateFile and DeviceIoControl. -- 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 46206] New: Altium Designer 17 account sign in fails as of 3.19
by wine-bugs＠winehq.org April 22, 2026

April 22, 2026

https://bugs.winehq.org/show_bug.cgi?id=46206 Bug ID: 46206 Summary: Altium Designer 17 account sign in fails as of 3.19 Product: Wine Version: 3.19 Hardware: x86-64 URL: https://s3.amazonaws.com/altium-release-manager/Altium _Designer_17/OfflineSetup_Altium_Designer_Public_17_1_ 9.zip OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jhansonxi(a)gmail.com Distribution: Ubuntu Account sign-ins are broken in Altium Designer 17.1.9 (and probably other releases) as of Wine 3.19. Steps to reproduce: 1. Launch Altium Designer. 2. Close floating window (Storage, etc.) which will likely trigger an error (probably bug #39765 which I'll verify later) 3. At MyAccount/License Management page click "Sign in" link 4. At "Account Sign In" dialog (which can get stuck behind main window) enter anything for user name and password, check the "I have read and understand the warning" privacy invasion checkbox, then the "Sign in" button. Expected behavior: Dialog box closes then reappears a moment later when sign-in fails. Wine 3.19-3.21 behavior: Dialog closes then an "Out of memory" error dialog is displayed. Installation: 1. Download the offline installer from the URL (3.6GB). Extract to subdirectory. 2. winetricks -q corefonts dotnet461 mdac28 win7 I used winetricks 20180815-next. Verified NET Runtimes with netfx_setupverifier-20180517.exe. Manually triggered GAC rebuild via ngen.exe since winetricks didn't seem to do so and it cluttered up the logs when it randomly started on its own. 3. Run the Altium installer. To save time deselect the optional items. Other: There's a nuisance rundll32.exe error at start-up reporting "This application could not be started". It doesn't seem to be related to this bug although I haven't found the cause of it yet. -- 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 15

[Bug 50591] New: ReadFile schedules async read when ReadIntervalTimeout is MAXDWORD
by WineHQ Bugzilla April 22, 2026

April 22, 2026

https://bugs.winehq.org/show_bug.cgi?id=50591 Bug ID: 50591 Summary: ReadFile schedules async read when ReadIntervalTimeout is MAXDWORD Product: Wine Version: 6.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: aaron.knister(a)gmail.com Distribution: --- Created attachment 69269 --> https://bugs.winehq.org/attachment.cgi?id=69269 ntdll: NtReadFile async reads always return success when avail_mode TRUE TeraTerm is ending up with missing data when it reads from a COM/Serial port. TeraTerm sets ReadIntervalTimeout to MAXDWORD and then calls ReadFile asynchronously, and if there's pending IO it waits 1 second for the overlapped struct event to be signalled. If the signal is received, it processes the received I/O, else continues on and will perform another ReadFile. This is the code snippet: if (!ReadFile(cv->ComID,&(cv->InBuff[cv->InBuffCount]), InBuffSize-cv->InBuffCount,&C,&rol)) { if (GetLastError() == ERROR_IO_PENDING) { if (WaitForSingleObject(rol.hEvent, 1000) != WAIT_OBJECT_0) { C = 0; } else { GetOverlappedResult(cv->ComID,&rol,&C,FALSE); } } What's happening in WINE, is ReadFile returns non-zero with ERROR_IO_PENDING and the WaitForSingleObject times out. The asynchronous read *does* complete after the timeout, but by that point the application has given up and moved on. I initially thought the application was at fault, because it should retry if the wait times out. However, in the documentation for ReadFile it points to documentation about COMMTIMEOUTS (https://docs.microsoft.com/en-us/windows/win32/api/winbase/ns-winbase-commt…) which says the following: A value of MAXDWORD, combined with zero values for both the ReadTotalTimeoutConstant and ReadTotalTimeoutMultiplier members, specifies that the read operation is to return immediately with the bytes that have already been received, even if no bytes have been received. To me, that means Wine ought not to be triggering an asynchronous read when the comm timeout parameters are set as indicated above. I coded a simple fix, which is in NtReadFile, if avail_mode is TRUE return success even if no bytes were read. See attached patch. It works for TeraTerm, I have no idea if it causes other regressions. -- 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