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

[Bug 44820] New: Processes might terminate with incorrect exit code due to race-condition when threads are killed during shutdown
by wine-bugs＠winehq.org Feb. 25, 2026

Feb. 25, 2026

https://bugs.winehq.org/show_bug.cgi?id=44820 Bug ID: 44820 Summary: Processes might terminate with incorrect exit code due to race-condition when threads are killed during shutdown Product: Wine Version: 3.4 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, to track https://github.com/wine-staging/wine-staging/tree/master/patches/ntdll-Thre… Unfortunately there is no further information/details, I just found this: https://wine-staging.com/news/2015-03-07-release-1.7.38.html -> https://github.com/wine-staging/wine-staging/blob/v1.7.38/debian/changelog --- quote --- * Added patch to fix race-condition when threads are killed during shutdown. --- quote --- https://github.com/wine-staging/wine-staging/blob/master/patches/ntdll-Thre… --- quote --- When exit_thread is executed, nb_threads is decremented before the thread is fully shutdown. When another thread runs ExitProcess() this will cause a SIGQUIT signal to all threads, effectively decrementing nb_threads twice. The process will terminate with a wrong exitcode then because the refcount reaches zero too early. Currently Wine has no locking protection of LdrShutdownProcess(), so it can only be executed safely when all other threads have terminated before. Most likely there are more Wine bugs in this area, but the attached patch should fix the most critical one (messed up refcounting of threads) for now. --- quote --- Sadly no applications are mentioned that could be used to validate the problem. $ wine --version wine-3.4 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.

2 7

[Bug 58511] New: Unimplemented sub function KeAcquireGuardedMutex from ntoskrnl.exe
by WineHQ Bugzilla Feb. 25, 2026

Feb. 25, 2026

http://bugs.winehq.org/show_bug.cgi?id=58511 Bug ID: 58511 Summary: Unimplemented sub function KeAcquireGuardedMutex from ntoskrnl.exe Product: Wine Version: 10.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: indigosky30(a)gmail.com Distribution: --- Im trying to figure out why a game that was running a few weeks ago normally doesnt work anymore (gunbound). First, they added Anticheat (SARD), this might be the reason why it fails but trying to debug I found the problem comes from an unimplemented Windows kernel function (note this is an old function introduced in 2003). ------------------------------- 0320:fixme:advapi:DecryptFileW (L"C:\\Program Files (x86)\\GunBoundWC\\game\\sard\\sard_1.0.1.17.sys", 00000000): stub 0320:fixme:ntdll:NtLoadDriver (L"\\Registry\\Machine\\SYSTEM\\CurrentControlSet\\Services\\sard_1.0.1.17"), stub! 0320:fixme:ntdll:NtUnloadDriver (L"\\Registry\\Machine\\SYSTEM\\CurrentControlSet\\Services\\sard_1.0.1.17"), stub! wine: Call from 00006FFFFFC66438 to unimplemented function ntoskrnl.exe.KeAcquireGuardedMutex, aborting wine: Unimplemented function ntoskrnl.exe.KeAcquireGuardedMutex called at address 00006FFFFFC66438 (thread 033c), starting deb ugger... 0350:fixme:dbghelp:elf_search_auxv can't find symbol in module 0350:fixme:dbghelp:elf_search_auxv can't find symbol in module wine: Call from 00006FFFFFC66438 to unimplemented function ntoskrnl.exe.KeAcquireGuardedMutex, aborting 0328:err:service:process_send_command service protocol error - failed to read pipe r = 0 count = 0! ---------------------- Looking at the call inside the ntoskrn routine, KeAcquireGuardedMutex isnt implemented in WINE (not found here) https://source.winehq.org/WineAPI/ntoskrnl.html, but can be found in the Windows kernel (https://gist.github.com/ntddk/56784b8da89f228f5f1d) Im wondering if implementing the function in WINE would solve the problem? Anyhow hoping someone more knowledgeable sheds some light on this 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.

2 4

[Bug 37664] New: CUDA encoder does not work on MediaCoder x64 0.8.33 build 5680
by wine-bugs＠winehq.org Feb. 25, 2026

