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

[Bug 52254] New: Cold Steel Subs: Application is not transparent (relies on DwmExtendFrameIntoClientArea)
by WineHQ Bugzilla Sept. 11, 2026

Sept. 11, 2026

https://bugs.winehq.org/show_bug.cgi?id=52254 Bug ID: 52254 Summary: Cold Steel Subs: Application is not transparent (relies on DwmExtendFrameIntoClientArea) Product: Wine Version: 7.0-rc2 Hardware: x86-64 URL: https://zerofield.net/2020/09/30/hajimari-no-kiseki-sp readsheet-translation/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dwmapi Assignee: wine-bugs(a)winehq.org Reporter: johnny(a)localmomentum.net Distribution: --- Created attachment 71376 --> https://bugs.winehq.org/attachment.cgi?id=71376 ColdSteelSubs transparency code (currently not in the distributed application) This application provides a transparent clickthrough overlay to show English translations on top of the original Japanese source. It relies on layered windows and DwmExtendFrameIntoClientArea to handle the transparent display. Currently, the main UI elements show, but the game (or any other application) does not show through. This seems to be because DwmExtendFrameIntoClientArea is only a stub. I'm not sure if that's the only reason it's not transparent, but it's at least one of the reasons. The program itself uses the unity3d engine along with some native dll calls to the relevant user32 apis to handle the transparency. I was able to get a copy of the relevant code (but not the whole application), of which I will attach. Since I can't get all of the code, I've been using an unity sample application to try to figure out some parts myself (the relevant code is here https://github.com/pheonise/Unity3D-Desktop-Overlay/blob/master/Assets/Scri…) This unity3d application works as expected on windows, but is not transparent via wine (as expected). When i comment the call to DwmExtendFrameIntoClientArea, then it its also no longer transparent on windows as well. It seems that if the sample application works, then I can make sure the dev applies to the same technique to the overlay application. Please let me know If i can provide any more information. -- 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 18

[Bug 59561] New: VICE: GTK version of x86sc.exe crashes at startup.
by WineHQ Bugzilla Sept. 11, 2026

Sept. 11, 2026

http://bugs.winehq.org/show_bug.cgi?id=59561 Bug ID: 59561 Summary: VICE: GTK version of x86sc.exe crashes at startup. Product: Wine Version: 11.4 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: bernhardu(a)mailbox.org Distribution: --- Created attachment 80616 --> http://bugs.winehq.org/attachment.cgi?id=80616 vice_gtk_3.10_winehq-11.4_backtrace.txt https://sourceforge.net/projects/vice-emu/files/releases/binaries/windows/G… Maybe related logging immediately before the crash: fixme:dxgi:DXGID3D10CreateDevice Ignoring flags 0x20. fixme:d3d:wined3d_swapchain_init The application requested more than one back buffer, this is not properly supported. Please configure the application to use double buffering (1 back buffer) if possible. ... fixme:d3d11:d3d11_device_context_SwapDeviceContextState D3D10 interface emulation not fully implemented yet! It crashes with following Backtrace: =>0 ID2D1Image_AddRef() [include/d2d1.h:3254] in d2d1 1 d2d_effect_SetInput+0x21() [dlls/d2d1/effect.c:2805] in d2d1 2 0x0000014022e58a in x64sc Unfortunately upstream builds are stripped so lacking debug information. But I guess following location is calling this SetInput with the context->render_bitmap being a NULL pointer: https://github.com/VICE-Team/svn-mirror/blob/main/vice/src/arch/gtk3/direct… (The SDL version from SDL2VICE-3.10-win64.zip seems to work find.) -- 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 18

[Bug 54836] New: GrandMA3 onPC Version 1.9.2.2 page fault on startup (1.8.8.2 worked fine)
by WineHQ Bugzilla Sept. 11, 2026

Sept. 11, 2026

https://bugs.winehq.org/show_bug.cgi?id=54836 Bug ID: 54836 Summary: GrandMA3 onPC Version 1.9.2.2 page fault on startup (1.8.8.2 worked fine) Product: Wine Version: 8.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: wintrust Assignee: wine-bugs(a)winehq.org Reporter: nikolaus.einhauser(a)web.de Distribution: --- So MALighting just released their new "major" update (new features, breaking old ones, etc) to their software which broke compatability with wine. Their previous version worked fine. The issue can easily be reproduced by installing the software and then starting `app_gma3.exe`. It will crash on startup. Judging by `wine: Unhandled page fault on execute access to 000000000000000F at address 000000000000000F (thread 010c)`, the problem seems to be in the application. By inspecting the `+relay` log a little closer the page fault only looks like a symptom of missing error handling. From what I can tell, the issue lies in wintrust.WinVerifyTrust but feel free to look trough the attached debug log yourself. I'd very glad to provide more in-depth debug info or help otherwise to aid in fixing this. Suggestions for workarounds are also appreciated. Thank you. PS. There is a contest currently ongoing that mandates the use of version 1.9 or higher. So staying on an older previously working version is not an option for me. -- 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 16

