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

[Bug 59007] New: Ultima Online - Enhanced Client - Intel/Nvidia issues
by WineHQ Bugzilla May 4, 2026

May 4, 2026

http://bugs.winehq.org/show_bug.cgi?id=59007 Bug ID: 59007 Summary: Ultima Online - Enhanced Client - Intel/Nvidia issues Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: thebit(a)gmail.com Distribution: --- My old AMD cpu/gpu works fine under Linux Desktop with UO EC. My new (purchased in 2024) pc is having issues with this EC client in UO. Intel(R) Core(TM) i9-14900KF Nvidia RTX 4070 12G 64GB RAM I am playing with server latency of circa 212ms and when i move one tile, it pauses for a few seconds then repeat and rinse.. doesnt happen everywhere but it is generally unplayable. Tried Fedora, Zorin OS, Pop OS, Ubuntu, Debian, openSUSE and Linux Mint same outcom with Nvidia focus if applicablee. Wasnt using the noveau driver just proprietry and even tried the insatller directly from Nvidia and also mainline kernels to see if that made a difference but nope. The odd thing is that the Classic Client (CC) and chromium installer (CC too) versions work fine on new pc under linux desktop, just the EC seems to have the issues. I am back on Windows 11 and using EC and no issues what so ever, besides the random client crashes which i didnt get any this whole past year under Linux Desktop. Tried distro and winehq repos, various Proton options and wine staging too, lutris and cli with wine direclty to no avail. All same result and no go. -- 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 58420] New: Wine crashes when running msys2 iff CPU's PKU/PKRU feature is enabled
by WineHQ Bugzilla May 3, 2026

May 3, 2026

http://bugs.winehq.org/show_bug.cgi?id=58420 Bug ID: 58420 Summary: Wine crashes when running msys2 iff CPU's PKU/PKRU feature is enabled Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: pipcet(a)protonmail.com Distribution: --- This is a heads-up about a bug in cygwin/msys2 which may be misreported as a wine bug. The Cygwin code assumes CPUID leaf 0x0d to indicate in EBX a 64-byte-aligned value. That may or may not be true on current Windows systems, but on current Linux systems running Wine, with recent CPUs, a CPU feature called "PKU" or "PKRU" (memory protection keys for userspace), enabled by default, indicates an additional 8-byte XSAVE area. This makes the Cygwin code attempt to xsave to a non-64-byte aligned area, which causes a segfault and abnormal program termination. While this is clearly a bug, it's a bug that apparently cannot be triggered by current Windows systems. This means Wine fails to be bug-for-bug compatible in this case. I don't think there's an easy way around that: we'd have to trap XGETBV and CPUID instructions to pretend that a feature that is enabled by Linux actually isn't available. It would have been nice if the Linux kernel had provided a way to disable the pku feature on a per-process basis, but AFAICT, it didn't. The nopku kernel command line argument makes things work, but requires a reboot and disables the very useful PKU feature for the entire system. So I don't think there's a good workaround here, but maybe we should suggest to the Linux kernel people to allow per-process activation of any future XCR0 features? -- 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 12

[Bug 47028] New: WinSCP hosts list missing indentation
by wine-bugs＠winehq.org May 3, 2026

May 3, 2026

https://bugs.winehq.org/show_bug.cgi?id=47028 Bug ID: 47028 Summary: WinSCP hosts list missing indentation Product: Wine Version: 4.6 Hardware: x86-64 URL: http://winscp.net/download/winscp577.zip OS: Mac OS X Status: NEW Keywords: download, source Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gijsvrm(a)gmail.com CC: jr98(a)gmx.net Created attachment 64194 --> https://bugs.winehq.org/attachment.cgi?id=64194 terminal output, +message log, screenshots On windows there is space between the edge of the box and the icons. To reproduce, run WinSCP.exe and you can see the hosts list on the left. Attached is a zip containing terminal output, a +message log and screenshots for comparison. -- 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 7

[Bug 55925] New: StarOffice 4.0 crashes on start
by WineHQ Bugzilla May 3, 2026

May 3, 2026

https://bugs.winehq.org/show_bug.cgi?id=55925 Bug ID: 55925 Summary: StarOffice 4.0 crashes on start Product: Wine Version: 8.20 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 75485 --> https://bugs.winehq.org/attachment.cgi?id=75485 WINEDEBUG=+ole Steps to reproduce: 1. Run `SETUP.EXE` (straightforward even if you don't know German) 2. Run `wine 'C:\office40\soffice.exe'` This looked suspicious: 0114:trace:ole:StgOpenStorage16 (c:\office40\config\soffice.cfg,00000000,0x00000040,00000000,0,02D7F530) 0114:warn:ole:StgOpenStorage16 Couldn't open file for storage $ sha256sum SETUP.EXE 68f4fa4f1b2cc18056190c8082dacf4d8e296b4aec97527bb5b52eafabf6c699 -- 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 625] Multiple applications need support for private dll search paths 'HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\App Paths\\AppName.exe' (Lotus Organizer 97, Microsoft Money 99, LeapFrogConnect)
by WineHQ Bugzilla May 3, 2026