Feb. 25, 2026

https://bugs.winehq.org/show_bug.cgi?id=37664 Bug ID: 37664 Summary: CUDA encoder does not work on MediaCoder x64 0.8.33 build 5680 Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rickardj42(a)gmail.com Distribution: --- Created attachment 50128 --> https://bugs.winehq.org/attachment.cgi?id=50128 Screenshot of the error message In MediaCoder x64 0.8.33 build 5680 attempting to select GPU encoder causes error "No supported acceleration hardware detected", dispite the presence of an NVidia GeForce 750ti in my system. Attempting to force GPU encoding using CUDA encoder results in Error (14) on all items(general encoder error). -- 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 12

[Bug 58439] New: REGRESSION: trying to edit a text field immediately causes the previous content to be completely erased
by WineHQ Bugzilla Feb. 25, 2026

Feb. 25, 2026

http://bugs.winehq.org/show_bug.cgi?id=58439 Bug ID: 58439 Summary: REGRESSION: trying to edit a text field immediately causes the previous content to be completely erased Product: Wine Version: 10.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: scallegari(a)arces.unibo.it Distribution: --- Hi, I am recently experimenting a regression and even if I cannot say in which version it was introduced, I am almost sure it is not the last one (but before) and that it is indeed a regression (a few month ago the behavior was different). I am working with a software called LTspice (that is closed source but free, which surely helps repro) and available from https://www.analog.com/en/resources/design-tools-and-calculators/ltspice-si…. Incidentally, the developers of this code have traditionally been wine-friendly (even if they do not offer a linux version of their code, neither they provide support for running it in wine, they have tried to ensure that it could be used with wine). This software is a circuit simulator with a schematic capture component. You can pick and place components and edit the values of their parameters using some dialog boxes. Often there are multiple things that can be tuned and the dialog box is arranged as a sort of a table, where some cells are editable. In order to adjust things, until some simulation results are satisfactory, it is common to modify some parameters multiple times and in doing so it is good to be able to edit the previous value. Unfortunately, in recent times it has become impossible to do so when running the software with wine. As soon as you try to modify a value, the value disappears and you remain with an empty field to be filled from scratch. -- 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 57662] New: Cashbooks Complete does not render correctly
by WineHQ Bugzilla Feb. 25, 2026

Feb. 25, 2026

https://bugs.winehq.org/show_bug.cgi?id=57662 Bug ID: 57662 Summary: Cashbooks Complete does not render correctly Product: Wine-staging Version: 10.0-rc5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winehq.tabloid372(a)passmail.net CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- The binary is free to download here: https://www.acclaimsoftware.com.au/download/ with no significant depends (access runtime is all). The main window renders using `DISPLAY=:0 wine ..` once a `XWayland&` instance is running otherwise using the native wayland drv backend to `wine-10.0-rc5 (Staging)` results in multiple windows being created that do not show anything. Overall this is a extremely simple program so it is unclear why it doesn't run, I couldn't see anything obvious in the logs. Only a excessive number of `vkd3d:0150:fixme:fold_cast Cast from uint to int2.` prints. -- 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 38

[Bug 59318] New: Graphic problem
by WineHQ Bugzilla Feb. 24, 2026

Feb. 24, 2026

http://bugs.winehq.org/show_bug.cgi?id=59318 Bug ID: 59318 Summary: Graphic problem Product: Wine Version: 11.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: halloalle14(a)gmail.com Distribution: --- Created attachment 80249 --> http://bugs.winehq.org/attachment.cgi?id=80249 Terminal messages win7 program: MMANA-GAL basic version actual http://gal-ana.de/basicmm/en/#18 OS linux LMDE7 actual Error: Sub-window has no graphic anymore since LMDE7 Last working WINE version under LMDE6 unknown. PC identical Testet with Wine 10 stable, 11 stable, 11.1 devel and oldest possible 8.0.2 stable. Every one new installed after clean up. +++++ MMANA-GAL basic has two pattern outputs. First one is the 2D far field plot tab. This one works. Second one is the small icon on top right, the 3D far field plot. This one does not work any more. The window pops up allows to choose 5°-setting and after enter a blank window appears instead a graphic. Export does not work too. The graphic file is corrupted and cant be opened. Farfield plot is a own sub program and this .exe was also marked to be run under win7 in the config like all other too. Other functions in the program seems to work like in the past. ++++++ I tried to install this regression SW using the commands from WINEhq website but was not able to run it just got a lot of useless error messages. +++++ Attached some maybe useful outputs from the terminal commands ++++++ 73 Bert -- 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 58972] New: error in mgest (gdiplus and C++ 2003 libraries)
by WineHQ Bugzilla Feb. 24, 2026