[Bug 58192] New: dozen Vulkan driver fails due to missing/minimal dxcore implementation (both MacOS and Linux)..
by WineHQ Bugzilla Sept. 11, 2026

Sept. 11, 2026

http://bugs.winehq.org/show_bug.cgi?id=58192 Bug ID: 58192 Summary: dozen Vulkan driver fails due to missing/minimal dxcore implementation (both MacOS and Linux).. Product: Wine Version: 10.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rtfss1(a)gmail.com Distribution: --- Hi, in brief my request expand dxcore.dll support in Wine to a minimal dxcore implementation that allows to run Dozen via Wine.. on both Macos and Linux.. on MacOS for Dozen+D3DMetal testing on Linux for Dozen+VKD3D testing.. details: just wanting to test Dozen (Mesa Vulkan over D3D12 library) in Macos with Crossover 25.0 (bottle setup to using D3DMetal 2.1 as D3D12 driver).. for that I just download: mesa3d-25.0.4-release-msvc.7z from: https://github.com/pal1000/mesa-dist-win/releases/tag/25.0.4 and then adjust ICD loader to find the vulkan_dzn.dll driver and run vulkaninfo.exe.. I check I have all enviroment correctly as also extract lavapipe Vulkan driver from that package and it works correctly with vulkaninfo.exe using dozen on Crossover 25.0 (setup to use D3DMetal 2.1) I see bug that is not related to D3DMetal D3D12 driver: MESA: error: Failed to retrieve D3D12GetInterface MESA: error: Failed to create DXCore adapter factory so would fail also on Linux.. seeing Dozen source code I find in: https://gitlab.freedesktop.org/mesa/mesa/-/blob/main/src/microsoft/vulkan/d… fails in dzn_enumerate_physical_devices_dxcore function.. code below.. that is using dxcore and fails with DXCoreCreateAdapterFactory being a stub currently: https://github.com/wine-mirror/wine/blob/master/dlls/dxcore/main.c perhaps it's better to use as reference if wanting to implement dxcore Wine support checking it works with a minimal sample provided "Minimal DXCore application": https://github.com/MicrosoftDocs/win32/blob/docs/desktop-src/dxcore/dxcore-… dxcore microsoft docs: https://learn.microsoft.com/en-us/windows/win32/dxcore/dxcore-enum-adapters dxcore seems the "future" to enumerate adapters on Windows due to enumeration possibly NPU devices also.. dozen source code where it fails: util_dl_library *dxcore = util_dl_open(UTIL_DL_PREFIX "dxcore" UTIL_DL_EXT); if (!dxcore) { mesa_loge("Failed to load DXCore\n"); return VK_ERROR_INITIALIZATION_FAILED; } using PFNDXCoreCreateAdapterFactory = HRESULT (APIENTRY*)(REFIID, void **); PFNDXCoreCreateAdapterFactory create_func = (PFNDXCoreCreateAdapterFactory)util_dl_get_proc_address(dxcore, "DXCoreCreateAdapterFactory"); if (!create_func) { mesa_loge("Failed to load DXCoreCreateAdapterFactory\n"); return VK_ERROR_INITIALIZATION_FAILED; } IDXCoreAdapterFactory *factory; if (FAILED(create_func(IID_PPV_ARGS(&factory)))) { mesa_loge("Failed to create DXCore adapter factory\n"); return VK_ERROR_INITIALIZATION_FAILED; } -- 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 1

[Bug 59407] New: Multiple apps require appx/appxbundle support to install
by WineHQ Bugzilla Sept. 10, 2026

Sept. 10, 2026

