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

[Bug 59449] New: FormatMessageW fails for well-formed function call and crashes application
by WineHQ Bugzilla March 6, 2026

March 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=59449 Bug ID: 59449 Summary: FormatMessageW fails for well-formed function call and crashes application 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: and44more(a)gmail.com Distribution: --- Created attachment 80433 --> http://bugs.winehq.org/attachment.cgi?id=80433 C++ code to demonstrate it This isn't really a bug, but more a missing error message. The FormatMessageW (winbase.h) function fails if given the valid error code CRYPT_E_NO_MATCH as an argument (see attached code snippet). It returns 0 indicating an error and does not modify the lpBuffer pointer argument. Applications that assume that FormatMessageW will allocate the error message at the memory address lpBuffer is pointing to will crash (like in my case) if they initalized lpBuffer with 0 before. Technically, this is the fault of the application since it assumed that FormatMessageW will not return an error if given a well-formed function call, but wine is missing the error message in the first place and that should be fixed. I'd also like to propose setting lpBuffer to a pointer to an empty string (null character) instead of not modifying it when FormatMessageW fails. (Create a global empty string variable instead of allocating memory each time). This behavior would adhere to the FormatMessageW documentation and would make applications with missing error checks more fail safe in this case. I'm using linux mint 22.1 with wine 9.0, but I also tested the attached code snippet in linux arch with wine 11.1. -- 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 4

[Bug 59329] New: Erratic behavior of std::rethrow_exception() with DLL runtime
by WineHQ Bugzilla March 6, 2026

March 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=59329 Bug ID: 59329 Summary: Erratic behavior of std::rethrow_exception() with DLL runtime Product: Wine Version: 11.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: ucrtbase Assignee: wine-bugs(a)list.winehq.org Reporter: p(a)perkele.cc Distribution: --- Created attachment 80262 --> http://bugs.winehq.org/attachment.cgi?id=80262 Minimal repro code I have observed various erratic behaviors after use of std::rethrow_exception() in my programs - either crashing or incorrect exception caught. Using DLL or static runtime seems to be a factor - using static runtime instead results in correct behavior for me. Compile and run attached program to test - verified with all Visual Studio versions from 2017 up. Live repro using mainstream software: Install any recent version of foobar2000, switch audio output to any of [exclusive] options, try playing anything - should say "Exclusive mode not allowed", says "Unknown exception" instead. Confirmed on: Fedora 43 / x86_64 / Wine 11.1 macOS 26.2 / ARM host running emulated x86_64 code / Wine 11.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.

1 14

[Bug 55739] New: Native Access 2: permanent loading circle after entering credentials
by WineHQ Bugzilla March 6, 2026

March 6, 2026

https://bugs.winehq.org/show_bug.cgi?id=55739 Bug ID: 55739 Summary: Native Access 2: permanent loading circle after entering credentials Product: Wine Version: 7.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dominikgx(a)gmail.com Distribution: --- Downloaded latest Native Access and entering credentials https://appdb.winehq.org/objectManager.php?sClass=version&iId=41061 -- 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 59462] New: wine-staging fails to build due to unable to find -lvkd3d
by WineHQ Bugzilla March 6, 2026

