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

[Bug 59672] winhttp: DOAXVV fails with error 9003 at title screen

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59672 --- Comment #10 from axis6404(a)proton.me --- I noticed a recurring discrepancy in the logs, such as around line 1414 of doaxvv9003-20260418.txt. Both winhttp:read_data and the "dwStatusInformationLength" in WINHTTP_CALLBACK_STATUS_READ_COMPLETE(0x80000) are occasionally 8193, even though only 8192 bytes were reported as available. 06e8:trace:winhttp:WinHttpQueryDataAvailable ... ... 06e8:trace:winhttp:query_data_available 8192 bytes available ... 06e8:trace:winhttp:WinHttpReadData ..., ..., 8193 (sample code: https://learn.microsoft.com/windows/win32/api/winhttp/nf-winhttp-winhttpque…) ... ... 06e8:trace:winhttp:read_data 8193 bytes read <--- here!!!!!!!!!!!! 06e8:trace:winhttp:send_callback ..., 0x80000, ..., 8193, ... <--- here!!!!!!!!!!!! I suspect 8192 is the correct value. Could you check if this 1-byte overflow is causing the issue? -- 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.

April 30, 2026

[Bug 59640] Roblox Studio's 3D-viewport turns blank or flickers (VK_SUBOPTIMAL_KHR)

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59640 --- Comment #1 from eff3ctsb0t(a)gmail.com --- Still occurs on Wine 11.7. -- 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.

April 30, 2026

[Bug 59090] Roblox Studio opens to a black window on native OpenGL renderer

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59090 --- Comment #8 from eff3ctsb0t(a)gmail.com --- Roblox seems to have removed the native OpenGL renderer from the latest version of Studio entirely, so I guess there is nothing to fix here. -- 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.

April 30, 2026

[Bug 59711] unlock_fd: UnlockFile returns ERROR_LOCK_VIOLATION (33) instead of ERROR_NOT_LOCKED (158) when no matching lock is held

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59711 --- Comment #1 from Zanie Blue <bugzilla-wine(a)accounts.zanie.blue> --- Note I reproduced this on Wine 9 in CI, but the issue appears to be present on the master branch on GitLab. -- 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.

April 30, 2026

[Bug 59711] New: unlock_fd: UnlockFile returns ERROR_LOCK_VIOLATION (33) instead of ERROR_NOT_LOCKED (158) when no matching lock is held

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59711 Bug ID: 59711 Summary: unlock_fd: UnlockFile returns ERROR_LOCK_VIOLATION (33) instead of ERROR_NOT_LOCKED (158) when no matching lock is held Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: ntdll Assignee: wine-bugs(a)list.winehq.org Reporter: bugzilla-wine(a)accounts.zanie.blue Distribution: --- Calling `UnlockFile` (or `NtUnlockFile`) for a region that the handle does not currently have a lock on returns `ERROR_LOCK_VIOLATION` (33) under Wine. It should return `ERROR_NOT_LOCKED` (158) instead. This breaks Rust's `std::fs::File::unlock`, which deliberately calls `UnlockFile` twice on every release (to handle the documented case of a handle holding both an exclusive and a shared lock on the same region), and explicitly tolerates `ERROR_NOT_LOCKED` on the second call but propagates any other error [1]. The result is a spurious "Lock violation" error reported by Rust programs that use `File::unlock` under Wine. I encountered this downstream while adding a Wine integration test in uv [2]. In `server/fd.c`, `unlock_fd()` calls `set_error(STATUS_FILE_LOCK_CONFLICT)` when no lock with the exact (start, end) is found on the handle [3]. Per `dlls/ntdll/error.h` that status maps to `ERROR_LOCK_VIOLATION` (33) [4], whereas the semantically correct status for "no such lock" is `STATUS_RANGE_NOT_LOCKED`, which maps to `ERROR_NOT_LOCKED` (158) [5, 6]. [1] https://github.com/rust-lang/rust/blob/f53b654a8882fd5fc036c4ca7a4ff41ce324… [2] https://github.com/astral-sh/uv [3] https://gitlab.winehq.org/wine/wine/-/blob/master/server/fd.c#L1566-1581 [4] https://gitlab.winehq.org/wine/wine/-/blob/master/dlls/ntdll/error.h#L449 [5] https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-erref/596a… [6] https://gitlab.winehq.org/wine/wine/-/blob/master/dlls/ntdll/error.h#L491 -- 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.