Feb. 24, 2026

http://bugs.winehq.org/show_bug.cgi?id=58972 Bug ID: 58972 Summary: error in mgest (gdiplus and C++ 2003 libraries) Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)list.winehq.org Reporter: grandrodri3(a)gmail.com Distribution: --- Created attachment 79681 --> http://bugs.winehq.org/attachment.cgi?id=79681 error on terminal with mgest program Hey guys, I was looking at CRM and accounting programs and I happened to want to try this program called mgest (download link at the end of this report), but it's giving me an error (the Wine debugger pops up on both Windows 10 and 11). Looking at the libraries, it has gdiplus and libraries from the old C++ 2003. I tried installing C++ through winetricks but got a decompression error. Any ideas on how to get this program to run? And... could you take a look at it? Cheers download of mgest: http://mgest.com/formulario-de-descarga-mgest-lite/ -- 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 59333] New: VNyan leaks memory (race in __wine_syscall_dispatcher $rsp switching breaks Unity GC)
by WineHQ Bugzilla Feb. 24, 2026

Feb. 24, 2026

http://bugs.winehq.org/show_bug.cgi?id=59333 Bug ID: 59333 Summary: VNyan leaks memory (race in __wine_syscall_dispatcher $rsp switching breaks Unity GC) Product: Wine Version: 11.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: ntdll Assignee: wine-bugs(a)list.winehq.org Reporter: lina(a)lina.yt Distribution: --- Created attachment 80270 --> http://bugs.winehq.org/attachment.cgi?id=80270 Debug & gdb logs VNyan (https://suvidriel.itch.io/vnyan) under recent versions of Wine starts leaking memory at a random time (from minutes to hours after startup). It took a few days of debugging and reverse engineering, but I tracked this down to an issue with Unity's GC observing a weird stack switch in Wine. For reference, Proton 8-5 seems to be fine and GE Proton 10-15 triggers the problem. The problem reproduces with plain `wine-11.0 (Staging)` (wine-11.0-2.fc43.x86_64 from Fedora 43), which is what I used for the traces in this bug. This is the Win32 threads code in the Unity fork of bdwgc: https://github.com/Unity-Technologies/bdwgc/blob/unity-master/win32_threads… Normally, bdwgc will use SuspendThread() on all application threads (see GC_suspend()) and then call GetThreadContext() to retrieve the thread context. It then uses the sp value to determine which stack segment to mark as roots for GC. The logic is complex and there is a safety check in case sp is out of bounds (then it collects the whole stack). However, on line 1695 above, sp is blindly subtracted from thread->stack_base and used to compute the stack usage in bytes, without any bounds checks. This means that when sp ends up above the stack, the subtraction overflows and returns a bogus huge stack size. This ends up throwing off the GC collection threshold, and the GC never runs again. During a normal stop-the-world GC ([1] in vnyan_debug.txt), all threads are stopped with $rip in Windows code (0x00006fffffxxxxxx) (other than the main thread which is in 0x000000018xxxxxx because I patched the Mono DLL to not relocate, for consistent debugging). Most threads are in NtWaitForSingleObject or NtWaitForAlertByThreadId, a couple in NtDelayExecution/NtNotifyChangeKey/NtUserMsgWaitForMultipleObjectsEx/NtWaitForMultipleObjects, and two threads in a mmdevapi wine_unix_call(). When the bug occurs, one thread is caught in the middle of UNIX code ([2] in vnyan_debug.txt). The stack pointer changes from this (pre-bug): Thread 82 (Thread 32.0x2c0): $201 = 0x7a8bf3e8 To this (during bug): Thread 82 (Thread 32.0x2c0): $295 = 0x12938eab0 The GC logs this warning (needs patches to enable debug logs): --> Marking for collection #2607 after 3617216 allocated bytes Marked from 150 dirty pages GC Warning: Thread stack pointer 000000012938EAB0 out of range, pushing everything Pushed 34 thread stacks And then the GC stops working. In the particular repro logged, rip is pointing here in __wine_syscall_dispatcher (it's usually within a few instructions of this area): https://github.com/wine-mirror/wine/blob/db11d0fe6a169c457e23d007e20404643d… This means that is_inside_syscall() returned false and allowed the thread state to be captured directly from native thread state. This is defined as: static inline BOOL is_inside_syscall( ULONG_PTR sp ) { return ((char *)sp >= (char *)ntdll_get_thread_data()->kernel_stack && (char *)sp <= (char *)get_syscall_frame()); } Just a few lines before the instruction the thread was stopped in: "leaq 0x70(%rcx),%rsp\n\t" /* %rsp > frame means no longer inside syscall */ Indeed, %rsp as seen by the user app is 0x70 into syscall_frame (which is 0x12938ea40). Later in the function the stack is switched to the proper user stack: /* switch to user stack */ "movq 0x88(%rcx),%rsp\n\t" I believe when a thread is stopped in the entire range between those two instructions, user code can observe %rsp set to a bogus value that should not be possible. This code was moved around by commit 245e8cedf059 and previously introduced by 0a5f7a71036. I'm not sure why %rsp is being set to point into &frame->rip instead of simply restoring it to the user stack pointer earlier. -- 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 44