May 3, 2026

http://bugs.winehq.org/show_bug.cgi?id=625 KRosUser <kyle.kcsoftwares(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kyle.kcsoftwares(a)gmail.com --- Comment #38 from KRosUser <kyle.kcsoftwares(a)gmail.com> --- https://gitlab.winehq.org/wine/wine/-/merge_requests/10798 -- 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 59394] New: Tex Murphy: Overseer fails to start (segfault) using NVK/Mesa
by WineHQ Bugzilla May 3, 2026

May 3, 2026

http://bugs.winehq.org/show_bug.cgi?id=59394 Bug ID: 59394 Summary: Tex Murphy: Overseer fails to start (segfault) using NVK/Mesa Product: Wine Version: 11.1 Hardware: x86-64 URL: https://store.steampowered.com/app/302370/Tex_Murphy_O verseer/ OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: opengl Assignee: wine-bugs(a)list.winehq.org Reporter: gyebro69(a)gmail.com CC: rbernon(a)codeweavers.com Regression SHA1: 6802b32b3859e3b1c3e59bdb462d373fcf0608cf Distribution: ArchLinux Created attachment 80353 --> http://bugs.winehq.org/attachment.cgi?id=80353 glxinfo -B, eglinfo -B The game crashes immediately on start in Wine-11.1 and 11.2 with a segmentation fault when using the open source NVK driver and Mesa 25.3.4. There is no such problem with the Nvidia binary driver 580.126.09. This happens in Wayland (KDE Plasma 6.5.5) and under X11 (XFCE) too. Switching to the GLX backend resolves the crash under X11 and XWayland, but not when using the native Wayland driver. Reverting the following commit on top of Wine-11.2 fixes the problem for me: commit 6802b32b3859e3b1c3e59bdb462d373fcf0608cf opengl32: Fix front buffer emulation glBlitFramebuffer parameters. There is nothing obvious in the terminal. I'm mostly using the binary Nvidia driver, I just happened to bump into this bug. Let me know if you need any further log. I'm attaching here the output of my 'glxinfo -B' and 'eglinfo -B'. I *think* the vga card is properly recognized and used by the OS with the open source driver. Wine-11.2 Mesa 25.3.4 NVIDIA GeForce GTX 1660 SUPER (NVK TU116) -- 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 58226] New: Warnings and notes when compiling from source on Arch Linux (GCC 15.1.1 20250425)
by WineHQ Bugzilla May 3, 2026

May 3, 2026

http://bugs.winehq.org/show_bug.cgi?id=58226 Bug ID: 58226 Summary: Warnings and notes when compiling from source on Arch Linux (GCC 15.1.1 20250425) Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: joni.hilger(a)yahoo.de Distribution: --- Created attachment 78547 --> http://bugs.winehq.org/attachment.cgi?id=78547 Full log of the build (gzip because of size) Hi, when compiling wine from up to date sources (taken from Gitlab today 2025-05-13) I get a few warnings (see wine-build-full.log.gz) This is how I build it: CFLAGS="-march=native -O3 -pipe -fno-plt -fexceptions \ -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security \ -fstack-clash-protection -fcf-protection -ffat-lto-objects" CXXFLAGS="$CFLAGS -Wp,-D_GLIBCXX_ASSERTIONS" LDFLAGS="-Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z,relro -Wl,-z,now \ -Wl,-z,pack-relative-relocs" # Apply flags for cross-compilation export CROSSCFLAGS="-O2 -pipe -g" export CROSSCXXFLAGS="-O2 -pipe -g" export CROSSLDFLAGS="-Wl,-O1" ../wine/configure \ --prefix=/usr \ --libdir=/usr/lib \ --with-x \ --with-wayland \ --with-gstreamer \ --enable-win64 make ../wine/configure \ --prefix=/usr \ --libdir=/usr/lib \ --with-x \ --with-wayland \ --with-gstreamer \ --with-wine64="$srcdir/$pkgname-64-build" make Made the following greps to have more focused logs (thought it might help): grep -C 5 "note: " wine-build-full.log > wine-build-grepped-notes.log grep -C 5 "warning: " wine-build-full.log > wine-build-grepped-warnings.log (full log is called wine-build-full.log.gz) Thank you for your 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 7

[Bug 59001] New: Compiling Wine with -march=znver4 prevents a crash with Deus Ex: Revision [Galaxy Audio]
by WineHQ Bugzilla May 3, 2026

May 3, 2026

