- Wine-Bugs - list.winehq.org

[Bug 58966] New: Transparent windows are completely broken under Winewayland driver.
by WineHQ Bugzilla April 4, 2026

April 4, 2026

http://bugs.winehq.org/show_bug.cgi?id=58966 Bug ID: 58966 Summary: Transparent windows are completely broken under Winewayland driver. Product: Wine Version: 10.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)list.winehq.org Reporter: cramea(a)proton.me Distribution: --- Created attachment 79670 --> http://bugs.winehq.org/attachment.cgi?id=79670 Comparison image Transparent windows lose transparency and just show up black and also become unclickable and unmovable in WineWayland. Issues are seen in an application called LunaTranslator. I'm guessing any application that uses transparency like this application is broken under WineWayland, but I'm not sure. -- 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 43425] New: 64-bit .NET application crashes with NullReferenceException
by wine-bugs＠winehq.org April 4, 2026

April 4, 2026

https://bugs.winehq.org/show_bug.cgi?id=43425 Bug ID: 43425 Summary: 64-bit .NET application crashes with NullReferenceException Product: Wine Version: 2.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: tjroamer(a)gmail.com Distribution: --- Created attachment 58791 --> https://bugs.winehq.org/attachment.cgi?id=58791 back trace of the bug I encountered a problem with the 64-bit .NET Framework: My C# program is very simple: Code: static void Main(string[] args) { System.Console.WriteLine("Hello world!"); Debug.WriteLine("Debug Hello world!"); } I installed the WINE-2.12 64-bit on CentOS 7 (3.10.0-514.21.1.el7.x86_64) and installed the .NET Framework 4.6.1 onto it. Before installing the .NET Framework, I removed wine-mono. I got the following error message when I tried to run the above program: Hello world! Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object. at System.Diagnostics.DiagnosticsConfiguration.Initialize() at System.Diagnostics.DiagnosticsConfiguration.get_IndentSize() at System.Diagnostics.TraceInternal.InitializeSettings() at System.Diagnostics.TraceInternal.WriteLine(String message) at ConsoleApplication3.Program.Main(String[] args) wine: Unhandled page fault on read access to 0x00000000 at address 0x1aa460fd (thread 0009), starting debugger... The problem is with the line "Debug.WriteLine(...)". However, the same application compiled with 32-bit works well. I found out that I got the similar error at other positions when I ran our in-house 64-bit .NET program, even if I don't use Debug.WriteLine(...), so I created the hello-world program to reproduce it. My final goal is: run our 64-bit .NET application on a 64-bit WINE with .NET Framework 4.6.1. -- 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 42340] New: Wrong decorations with KWin (KDE Plasma 5)
by wine-bugs＠winehq.org April 4, 2026

April 4, 2026

https://bugs.winehq.org/show_bug.cgi?id=42340 Bug ID: 42340 Summary: Wrong decorations with KWin (KDE Plasma 5) Product: Wine Version: 2.0-rc6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: ArchLinux Created attachment 57102 --> https://bugs.winehq.org/attachment.cgi?id=57102 Testprogram to show wrong decorations Setting "Allow the window manager to decorate the windows" in winecfg solves the issue. There are two issues: -Minimize box is always shown -Maximize box is only shown when WS_THICKFRAME is also used Testprogram 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.

2 2

[Bug 59619] New: Windows with no window control buttons have at least close button
by WineHQ Bugzilla April 4, 2026

April 4, 2026

http://bugs.winehq.org/show_bug.cgi?id=59619 Bug ID: 59619 Summary: Windows with no window control buttons have at least close button 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: gsw.eugeneulan(a)gmail.com Distribution: Mint To replicate this issue, you can launch included executable (HiBitUninstaller-Portable.exe) in the default Wine prefix. The first greeting window "Save Settings" on real Windows doesn't have any window control buttons (minimize, maximize & close). On Cinnamon desktop (tried with Linux Mint 22.3) this window has close button; on KDE Plasma (tried with Kubuntu 25.10) it also has minimize button, but that's another inconsistent behavior regarding window control buttons that has been reported long ago: https://bugs.winehq.org/show_bug.cgi?id=42340 If an option "Allow the window manager to decorate the windows" in winecfg is disabled, then there'll be no window control buttons present, as expected. -- 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 59447] New: No visual difference between enabled and disabled tree view element
by WineHQ Bugzilla April 4, 2026

