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

[Bug 60132] New: Regression: screen offset on borderless windowed mode in Final Fantasy XIV

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=60132 Bug ID: 60132 Summary: Regression: screen offset on borderless windowed mode in Final Fantasy XIV Product: Wine Version: 11.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)list.winehq.org Reporter: kokoseij(a)gmail.com Target Milestone: --- Distribution: --- Created attachment 81714 --> http://bugs.winehq.org/attachment.cgi?id=81714 trace log of a "bad" build launching the game with WINEDEBUG="-all,trace+win,trace+x11drv" Reproduction Steps: 1. Disable Graphics option "Allow the window manager to decorate the windows" on winecfg 2. launch the critically acclaimed MMORPG Final Fantasy XIV, with XIVLauncher 3. If not already done so, enable borderless fullscreen on in-game config, and repeat step 2 Symptoms: The game screen is rendered slightly offset towards bottom right; about as much as a window border and title bar generated by Wine. Empty areas appear black. The cursor position is not affected by this, meaning the hardware cursor doesn't align where the click event happens. When toggling software cursor in-game, the cursor position shifts as much as the screen does. Checking with xwininfo shows the window size matches the screen size. From the trace log, it seems like FFXIV creates a small window with decorations, resizes it to match the screen size, and then removes the decoration. Wine with a problematic commit seems to not honour the new Notably, the DXVK debug info overlay is also offset, which sounds like the entire framebuffer may be getting shifted altogether. This bug was introduced with commit `b868cd31d6b5fb0a5e09e45658c4901bb6d1c09a` (win32u: Move client surface rect computation out of the drivers.), and still present as of 11.14 release. The bug was reproduced on a following setup: * Fedora Linux 44 x86_64 * Xfce 4.20 * X.Org X Server 1.21.1.24 * Vanilla Wine commit b868cd31d6b5fb0a5e09e45658c4901bb6d1c09a, and 11.14 release * DXVK v3.0.2 The game launch environment, if relevant, is: * XIVLauncher v7.0.20.0 * FFXIV version 2026.07.16.0001.0000 Lastly, the attached trace log includes the launcher as well. Please start reading around the part where `ffxiv_dx11.exe` is mentioned by DXVK. -- 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.

Aug. 5, 2026

[Bug 60131] Changing a distribution when reviewing test results, accepts the new distribution anyway

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=60131 --- Comment #1 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- Okay... After accepting another test result which used this "new" distro, and changing it to the existing distro, the "new" distro was deleted by the AppDB. Bizarre behaviour. -- 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.

Aug. 5, 2026

[Bug 60131] New: Changing a distribution when reviewing test results, accepts the new distribution anyway

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=60131 Bug ID: 60131 Summary: Changing a distribution when reviewing test results, accepts the new distribution anyway Product: WineHQ Apps Database Version: unspecified Hardware: x86-64 URL: https://appdb.winehq.org/objectManager.php?bIsQueue=fa lse&bIsRejected=false&sClass=distribution&iId=2085&sAc tion=view&sTitle=View+Distribution OS: Linux Status: NEW Severity: normal Priority: P2 Component: appdb-unknown Assignee: wine-bugs(a)list.winehq.org Reporter: imwellcushtymelike(a)gmail.com Target Milestone: --- Distribution: --- For reasons unknown, people love to submit distributions that are already listed. When reviewing test results, you can remove the details of the "new" distro from the fields, and select the existing distro. After accepting the test result, the "new" distro is created anyway. This new distro now claims to have a test result, though there are none. I assume this is because the accept/reject of this distro is linked directly to the test result. This is obviously not ideal. The counter of 1 for an empty distro may be an additional issue. There may be a number of empty distros like this, but the list isn't currently sortable by number of test results. -- 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.

Aug. 5, 2026

[Bug 60130] GetProcAddress() crashes with a stack overflow when a DLL export forwards to its own module name

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=60130 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download, source, testcase URL| |https://bugs.winehq.org/att | |achment.cgi?id=81711 -- 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.

Aug. 5, 2026

