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

[Bug 59623] New: Dishonored(DE) fails to load built-in (wine) 64bit msvcp90.dll / msvcr90.dll
by WineHQ Bugzilla April 5, 2026

April 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=59623 Bug ID: 59623 Summary: Dishonored(DE) fails to load built-in (wine) 64bit msvcp90.dll / msvcr90.dll Product: Wine Version: 11.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcp Assignee: wine-bugs(a)list.winehq.org Reporter: ikalvachev(a)gmail.com Distribution: Slackware Created attachment 80688 --> http://bugs.winehq.org/attachment.cgi?id=80688 trace of Dishonored.DE having issue loading built-in msvcp/r90.dll I got the Dishonored (Definitive Edition) game from the Epic Store. From the logs it seems that the game tries to load MSVCP90.DLL, in turn it tries to load MSVCR90.DLL (from winsxs/amd64*) and fails at init. Installing native (win64) libraries with `winetricks` workarounds the problem. Distribution is Slackware64-current. I'm compiling my own wine-11.6 with `--enable-archs=i386,x86_64` aka WoW64. The prefix is about a month old (wine-11.4 at the time). I've run `wineboot -u` to test 11.6. I do have the wine msvcp/r90.dll files in system32 and winsxs/amd64*/ and they are the same as the ones in `wine-11.6/lib/wine/x86_64-windows/` installation. I'm attaching log created with `WINEDEBUG=+timestamp,Dishonored.exe:+module` The log does not contain messages from the EpicLauncher. The relevant part is at the last page. It doesn't look like the problem is unimplemented or missing function/functionality/stub... I don't know what other debug options to use to trace the cause of the problem. -- 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 0

[Bug 58071] New: Sacred Gold: Crash on startup with specific setup
by WineHQ Bugzilla April 5, 2026

April 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=58071 Bug ID: 58071 Summary: Sacred Gold: Crash on startup with specific setup Product: Wine Version: 10.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: wine(a)kryotek.mozmail.com Distribution: --- Created attachment 78325 --> https://bugs.winehq.org/attachment.cgi?id=78325 Tar containing the winedbg log and both system's info The game crashes on startup on my desktop PC, but works on my laptop. All the detailed info is in the attachment, here's a TLDR: Game is really old and runs DX7 Both systems are running the latest Arch Linux with KDE Plasma on Wayland, using the zen kernel. Laptop is old, with an integrated Intel i3 GPU and a dedicated NVIDIA 610M. I'm NOT using Nvidia dedicated drivers. Integrated display, it believes an external VGA is connected but that's disabled in KDE. Desktop is a full AMD system with no integrated GPU and a dedicated 6750XT. I have a multi monitor setup with the main being a 1440p 165hz display with VRR, the secondary a 1280x1024 75HZ without VRR. Initially I had the problem using Bottles, but I tried again with a fresh wine installation and a fresh wine prefix and had the same results. I'm using the latest wine 10.5 and manually cloning and building wine didn't fix the problem. The bug is triggered inside "d3d7_EnumZBufferFormats" because the device_iid pointer is 0x438, probably too low to be an actual pointer? If you want help in reproducing and debugging I'm free most of the time and will be happy to help! -- 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 17

[Bug 59618] New: Len'en Mugenri ~ Evanescent Existence: Crashes when entering Aoji's second boss spell card
by WineHQ Bugzilla April 5, 2026

April 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=59618 Bug ID: 59618 Summary: Len'en Mugenri ~ Evanescent Existence: Crashes when entering Aoji's second boss spell card 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: tasos500(a)hotmail.com Distribution: --- Created attachment 80679 --> http://bugs.winehq.org/attachment.cgi?id=80679 Backtrace file On a clean save file, after first using the config app to set the game to full screen 32bit mode, start a Normal difficulty playthrough. When Aoji's second nonspell is cleared through damage, the game crashes. The game was not patched with the English translation. See the attached backtrace file. The game can be downloaded for free here: https://www.freem.ne.jp/win/game/15994 The Wine version used is 11.0 (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.

1 1

[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