April 4, 2026

http://bugs.winehq.org/show_bug.cgi?id=59447 Bug ID: 59447 Summary: No visual difference between enabled and disabled tree view element Product: Wine Version: 11.3 Hardware: x86-64 URL: https://github.com/SimplexDesigns/Windows-Components-T ester/releases/download/v1-release/Release.zip OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: gsw.eugeneulan(a)gmail.com Distribution: Ubuntu Created attachment 80431 --> http://bugs.winehq.org/attachment.cgi?id=80431 Running Windows Component Tester on different systems All disabled window elements have some sort of gray color applied to them, except for the Tree View. This is very confusing, as with no visual difference the user should interact with an element to see whether it's disabled or not. You can use Windows Components Tester utility for additional testing: 1. Download its archive by the direct link included in the bug's URL field; 2. Extract the archive; 3. Run "Windows Component Tester.exe" in the default Wine prefix; 4. Go to the "Item View" tab at the top; 5. See and compare observed and expected results on the attached screenshot! -- 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 44467] New: South Park The Fractured But Whole: Crashes on startup
by wine-bugs＠winehq.org April 4, 2026

April 4, 2026

https://bugs.winehq.org/show_bug.cgi?id=44467 Bug ID: 44467 Summary: South Park The Fractured But Whole: Crashes on startup Product: Wine Version: 3.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: k.haoz(a)zoho.com Distribution: --- Created attachment 60410 --> https://bugs.winehq.org/attachment.cgi?id=60410 Backtrace when trying to start the game through Steam. The game crashes when trying to start it through the Steam client. -- 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 50499] New: SO_REUSEADDR compatibility problems
by WineHQ Bugzilla April 4, 2026

April 4, 2026

https://bugs.winehq.org/show_bug.cgi?id=50499 Bug ID: 50499 Summary: SO_REUSEADDR compatibility problems Product: Wine Version: 6.0-rc6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: James(a)superbug.co.uk Distribution: --- The use case I am struggling with is the use of a Windows program running in wine that is sending and receiving UDP packets. This particular windows program uses SO_REUSEADDR socket option and opens two sockets. Lets call the first one socket A, and the second one Socket B. The SO_REUSEADDR from the Windows application is translated by "wine" into a SO_REUSEADDR in Linux. Unfortunately the behaviour of these is different between Windows and Linux so the Windows application fails to run on Linux under wine. 1 ) On windows: All received unicast UDP packets will arrive on the first opened socket. Thus on socket A. 2) On Linux: All received unicast UDP packets will arrive on the last opened socket. Thus on socket B. The problem is that this windows program only expects to receive unicast UDP packets on socket A, and thus it sees no packets. There are no currently existing socket options in Linux that would permit wine to simulate the Windows behaviour. And thus, the reason I am asking the question here. Please can we add an extra socket option to the Linux socket options such that we can get wine to simulate Windows correctly. I.e. behave like (1) above. Now wine is pretty good at simulating most things Windows throws at it, but socket options is not one of them yet. Also note, that (1) is actually more secure than (2) because it prevents other applications with the same UserID from hijacking the socket. Although (2) is more helpful in more gracefully handling some error edge cases. Suggested new option name: SO_REUSEADDR_WS -- 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 56759] New: Army Men: Colors are displayed incorrectly
by WineHQ Bugzilla April 4, 2026

April 4, 2026

https://bugs.winehq.org/show_bug.cgi?id=56759 Bug ID: 56759 Summary: Army Men: Colors are displayed incorrectly Product: Wine Version: 9.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bugzilla(a)cock.email Distribution: --- The first Army Men game has incorrect colors. This causes the cinematics to be black, the in game colors to be crushed, for instance blue rivers become black rivers, and the greens of the forest all become one color of green. It makes things somewhat difficult to see. I have tested this on different computers with different hardware to make sure. Someone mentioned it has something to do with the bitmaps for the game not being converted properly. -- 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 59312] New: Application icon for game is not rendering correctly (literally in half).
by WineHQ Bugzilla April 4, 2026