http://bugs.winehq.org/show_bug.cgi?id=59407 Bug ID: 59407 Summary: Multiple apps require appx/appxbundle support to install Product: Wine Version: 11.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)list.winehq.org Reporter: asdfghrbljzmkd(a)outlook.com Distribution: --- An easy example is this app: https://downloads.thehomeremote.com/designer/HomeRemote.Designer.Package_4.… As per https://forum.winehq.org/viewtopic.php?t=37861 the app can run if manually extracted, but Wine itself currently has no capability to install msixbundle packages. Some Adobe Creative Cloud applications (at least Adobe Express Photos and Adobe Fresco) need appxbundle support to install. Currently they crash earlier in the process due to a missing PackageFullNameFromId implementation, but when including the implementation from Proton, they fail to install the appxbundle. See https://bugs.winehq.org/show_bug.cgi?id=59278 for details (including Adobe Installer logs showing to trying and failing to install an appxbundle). Interestingly, Microsoft has released some appx code as MIT (https://github.com/microsoft/msix-packaging) Perhaps this code could be integrated into Wine in order to provide appx/appxbundle installation capabilities? -- 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 39773] New: File->Open slowdown caused by desktop.ini checks
by wine-bugs＠winehq.org Sept. 9, 2026

Sept. 9, 2026

https://bugs.winehq.org/show_bug.cgi?id=39773 Bug ID: 39773 Summary: File->Open slowdown caused by desktop.ini checks Product: Wine Version: 1.8-rc2 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- To reproduce this you will need two Linux machines, a Samba server and a Samba client. On the Samba server: * Create a directory with lots of subdirectories and files: mkdir smbdir cd smbdir for i in `seq 1 200`;do mkdir sub$i; done for i in `seq 1 200`;do touch file$i; done * Export smbdir through Samba. (alternatively you could export '/' and use '/usr/lib' as a replacement for smbdir) On the Samba client: * Mount the Samba share. You can either do it by adding a /etc/fstab line like: //MYSERVER/smbdir /mnt/smbdir cifs rw,username=MYLOGIN,password=MYPASSWORD,domain=MYDOMAIN 0 0 Or by starting Nautilus in GNOME, clicking on '+Other Places' -> Windows network... using GVFS. Note that in this case you'll have to work around the colon in the mount point filename (see bug 34868). * Slow down the network connection using a command like this: tc qdisc add dev eth0 root netem delay 10ms * Check the above line is effective by running: ping MYSERVER The rtt should be around 10ms. * cd /mnt/root/ wine notepad * Open the File->Open dialog, navigate to the smbdir folder exported through Samba. * BUG: The initial display will be slow and scrolling through the many subfolders will be very slow. * Change the file mask to '*.*'. * Scroll all the way to the right so only files are visible. As long as only files are visible scrolling should then be very fast! * Finally change the rtt to 0ms on the Samba server and check that the RTT is under 1ms. * Now test again notepad's File->Open dialog and everything should be reasonably fast. The problem is that whenever File->Open displays a folder in the open file dialog it checks whether it contains a desktop.ini file to display the right icon. That's not cached, thus incurring a few file lookups per folder displayed. For local file systems that's fast enough but on network shares with a non-trivial RTT the speed impact is significant. A 10+ ms RTT makes the dialog essentially unusable. Note that when displaying a filename we have everything in the cache so redisplays are lightning fast and track the mouse. Also Microsoft Office has the same problem even though it does not use the standard comdlg32 dialog (though that may depend on the Windows version being emulate). On Windows Microsoft Office suffers no slowdown in this situation. What this means is that the standard common dialog is probably the wrong level for fixing this. Hacking SHELL32_GetCustomFolderAttributeFromPath() in shell32 to just return FALSE speeds things up greatly. The display still lags a bit behind the mouse so that there may be some residual file lookups or other slowdowns but it's still night and day. -- 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 5

[Bug 55029] New: Wishlist: do reflink on CopyFileW for WINEPREFIX size reduction
by WineHQ Bugzilla Sept. 9, 2026

Sept. 9, 2026

https://bugs.winehq.org/show_bug.cgi?id=55029 Bug ID: 55029 Summary: Wishlist: do reflink on CopyFileW for WINEPREFIX size reduction Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: arthur200126(a)gmail.com Distribution: --- The current implementation of CopyFileW consists of a simple read-write loop. This of course is completely fine in terms of Windows emulation, but one of the consequences is huge file size inflation when setting up things like a WINEPREFIX: on a wine 7.7-staging 64-bit install, each fresh prefix takes up 1.2 GiB: 619M of that is System32, and Syswow64 520M. Doing reflink on the CopyFileW interface (which is what rundll32 uses to get wine.ini set up) would greatly reduce the disk space burden associated with setting up a fresh prefix. Removal of real disk IO would also make the process a lot faster. Back in GNU land, the `cp` utility has been doing reflink by default since June 2020. -- 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 25723] New: PhysX causes major lag in Mirror's Edge.
by wine-bugs＠winehq.org Sept. 8, 2026

Sept. 8, 2026