March 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=59462 Bug ID: 59462 Summary: wine-staging fails to build due to unable to find -lvkd3d Product: Wine Version: 11.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: neotheuser(a)ymail.com Distribution: --- Using the llvm-mingw64 toolchain, I am unable to build Wine using the wine-staging patches. Short build log: tools/winegcc/winegcc -o dlls/wined3d/i386-windows/wined3d.dll --wine-objdir . --cc-cmd="i686-w64-mingw32-clang" -b i686-w64-mingw32 \ -Wl,--wine-builtin -shared ../dlls/wined3d/wined3d.spec dlls/wined3d/i386-windows/adapter_gl.o \ ... [ cut ] ... -lvkd3d libs/dxguid/i386-windows/libdxguid.a dlls/opengl32/i386-windows/libopengl32.a \ tools/winegcc/winegcc -o dlls/wined3d/x86_64-windows/wined3d.dll --wine-objdir . --cc-cmd="x86_64-w64-mingw32-clang" -b \ ... [ cut ] ... dlls/wined3d/resource.res dlls/wined3d/version.res -lvkd3d libs/dxguid/x86_64-windows/libdxguid.a \ ... [ cut ] ... lld: error: unable to find library -lvkd3d clang: error: linker command failed with exit code 1 (use -v to see invocation) ... [ cut ] ... lld: error: unable to find library -lvkd3d winegcc: /home/fedora/dev/llvm-mingw-20251216-ucrt-ubuntu-22.04-x86_64/bin/i686-w64-mingw32-clang failed clang: error: linker command failed with exit code 1 (use -v to see invocation) make: *** [Makefile:176705: dlls/wined3d/i386-windows/wined3d.dll] Error 2 make: *** Waiting for unfinished jobs.... winegcc: /home/fedora/dev/llvm-mingw-20251216-ucrt-ubuntu-22.04-x86_64/bin/x86_64-w64-mingw32-clang failed make: *** [Makefile:176754: dlls/wined3d/x86_64-windows/wined3d.dll] Error 2 I noticed the following: fedora@fedora:~/dev/wine$ ld.lld -lvkd3d ld.lld: error: unable to find library -lvkd3d fedora@fedora:~/dev/wine$ ld.lld -L/usr/lib64 -lvkd3d ld.lld: warning: cannot find entry symbol _start; not setting start address However, adding -L/usr/lib64 to LDFLAGS and even modifying the Makefile within the build directory and forcefully adding it behind `-lvkd3d` the issue still persists and I have no idea how to fix this. Wine from latest `master` branch compiles fine, however Wine with wine-staging (--all specified, all staging patches, fails, not sure which patch yet is the culprit) Toolchain location: https://github.com/mstorsjo/llvm-mingw/releases/tag/20251216 configure line: ../configure CC="clang" CXX="clang++" CPP="clang-cpp" i386_CC="i686-w64-mingw32-clang" i386_CXX="i686-w64-mingw32-clang++" x86_64_CC="x86_64-w64-mingw32-clang" x86_64_CXX="x86_64-w64-mingw32-clang++" --enable-archs=i386,x86_64 --disable-tests --prefix=/home/fedora/wine-out I have not yet tried to build wine-staging with GCC+BFD linker yet. This is Fedora 43. Package relevant files installed from libvkd3d-devel (installed both 32-bit and 64-bit devel packages): /usr/include/vkd3d/vkd3d.h /usr/lib64/libvkd3d.so /usr/lib64/pkgconfig/libvkd3d.pc /usr/lib/libvkd3d.so /usr/lib/pkgconfig/libvkd3d.pc -- 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 6

[Bug 59342] New: Roblox Studio crashes when typing ASCII symbols in search bar of "Find in Place" window when RegEx is enabled
by WineHQ Bugzilla March 6, 2026

March 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=59342 Bug ID: 59342 Summary: Roblox Studio crashes when typing ASCII symbols in search bar of "Find in Place" window when RegEx is enabled 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: eff3ctsb0t(a)gmail.com Distribution: --- Created attachment 80281 --> http://bugs.winehq.org/attachment.cgi?id=80281 Wine debugging log When typing symbols like brackets or question marks inside of the search bar of the "Find in Place" window while having RegEx enabled, Roblox Studio crashes. Wine complains about an unimplemented function within the msvcp140.dll library inside of the debugging log. It is also noteworthy that some ASCII symbols like exclamation marks do not cause a crash. Steps to reproduce: 1. Open a Baseplate template inside of Roblox Studio. 2. Enable the "Find in Place" window by going through the "Window" menu at the top, then through "Script" and then click on "Find in Place". 3. Enable RegEx (.*) inside of the newly spawned window and then type ")" into the search bar of said window. A Wine wrapper program called "Vinegar" can be used to make the process of setting up Roblox Studio a lot easier. Logging into Roblox Studio (and by extension opening a Baseplate) requires a Roblox account though. -- 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 11

[Bug 14713] New: Xara Xtreme 4: Resizing handles not visible
by wine-bugs＠winehq.org March 6, 2026