April 4, 2026

http://bugs.winehq.org/show_bug.cgi?id=59312 Bug ID: 59312 Summary: Application icon for game is not rendering correctly (literally in half). Product: Wine Version: 11.1 Hardware: arm OS: MacOS Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: porksoda6716(a)gmail.com Created attachment 80243 --> http://bugs.winehq.org/attachment.cgi?id=80243 Wine log. Same issue existed back in wine-stable version 10 (installed via MacPorts) and in wine-development 11.0-rc5 (installed via Homebrew this time, MacPorts version uninstalled). I installed a Godot game meant for Windows (https://allhailthequeenuwu.itch.io/tadc-vn-candy-chaos) and tried running it through Wine on my Mac. For the most part, it works perfectly fine. However, there is a weird issue where the application icon in the dock does not render properly. Instead, it shows up cut off. This happens whether running it through the command line, right-clicking on the .exe and opening it via Wine-Devel, or running the game through the Wine explorer. The game files seem to be stored separately from the downloaded zip file. I was able to find some game files in "/Users/<user>/.wine/drive_c/users/<user>/AppData/Roaming/Godot/app_userdata/TADC Fangame sequel", though they seem to be user preferences, logs, save file data, and shader caches. I have my game installed in "/Applications/Games/TADCVN CANDY CHAOS/TADCVN_CANDY_CHAOS.exe." I cannot find a directory for the assets so I don't know where the icon should be loaded from. -- 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 5

[Bug 41247] New: WASAPI exclusive pull mode sound doesn't work, but shared (non-exclusive) does
by wine-bugs＠winehq.org April 4, 2026

April 4, 2026

https://bugs.winehq.org/show_bug.cgi?id=41247 Bug ID: 41247 Summary: WASAPI exclusive pull mode sound doesn't work, but shared (non-exclusive) does Product: Wine Version: 1.9.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: markk(a)clara.co.uk Distribution: --- Wine 1.9.17, Lubuntu 16.04 x86-64. The current beta version of WinUAE (3.4.0 beta 4) uses WASAPI in pull mode. In Wine that works OK in shared (non-exclusive) mode, but exclusive mode does not work, giving console output like this: fixme:alsa:AudioClient_Initialize EXCLUSIVE mode with EVENTCALLBACK WASAPI: Initialize() 8889000A Sorry, can't initialize sound. In contrast, WinUAE 3.3.0 uses WASAPI in push mode, and both exclusive and shared work fine there. To reproduce: - Use winecfg to set Windows version to e.g. Windows 10. - Download and run the WinUAE 3.3.0 installer from http://www.winuae.net/files/InstallWinUAE3300.msi - Rename winuae.exe to winuae330.exe - Download WinUAE 3.4.0 beta 4 from http://www.winuae.net/files/b/winuae_3300b4.7z then unpack to the WinUAE program directory. - Download a program which plays sound, for example http://main.aminet.net/demo/euro/DOC_Demons.lha - Run winuae.exe (version 3.4.0b4): wine winuae.exe -log - When the WinUAE Properties window appears, click Floppy drives in the tree-view on the left side. Then click the "..." button to the right of DF0: and select DOC_Demons.lha - Click Sound in the tree-view on the left. By default the drop-down at the top should say "WASAPI: Default Audio Device", if not select that. - Click Start at the bottom of the window. - Part of the log output should say something like WASAPI: '{0.0.0.00000000}.{176D6B2F-F69E-497A-AE3D-15C5CEE27C79}' WASAPI: Shared Pull CH=2 FREQ=44100 BUF=2048 (4096) - Wait for the demo to load and start, and you should hear sound. - Press F12 to open the settings window. The sound page should be showing. Change the drop-down at the top to "WASAPI EX: Default Audio Device" then click OK at the bottom to continue emulation. There is no sound and this console output: fixme:alsa:AudioClient_Initialize EXCLUSIVE mode with EVENTCALLBACK WASAPI: Initialize() 8889000A Sorry, can't initialize sound. -- 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 4