http://bugs.winehq.org/show_bug.cgi?id=59001 Bug ID: 59001 Summary: Compiling Wine with -march=znver4 prevents a crash with Deus Ex: Revision [Galaxy Audio] Product: Wine Version: 10.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: shtetldik(a)gmail.com Distribution: --- Created attachment 79730 --> http://bugs.winehq.org/attachment.cgi?id=79730 Crash error I found a slightly weird bug. When running Deus Ex: Revision mod using regular WineHQ build (for Debian testing), it crashes during audio initialization [Galaxy Audio]. See attached screenshot. But when I compile Wine myself using this set up with explicit CPU architecture set to znver4: export CXXFLAGS="-march=znver4" export CFLAGS="$CXXFLAGS" export CROSSCFLAGS="$CXXFLAGS" It doesn't crash. My CPU is AMD Ryzen 9 7950X (Zen 4). I don't see anything clear in the log output. What can the issue be? And do you have any suggestions how to get more diagnostic for this? Build environment: gcc: 15.2.0 gcc-mingw-w64: 15.2.0 -- 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 54784] New: mIRC 7.72 crashes after restoring from application tray
by WineHQ Bugzilla May 3, 2026

May 3, 2026

https://bugs.winehq.org/show_bug.cgi?id=54784 Bug ID: 54784 Summary: mIRC 7.72 crashes after restoring from application tray Product: Wine Version: 8.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dragone2(a)risposteinformatiche.it Distribution: --- Created attachment 74279 --> https://bugs.winehq.org/attachment.cgi?id=74279 Unhandled exception: page fault on read access - mIRC - Wine-staging 8.5 mIRC was running for about 4-5 hours before the crash. It was reduced on the tray and its icon was blinking to notify that there were new messages / activities in channels or private messages. I clicked on it to restore the window and see the messages and wine gave me this backtrace (see the attachment). I was forced to quit mIRC and restart it again. This rarely happens, so it's not a real problem for me, but I don't know if it could help you fix this. Other infos: - Executable path: D:\mIRC\mirc.exe - mIRC Version: 7.72 (the latest one). - mIRC running in portable mode from a specific drive (on Wine, D:\) formatted in NTFS. - mIRC was running using some custom scripts. But this crash never happen on Windows. - Distro: Linux Mint 21.1 with latest updates. - Kernel: 5.15.0-69-generic - Wine infos: Wine build: wine-8.5 (Staging) Platform: i386 (WOW64) Version: Windows 10 - Drive Z: is a drive formatted in BTRFS. - CPU: Intel Core i7-6700 - RAM: 32 GB, when the crash occurred I was using less than 8 GB. -- 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 59714] New: Add support for loading and executing ring-0/ring-1 virtualization drivers (Hypervisor bypass/Custom VBS)
by WineHQ Bugzilla May 3, 2026

May 3, 2026

http://bugs.winehq.org/show_bug.cgi?id=59714 Bug ID: 59714 Summary: Add support for loading and executing ring-0/ring-1 virtualization drivers (Hypervisor bypass/Custom VBS) Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)list.winehq.org Reporter: vidyutsanthosh4(a)gmail.com Distribution: --- Hello developers, First off, thanks for your work on Wine and for all that you do. I want to bring up the topic of one of Wine's limitations related to its ability to run software depending on kernel-mode drivers and hypervisor-based features. Summary Some new applications have requirements of: Custom kernel-mode drivers Virtualization-based protection mechanisms Execution in virtualization-assisted mode (such as usage of VT-x / AMD-V) Such apps fail to start with Wine because: Wine lacks any possibility to load and execute kernel-mode Windows drivers There is no way to access host-level virtualization features Implementation of ntoskrnl is not capable to handle such situations Observed behavior When started: Drivers cannot load successfully or report errors Sometimes, Wine might crash or terminate without reason There are no errors that hint at necessity of virtualization or kernel-mode execution Expected / desired behavior While I know that full support of kernel-mode drivers and hypervisor-level execution is not in Wine's roadmap. It would still be nice to see the following improvements made: Detection and diagnostics Detect if the application tries to: Load kernel-mode driver Utilize virtualization instructions or hypervisor APIs Display an error that explicitly states that such functionality is not supported by Wine Documentation improvements Documentation about: Restrictions around kernel-mode execution Incompatibility of applications dependent on virtualization features Alternatives in running such programs (e.g. KVM-based VM) Research in possible hybrid solutions (long-term) Look into possible ways to integrate with the host OS's virtualization (e.g. KVM), possibly for selected scenarios, even if partially Some kind of experimental flag or limited feature set could be useful for research and tooling purposes Use cases Better diagnostics of the issue would be useful for: Debugging of incompatibilities Running software which requires virtualization or kernel-mode operation Development tools that need low-level control of the system Closing notes I realize that Wine cannot provide kernel-mode and hypervisor-based features. My suggestion rather focuses on: Visibility into the issue Improved handling of such applications Error reporting -- 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