[Bug 60130] GetProcAddress() crashes with a stack overflow when a DLL export forwards to its own module name

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=60130 --- Comment #2 from realmaitreal(a)deadmail.lat --- Created attachment 81713 --> http://bugs.winehq.org/attachment.cgi?id=81713 Windows 10 x64 output for the same test (returns NULL, error 193) -- 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.

Aug. 5, 2026

[Bug 60130] GetProcAddress() crashes with a stack overflow when a DLL export forwards to its own module name

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=60130 --- Comment #1 from realmaitreal(a)deadmail.lat --- Created attachment 81712 --> http://bugs.winehq.org/attachment.cgi?id=81712 the stock wine-11.14 run above -- 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.

Aug. 5, 2026

[Bug 60130] New: GetProcAddress() crashes with a stack overflow when a DLL export forwards to its own module name

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=60130 Bug ID: 60130 Summary: GetProcAddress() crashes with a stack overflow when a DLL export forwards to its own module name Product: Wine Version: 11.14 Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)list.winehq.org Reporter: realmaitreal(a)deadmail.lat Target Milestone: --- Created attachment 81711 --> http://bugs.winehq.org/attachment.cgi?id=81711 sources + both binaries, sha1 b5346d4acdd636eae5fd13a8a986a030f805b48e A DLL that forwards an export to its own module name makes GetProcAddress() recurse until the thread stack is exhausted, killing the process. Attached is a minimal testcase (source included, ~20 lines): selffwd.dll - one export, "test_func", a forwarder to "SELFFWD.test_func", i.e. to the DLL's own base name fwdloop.exe - LoadLibraryA("selffwd.dll") then GetProcAddress(mod, "test_func") Steps to reproduce: 1. put selffwd.dll and fwdloop.exe in the same directory 2. wine fwdloop.exe Expected (Windows 10 x64, see windows-output.txt): GetProcAddress returns NULL, GetLastError() is 193 (ERROR_BAD_EXE_FORMAT), the program exits normally. Actual (wine-11.14, clean prefix, no DLL overrides, see wine-output.txt): err:virtual:virtual_setup_exception stack overflow ... and the process dies before GetProcAddress returns. find_forwarded_export() in dlls/ntdll/loader.c resolves the forwarder's module by base name, which finds the forwarding module itself, and recurses on the same export with unchanged arguments. Nothing bounds the chain. This is not specific to the testcase. It affects the common "proxy DLL" pattern, where a stub in an application's directory forwards its exports on to the system copy of the same name. I hit it originally with a third-party plugin DLL for 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.

Aug. 5, 2026

[Bug 60129] strftime missing support for %O modifier (breaks Python 3.15 calendar module)

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=60129 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |minor Component|msvcrt |ucrtbase -- 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.

Aug. 5, 2026

[Bug 60129] strftime missing support for %O modifier (breaks Python 3.15 calendar module)

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=60129 --- Comment #3 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- Created attachment 81710 --> http://bugs.winehq.org/attachment.cgi?id=81710 Stub patch Stub stops the error but won't fix anything. "winetricks ucrtbase2019" is a workaround. -- 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.

Aug. 5, 2026

[Bug 59067] some Unreal Engine games don't render correctly with opengl renderer

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59067 --- Comment #6 from Stian Low <wineryyyyy(a)gmail.com> --- Created attachment 81709 --> http://bugs.winehq.org/attachment.cgi?id=81709 creenshots renderer=gl bugged but not for vulkan for opening gameplay for wine-11.14-702e44767a8 (In reply to Stian Low from comment #5) > Otherwise this bug may be closed as invalid and not a duplicate of Frostpunk > dark rendering bug fixed via MR-10567. Cancel that. Gameplay indeed shows darker rendering for renderer=gl but not vulkan and not fixed by MR-10567 and seems like a separate bug. MR-10567 involves SRGB corrections including for gl specifically so I'll take a closer look if it may be related. It may be indeed an Unreal Engine bug so please provide any others if you remember. Thanks for 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.

Aug. 5, 2026