April 30, 2026

[Bug 59690] Both Command & Conquer 3 and Command & Conquer Red Alert 3 show the same kind of error

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59690 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick(a)piezo-forte.be --- Comment #11 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, Please read the link given in comment #3 as it contains the instructions to do a regression test. What you did is compile a local git version of wine and run it. Being able to do that is a requirement of a regression test, but is not the regression test. The regression test involves repeating that, in succession, indicating if the issue was present or not at each iteration, until the git bisect command tells which commit is the bad commit. Now that you have a copy of the git source that you can compile yourself, you need to follow the instructions starting from there to perform the regression test: https://gitlab.winehq.org/wine/wine/-/wikis/Regression-Testing#running-the-… Please read the whole instruction page thoroughly, as we won't be able to help you by holding your hand for the whole process on this Bugzilla. If you need such help, you should ask on the forums (link on the top most header bar on this page). Regards. -- 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.

April 30, 2026

[Bug 55653] Logitech Extreme 3d Joystick has axes mapped incorrectly

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=55653 --- Comment #24 from Ray Culp <alias3.aerospace239(a)passinbox.com> --- (In reply to rens from comment #14) > Hi > Thx for posting > > What is a usrmerged Linux install? > > I tested the install on side and Ubuntu, desktop version > > No issues there. > > Plz explain so I can try to fix it. > > Best Yes, I will explain as well as I can with my limited knowledge. :-) "usrmerge" is a change in the Linux filesystem that was proposed around 2012 and introduced gradually across different distros over the last ten years or so. Traditional directories like /bin, /sbin, and /lib were changed to symlinks pointing to /usr/bin, /usr/sbin and /usr/lib. For example, I think it only became the default on Ubuntu on 2019. If you copy or move a file to /sbin on a "usrmerged" system, it gets rerouted to /usr/sbin without any problems. The problem arises when you unpack an archive that contains the directory structure /sbin/somefile. Then the symlink /sbin is overwritten with an actual physical directory called /sbin. This destroys the symlink. When the system boots, it tries to run /sbin/init (which should point to /usr/sbin/init). But now it's gone. (In reply to rens from comment #15) > Not side, opens use which distro are you seeing this? This is on Linux Mint 22.3, which is based on Ubuntu 24.04 LTS. (In reply to mata from comment #21) > Oh, come on, your install script just obviously damaged someones system by > doing stupid thing Don't blame rens please. It's not his fault. And he made a great utility that actually works. <3 I messed up my own computer because ultimately I decided to run the script, and I lacked the knowledge to see that it would overwrite the symlink. If I wanted my OS to take me by the hand, I would have bought an Apple. :-) -- 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.

April 30, 2026

[Bug 59690] Both Command & Conquer 3 and Command & Conquer Red Alert 3 show the same kind of error

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #10 from Scott Kidman <scottkidman(a)protonmail.com> --- Created attachment 80847 --> http://bugs.winehq.org/attachment.cgi?id=80847 Regression Test for Red Alert 3 My first attempt. I just entered /wine-git/wine ~/path/to/game/Ra3.exe Tell me how I did, but be lenient, it's my first time after all. The Wine version is wine-11.7-164-g1535a941198. -- 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.

April 30, 2026

[Bug 59710] Age of Empires II crashes on startup, has since version 5 of wine, continue in 8, 10, and 11 (latest)

by WineHQ Bugzilla

April 30, 2026

[Bug 59701] Age of Empires II segfaults for some reason on the LTS version of Debian. (11.1) (also used by Devuan 4)

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59701 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xcrt3(a)bobmail.info --- Comment #43 from Alexandre Julliard <julliard(a)winehq.org> --- *** Bug 59710 has been marked as a duplicate of this bug. *** -- 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.

April 30, 2026