[Bug 15346] New: Winamp disappears when you move it's location
by wine-bugs＠winehq.org Feb. 24, 2026

Feb. 24, 2026

http://bugs.winehq.org/show_bug.cgi?id=15346 Summary: Winamp disappears when you move it's location Product: Wine Version: 1.1.5 Platform: All OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: homerhomer(a)gmail.com Created an attachment (id=16178) --> (http://bugs.winehq.org/attachment.cgi?id=16178) DwmSetWindowAttribute error Sort of a silly bug, basically once winamp is up and running, if you click on the title bar and move it around winamp disappears. To make sure that the bug happens make sure to swirl it around a couple of times. ( A Swirly if you will ) Attached I also noticed this when running winamp manually at startup. This may be related. but then I move winamp and it disappears I don't get any more error messages. So I'm not sure. I appreciate the good work Thank you I'm running Ubuntu 8.04, Wine 1.1.5, AMD64 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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 48

[Bug 49583] New: Assassin's Creed Odyssey displays black bars on top and bottom.
by WineHQ Bugzilla Feb. 24, 2026

Feb. 24, 2026

https://bugs.winehq.org/show_bug.cgi?id=49583 Bug ID: 49583 Summary: Assassin's Creed Odyssey displays black bars on top and bottom. Product: Wine Version: 5.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: GloriousEggroll(a)gmail.com Distribution: --- Created attachment 67739 --> https://bugs.winehq.org/attachment.cgi?id=67739 AC Odyssey black bar fix It's been a long known issue that AC: Odyssey renders with black bars on the top and bottom of the screen (see screenshot 1). Derek Lesho came up with a stub patch that both fixed this -and- allowed STEEP to run (it would not display previously). That patch can be found here: https://github.com/GloriousEggroll/proton-ge-custom/blob/5.12-GE-1/patches/… Recently, the relevant function QueryDisplayConfig was implemented, however it did not contain some of the changes Derek's patch adds. This allowed steep to work, however AC: Odyssey still retained the black bar issue. I modified Derek's patch by adding the relevant parts to QueryDisplayConfig, and removing the relevant flag checks (Derek's patch did this previously), and this allowed AC: Odyssey to render properly without the black bars. (see screenshot 2). The patch is hacky but may provide more information towards fixing this properly. -- 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 9