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

[Bug 57909] New: Star Citizen WineWayland Cursor Warping
by WineHQ Bugzilla May 4, 2026

May 4, 2026

https://bugs.winehq.org/show_bug.cgi?id=57909 Bug ID: 57909 Summary: Star Citizen WineWayland Cursor Warping Product: Wine Version: 10.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: mactan(a)edgetransit.dev Distribution: --- star citizen has a cursor warp issue on wayland that spins the camera down to stare at the ground or the cursor's last position on mouse move observed behavior on 10.2 mainline nonstaging winewayland session. cursor flickers instead of being held and the cursor does not warp to center when the interact key is held, and the camera warps to the cursors last position https://youtu.be/rkWaCgDNZeo https://youtu.be/hvb-BOVlsew these are examples of the expected behavior as observed on 10.2 x11 session, when the interact key (default F) is held, the cursor warps to the middle of the screen and the user can move the cursor freely from there. upon release and holding again, cursor warps to center when the key is held https://youtu.be/5cfveNGmHRI https://youtu.be/NKBSWfQrfCw observed behavior on 10.2 wayland xwayland session. the cursor does not warp to center when the interact key is held, and the camera warps to the cursors last position https://youtu.be/9I3g-fbxMUQ https://youtu.be/MAm85csb4Lk observed behavior with patches !7352 !7353 !7368 !7457 !7475 applied. cursor flickers instead of being held and constantly warps to the display center instead of being allowed to move about the screen after the initial warp. attached log with +waylanddrv,+win https://youtu.be/XxRbAljl49w https://youtu.be/RyS8UjzH9hs -- 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 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 56034] New: Borland Turbo CPP 4.5 installer hangs after opening INSTALL.TXT
by WineHQ Bugzilla May 3, 2026

May 3, 2026

https://bugs.winehq.org/show_bug.cgi?id=56034 Bug ID: 56034 Summary: Borland Turbo CPP 4.5 installer hangs after opening INSTALL.TXT Product: Wine Version: 9.0-rc2 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 75680 --> https://bugs.winehq.org/attachment.cgi?id=75680 Patch that fixes the first hang Note that the installer is INSTALL.EXE, not SETUP.EXE. If you click Continue, the installer opens INSTALL.TXT in Notepad. When you close Notepad, the installer should continue, but instead it hangs. If you click Skip, the installer works but hangs after installation. The attached patch fixes the problem, mostly. For some reason you have to click the background after closing Notepad, and the installer still hangs at the end. I don't know how close the patch is to a correct solution. $ sha256sum 'Borland Turbo CPP 4.5 for Windows.7z' 8a6f5797f0af880728421426beacf5e5760701e424d89e14cd714a13e625f2ff -- 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

[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 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 59436] New: Wayland/EGL: Washed-out colors caused by double sRGB conversion on default framebuffer (GL_FRAMEBUFFER_SRGB)
by WineHQ Bugzilla May 3, 2026

May 3, 2026

http://bugs.winehq.org/show_bug.cgi?id=59436 Bug ID: 59436 Summary: Wayland/EGL: Washed-out colors caused by double sRGB conversion on default framebuffer (GL_FRAMEBUFFER_SRGB) Product: Wine Version: 11.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)list.winehq.org Reporter: tpaniaki(a)protonmail.com Distribution: --- Created attachment 80417 --> http://bugs.winehq.org/attachment.cgi?id=80417 Patch Fixes https://bugs.winehq.org/show_bug.cgi?id=59073 Summary When running Wine with the Wayland driver (winewayland.drv) using EGL, colors may appear washed out / desaturated in OpenGL applications. The issue is caused by GL_FRAMEBUFFER_SRGB remaining enabled while rendering to the default framebuffer (FBO 0), leading to a double gamma/sRGB conversion in some Wayland/EGL pipelines. Disabling GL_FRAMEBUFFER_SRGB only when rendering to the default framebuffer fixes the color output. Environment Wine: wine-git (tested on 11.x, reproducible on current master) Backend: winewayland.drv (Wayland native, not XWayland) GPU: AMD (Mesa) Compositor: wlroots-based (qtile Wayland) EGL backend in use Application tested: Roon (Chromium/CEF-based UI, OpenGL rendering) Observed behavior Colors appear faded / washed out Gamma looks incorrect (as if double sRGB conversion occurs) Issue only occurs under Wayland/EGL Colors are correct: Under X11/XWayland Or if GL_FRAMEBUFFER_SRGB is manually disabled for FBO 0 Root cause hypothesis Some Wayland/EGL compositors already perform colorspace handling for the window surface. If GL_FRAMEBUFFER_SRGB remains enabled when rendering to the default framebuffer, the pipeline applies sRGB conversion twice: App → GL_FRAMEBUFFER_SRGB → EGL/Compositor colorspace → Display This results in desaturated output. Minimal fix Disable GL_FRAMEBUFFER_SRGB only when binding the default framebuffer (FBO 0), while preserving the application's requested sRGB state for non-default FBOs. Example patch (conceptual) Inside framebuffer binding path: if (!framebuffer && gl_info->supported[ARB_FRAMEBUFFER_SRGB]) { TRACE("glBindFramebuffer disabling GL_FRAMEBUFFER_SRGB on default framebuffer\n"); glDisable(GL_FRAMEBUFFER_SRGB); } else if (framebuffer && app_framebuffer_srgb_enabled) { TRACE("glBindFramebuffer restoring GL_FRAMEBUFFER_SRGB on non-default framebuffer\n"); glEnable(GL_FRAMEBUFFER_SRGB); } Results Colors become correct under Wayland/EGL No regression observed in tested OpenGL apps Behavior matches X11 output sRGB still works correctly for offscreen FBO rendering -- 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 59073] New: Washed out colors in OpenGL
by WineHQ Bugzilla May 3, 2026

May 3, 2026

http://bugs.winehq.org/show_bug.cgi?id=59073 Bug ID: 59073 Summary: Washed out colors in OpenGL Product: Wine Version: 10.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: opengl Assignee: wine-bugs(a)list.winehq.org Reporter: tpaniaki(a)protonmail.com Distribution: --- Created attachment 79862 --> http://bugs.winehq.org/attachment.cgi?id=79862 glxinfo A recent update in a wine component makes my OpenGL apps all washed out (see screenshot). This affects both X11 and wayland. I'm running qtile on wayland with wlroots0.19. -- 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

[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