http://bugs.winehq.org/show_bug.cgi?id=25723 Summary: PhysX causes major lag in Mirror's Edge. Product: Wine Version: 1.3.11 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: H3g3m0n(a)gmail.com When the PhysX option is enabled (setting in the Video Options) in Mirror's Edge. When 'physics' things start to occur the game starts to get some major lag becoming unplayable. Mirror's Edge doesn't make too much use of PhysX (I believe it was on of the first games with support for it), afaik it's mostly used for enabling shattering glass to create shards and maybe some bits of paper on the ground. As such this only seems to happen at specific points in the game. For example Chapter 1 Flight->Check Point D. As you are running across the bridge, the helicopter starts to shoot the glass causing it to shatter. If you continue on to the next area, at some point (when you go underground) it suddenly returns to normal speed (most likely it has unloaded the previous area). With PhysX set to off, there is no lag but no glass shards. -- 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 22

[Bug 59322] New: Star Trek Bridge Commander: massive graphical glitches under XWayland full-screen mode
by WineHQ Bugzilla Sept. 7, 2026

Sept. 7, 2026

http://bugs.winehq.org/show_bug.cgi?id=59322 Bug ID: 59322 Summary: Star Trek Bridge Commander: massive graphical glitches under XWayland full-screen mode Product: Wine Version: 11.1 Hardware: x86-64 URL: https://archive.org/download/StarTrekBridgeCommanderDE MO/StarTrekBridgeCommanderDEMO.exe OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: gyebro69(a)gmail.com Distribution: ArchLinux Created attachment 80253 --> http://bugs.winehq.org/attachment.cgi?id=80253 terminal output I just recently switched over to KDE Plasma to test my games using XWayland or the native Wayland driver. This bug occurs only with XWayland and in Wine's fullscreen mode: some of my old games (DX6 and DX7 era) shows graphical glitches that look like wrong Z-order issue and textures overlapping or missing entirely. The bug doesn't occur with XWayland in virtual desktop mode, neither under X server or when using the native Wayland driver. Reproduced using the nouveau vulkan driver (NVK over Zink) and Mesa 25.3.4 and with the following Nvidia binary driver versions as well: 570.211.01, 580.126.09, 590.48.01. Star Trek Bridge Commander demo, when starting a new game from the main menu, has this bug. StarTrekBridgeCommanderDEMO.exe sha256: 8fe735f356ac008f6ef5072502b19aefb5be5115fc15adf26ae70655b3b7e62a Another example of the broken rendering is Tachyon: The Fringe on Steam: https://store.steampowered.com/app/32760/Tachyon_The_Fringe/ Tested with wine-11.1-58-gf4626afec7c Arch Linux KDE Plasma 6.5.5 KWin (Wayland) X server version: 1.24.1 NVIDIA binary drivers 590.48.01 -- 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 2

[Bug 59383] New: Beyond Divinity (GOG, Steam) doesn't exit cleanly in Wayland when CSMT is enabled
by WineHQ Bugzilla Sept. 7, 2026

Sept. 7, 2026

http://bugs.winehq.org/show_bug.cgi?id=59383 Bug ID: 59383 Summary: Beyond Divinity (GOG, Steam) doesn't exit cleanly in Wayland when CSMT is enabled Product: Wine Version: 11.2 Hardware: x86-64 URL: https://store.steampowered.com/app/219760/Beyond_Divin ity/ OS: Linux Status: NEW Severity: minor Priority: P2 Component: winewayland Assignee: wine-bugs(a)list.winehq.org Reporter: gyebro69(a)gmail.com Distribution: ArchLinux After exiting the game via the menu, the game executable (div.exe) remains in the process list and occupies one CPU core at 100%. I waited for 5 minutes, but the process still didn't exit. The problem happens only when using the native Wayland driver (DISPLAY= wine div.exe), but it is not reproducible under XWayland or when running the game under X11 (XFCE). This was reproduced with NVIDIA driver 580.126.09 and with NVK / Mesa 25.3.4. Running the game under Weston 14.02 also triggers this bug. Both the Steam and GOG.com versions are affected, but the original demo version is not. Disabling CSMT resolves the problem for me. FWIW, it was commit de0fc7fd (from Wine-10.11) that enabled the game to display properly in Wayland, and the issue was already present then. Prior to that commit, the game displayed only a black screen while running; however, navigating blindly to the 'Quit' button in the menu resulted in a clean shutdown. Plain terminal output doesn't reveal anything, let me know if any debug log would help. Arch Linux KDE Plasma 6.5.5 KWin (Wayland) Nvidia 580.126.09 -- 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 1