March 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=14713 Summary: Xara Xtreme 4: Resizing handles not visible Product: Wine Version: 1.1.2 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: info(a)linopus.de Xara Xtreme 4: Resizing handles not visible Xara Xtreme 4, the latest edition of the vector drawing application from Xara (30 days trial available at http://www.xara.com/us/downloads/xtreme/ ), shows no resizing handles when selecting an object. The resizing handles should be visible when clicking an object with the select tool. By contrast, the turning/shearing handles are visible. The turning/shearing handels appear when clicking an object twice with the select tool. Additionally, Bezier handles and points on curves do appear, but in wrong colors (cyan instead of red). Bezier handles and points appear when using the edit shape tool. This is on a wine 1.1.2 install on Ubuntu Linux 8.04 in its standard settings. The same bug is present when using Xara Xtreme X1, which is the thirdlast edition. The bug is also present in earlier versions of wine (e.g. 0.9.56) and CrossOver (e.g. 7.0.1). Yours sincerely Tobias Hilbricht -- 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 12

[Bug 58505] New: Odd windows management behaviour in later dev versions
by WineHQ Bugzilla March 6, 2026

March 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=58505 Bug ID: 58505 Summary: Odd windows management behaviour in later dev versions Product: Wine Version: 10.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kg.hammarlund(a)gmail.com Distribution: --- I run a geneaology database program written for windows under wine. It runs fine on v10.0 (stable) and on dev versions up to 10.4. From v10.5 and upwards, including v1012, I'm encountering an odd issue. When opening a search window, this window opens in the background instead of on top of the main window. I then have to move or resize the main window in order to highilght the search window and fill in the search data. But this only happens the first time I open the search window. Next time it opens in the foreground. If I untick the box "Allow the window manager to control the windows" in winecfg > graphics, the search window opens expected. But this solution has its drawbacks. -- 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 28

[Bug 59455] New: Disappearing TreeView items on TVM_INSERTITEM+TVM_EXPAND+TVM_EDITLABEL
by WineHQ Bugzilla March 6, 2026

March 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=59455 Bug ID: 59455 Summary: Disappearing TreeView items on TVM_INSERTITEM+TVM_EXPAND+TVM_EDITLABEL Product: Wine Version: 11.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)list.winehq.org Reporter: p(a)perkele.cc Distribution: --- Created attachment 80442 --> http://bugs.winehq.org/attachment.cgi?id=80442 Minimal repro program See attached program. 1. TVM_INSERTITEM 2. TVM_EXPAND on parent item 3. TVM_EDITLABEL on new item Result: parent item disappears for the duration of editing Intended result: parent item should remain visible -- 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 24851] New: Explorer++ treeview shows plus signs even when a folder contains no subfolders
by wine-bugs＠winehq.org March 6, 2026

March 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=24851 Summary: Explorer++ treeview shows plus signs even when a folder contains no subfolders Product: Wine Version: 1.3.5 Platform: x86-64 URL: http://www.explorerplusplus.com/download OS/Version: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: RandomAccountName(a)mail.com Created an attachment (id=31446) --> (http://bugs.winehq.org/attachment.cgi?id=31446) terminal output On Windows, the little plus signs for expanding folders in the treeview don't appear next to folders that contain no subfolders (and thus, nothing to expand). In Wine, such folders still have the plus sign even though it doesn't do anything. Native comctl32 didn't help. -- 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.

2 14

[Bug 16957] New: CreateProcess handles are inherited even when bInheritHandles=FALSE
by wine-bugs＠winehq.org March 6, 2026

March 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=16957 Summary: CreateProcess handles are inherited even when bInheritHandles=FALSE Product: Wine Version: 1.1.2 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: kernel32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: ben(a)salilab.org Created an attachment (id=18729) --> (http://bugs.winehq.org/attachment.cgi?id=18729) test.c The attached file uses CreateProcess to create a subprocess (gzip in this case) with redirected standard output. In order for this to work properly, the output handle created in this code must be inherited by the subprocess - thus the bInheritHandles argument to CreateProcess must be TRUE. And indeed if this program is compiled to test-true.exe, a simple text file 'test.in' and the gzip binary are placed in the same directory, and then test-true.exe is run, it successfully produces the output test.gz. If the TRUE argument is switched to FALSE and the file is compiled again to test-false.exe, when the program is run in the same way on a 'real' Windows sytem (32 bit Vista Business in this case) the following is output: gzip: stdout: Bad file descriptor This is also fine and expected, since the output file handle was not passed to gzip. *However* if the same test-false.exe program is run with Wine (the Fedora 10 wine-core-1.1.12-1.fc10.i386 package in this case) it runs in just the same way as test-true.exe, generating the test.gz output. This suggests to me that the bInheritHandles argument is ignored by Wine. As stated, this is a minor bug but it would be nice if Wine behaved the same way as Windows here. (In our case we discovered this problem after we tested our program successfully under Wine, but then had it fail on a real Windows system.) I am not familiar with the code, but hopefully it should be straightforward enough to provide the subprocess with invalid handles if bInheritHandles=FALSE? -- 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 17