- Wine-Bugs - list.winehq.org

[Bug 59015] New: Battle.net client fails to start games (e.g. Starcraft Remastered)
by WineHQ Bugzilla Dec. 2, 2025

Dec. 2, 2025

http://bugs.winehq.org/show_bug.cgi?id=59015 Bug ID: 59015 Summary: Battle.net client fails to start games (e.g. Starcraft Remastered) Product: Wine-staging Version: 10.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: zculek(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 79754 --> http://bugs.winehq.org/attachment.cgi?id=79754 Relevant crash logs Environment: - Hardware: Lenovo Thinkbook 15p G2 (Core i5-1235U, Intel GPU) - OS: Linux Mint 21.3 Cinnamon (Linux kernel 5.15.0-161-generic) - Wine: wine-staging 10.19 - Application: Battle.net client/launcher 2.49.4.15928 Issue: Battle.net client fails to start games, e.g. Starcraft Remastered. Expected behavior: Game should start normally when clicking on Play button. Actual behavior: The game doesn't start (crashes) due to error: 04b0:err:module:loader_init "ClientSdk.dll" failed to initialize, aborting 04b0:err:module:loader_init Initializing dlls for L"C:\\Program Files (x86)\\StarCraft\\x86_64\\StarCraft.exe" failed, status c0000094 Additional notes: - Reverting to wine-staging 10.18 resolves this issue, so it looks to be a regression. - This already happened at least once - https://bugs.winehq.org/show_bug.cgi?id=49525 - with wine-staging 5.12, so could be the same regression. Please let me know if any additional info is needed. -- 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 59070] New: vkGetPhysicalDeviceProperties2 gives incorrect results in wow64 mode
by WineHQ Bugzilla Dec. 1, 2025

Dec. 1, 2025

http://bugs.winehq.org/show_bug.cgi?id=59070 Bug ID: 59070 Summary: vkGetPhysicalDeviceProperties2 gives incorrect results in wow64 mode Product: Wine Version: 10.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winevulkan Assignee: wine-bugs(a)list.winehq.org Reporter: m101010a(a)gmail.com Distribution: --- Created attachment 79853 --> http://bugs.winehq.org/attachment.cgi?id=79853 vkGetPhysicalDeviceProperties2 test program When running the attached C++ program on Linux, and as a 64-bit program on wine, it prints 29 different image layouts. When run as a 32-bit program on wine (under wow64), it sometimes prints "Undefined" 29 times, and sometimes prints no image layouts at all. vkGetPhysicalDeviceProperties2 should consistently give the same results regardless of whether it is called from a 32-bit or 64-bit program. -- 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 0

[Bug 59016] New: Directdraw games get black screen
by WineHQ Bugzilla Dec. 1, 2025

Dec. 1, 2025

http://bugs.winehq.org/show_bug.cgi?id=59016 Bug ID: 59016 Summary: Directdraw games get black screen Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)list.winehq.org Reporter: i(a)xuzhao.net Distribution: --- Created attachment 79755 --> http://bugs.winehq.org/attachment.cgi?id=79755 Black screen, with directdraw render method Hi Wine Community, I want to ask about a regression I observed on my desktop (openSUSE Tumbleweed, KDE, NVIDIA 3080 Ti). A few old Japanese Galgames have blackscreen starting from a few months ago. To be specific, I am running Ebenbourg no Kaze (by Studio e-go!). The game screen is black, but with `WINEDEBUG=+ddraw` I can see logs being printed out: https://pastebin.com/s5m0i3AK I am testing on other applications, e.g., VisualBoyAdvance (the GameBoyAdvance simulator). I found that when I switch the render method to "DirectDraw" it shows black screen, but when I switch to "GDI", "OpenGL" or "Direct3D", the screen is normal. I have tried changing [HKCU/Wine/Direct3D] -> "renderer" from "gl" to "gdi", but the game/application will crash/black screen. I suspect there is a regression in DirectDraw support in Wine. -- 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 59049] New: When navigating through the wine file explorer via Clip Studio Paint Pro 4.0.3 after pressing File>Open>.. the Explorer is only able to see Clip Studio made .psd files.
by WineHQ Bugzilla Dec. 1, 2025

Dec. 1, 2025

http://bugs.winehq.org/show_bug.cgi?id=59049 Bug ID: 59049 Summary: When navigating through the wine file explorer via Clip Studio Paint Pro 4.0.3 after pressing File>Open>.. the Explorer is only able to see Clip Studio made .psd files. Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: n96rom(a)gmail.com Distribution: --- Created attachment 79820 --> http://bugs.winehq.org/attachment.cgi?id=79820 Screenshot of Wine File Explorer unable to see other available psd files than "Illustration". I followed this guide: https://appdb.winehq.org/objectManager.php?sClass=version&iId=42586 It worked. I am able to use every other functionality of CS. However, the wine file system does not detect any other .psd files except the ones I have created in CS. To navigate I used File>Open> and then it opens up wine's file explorer. I am not sure how to change it to Dolphin which is the file explorer used on my OS, PikaOS 4 but it cant see the files. -- 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 59060] New: Movie Maker msi does not open
by WineHQ Bugzilla Dec. 1, 2025

Dec. 1, 2025

http://bugs.winehq.org/show_bug.cgi?id=59060 Bug ID: 59060 Summary: Movie Maker msi does not open Product: Wine Version: 10.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)list.winehq.org Reporter: passymas(a)gmail.com Distribution: --- Created attachment 79830 --> http://bugs.winehq.org/attachment.cgi?id=79830 error movie maker msi Movie Maker msi does not open. -- 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 59068] New: ScriptPlace() total run width sum inconsistent with advance width array sum
by WineHQ Bugzilla Dec. 1, 2025

Dec. 1, 2025

http://bugs.winehq.org/show_bug.cgi?id=59068 Bug ID: 59068 Summary: ScriptPlace() total run width sum inconsistent with advance width array sum Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: usp10 Assignee: wine-bugs(a)list.winehq.org Reporter: benc.marek.elektro98(a)proton.me Distribution: --- Created attachment 79842 --> http://bugs.winehq.org/attachment.cgi?id=79842 Example program with ScriptPlace() that displays a run's advance width. Hello, I'm working on a Uniscribe text editor and doing a bit of testing with Wine too, and I've hit an issue where the ScriptPlace() function's last argument, the ABC width of the run, occasionally has an inconsistent width as compared to the sum of the advance width elements provided through the piAdvance array. The MSDN documentation appears to suggest that the sum of the fields provided by the ABC parameter should match the total width of the run: https://learn.microsoft.com/en-us/windows/win32/api/usp10/nf-usp10-scriptpl… """ The composite ABC width for the whole item identifies how much the glyphs overhang to the left of the start position and to the right of the length implied by the sum of the advance widths. The total advance width of the line is exactly abcA+abcB+abcC. The abcA and abcC values are maintained as proportions of the cell height represented in 8 bits and are thus roughly +/-1 percent. The total width retrieved, which is the sum of the abcA+abcB+abcC values indicated by piAdvance, is accurate to the resolution of the TrueType shaping engine. """ I'm adding the source code of a simple demonstration program to show the error in the attachment. Here's the build command: $ i686-w64-mingw32-gcc -o scriptplace_abc_testcase.exe scriptplace_abc_testcase.c -lusp10 -lgdi32 -municode -O2 -Wall -Wextra -W This example uses a string that triggered the condition for me in my text editing widget, which I noticed as the caret being misaligned, since the distance of the caret from the edge of the run was measured with the assumption that the total advance width is abcA+abcB+abcC, but that is not the case. The example program generates a single text run, displays it on-screen with the default UI font retrieved by SPI_GETNONCLIENTMETRICS (Tahoma) with a 24 pt size, and displays the advance width value for each glyph, their sum, the ABC values, and their sum. On Debian 13 with wine-10.0 (Debian 10.0~repack-6), I'm getting the following: testprog_load_1st_glyph_run(): first_run->abc: { abcA: 16, abcB: 178, abcC: 28 }, total: 222 testprog_load_1st_glyph_run(): first_run->glyph_advances: [ 17, 17, 15, 12, 10, 24, 8, 12, 18, 10, 12, 18, 12, 17, 17 }, total: 219 On Windows, I'm getting the following: testprog_load_1st_glyph_run(): first_run->abc: { abcA: 0, abcB: 209, abcC: 0 }, total: 209 testprog_load_1st_glyph_run(): first_run->glyph_advances: [ 20, 17, 16, 9, 9, 23, 7, 9, 18, 9, 9, 18, 11, 17, 17 }, total: 209 I was able to trace down the error in the Wine source code. The advances and ABC are initially set to the same value in ScriptShape, see the following: https://gitlab.winehq.org/wine/wine/-/blob/master/dlls/gdi32/uniscribe/usp1… """ if (pABC) { pABC->abcA += abc.abcA; pABC->abcB += abc.abcB; pABC->abcC += abc.abcC; } if (piAdvance) piAdvance[i] = abc.abcA + abc.abcB + abc.abcC; } SHAPE_ApplyOpenTypePositions(hdc, (ScriptCache *)*psc, psa, pwGlyphs, cGlyphs, piAdvance, pGoffset); """ But if you look just below, there is a SHAPE_ApplyOpenTypePositions() call that accepts the glyph advance array as an argument. This eventually ends up calling GPOS_apply_lookup() in https://gitlab.winehq.org/wine/wine/-/blob/master/dlls/gdi32/uniscribe/open… - which adjusts the advances: """ if (advance.x || advance.y) { GPOS_convert_design_units_to_device(lpotm, lplogfont, advance.x, advance.y, &devX, &devY); piAdvance[glyph_index] += round(devX); if (advance.y) FIXME("Unhandled adjustment to Y advancement\n"); } break; """ Clearly, this causes the advance array and the ABC width to de-synchronize. I also don't think the way the ABC width is calculated in the first place is correct, I see the As and Cs being summed up, but shouldn't they only be propagated for the left-most and right-most glyph, and otherwise be summed up in the B? But that's a separate issue, and it doesn't cause a problem for me. Thanks, Marek -- 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 3

[Bug 59008] New: Red dead redemption hangs
by WineHQ Bugzilla Dec. 1, 2025

Dec. 1, 2025

http://bugs.winehq.org/show_bug.cgi?id=59008 Bug ID: 59008 Summary: Red dead redemption hangs Product: vkd3d Version: 1.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vkd3d Assignee: wine-bugs(a)list.winehq.org Reporter: levanchelidze(a)gmail.com Distribution: --- Created attachment 79745 --> http://bugs.winehq.org/attachment.cgi?id=79745 terminal output On uhd 620 graphics after in game some time passes the game hangs Using wine 10.19 and installed vkd3d from winetricks BufferCount = 3. 10029.717:0020:0024:info:vkd3d-proton:dxgi_vk_swap_chain_init_sync_objects: Ensure maximum latency of 3 frames with KHR_present_wait. 10029.728:0020:0024:info:vkd3d-proton:dxgi_vk_swap_chain_init_waiter_thread: Enabling present wait path for frame latency. 10029.728:0020:0024:info:vkd3d-proton:dxgi_vk_swap_chain_init_sleep_state: Timer interval is 1.0 ms. warn: DXGI: MakeWindowAssociation: Ignoring flags 10029.751:0020:01f8:info:vkd3d-proton:dxgi_vk_swap_chain_recreate_swapchain_in_present_task: Got 3 swapchain images. 10029.923:0020:01f8:info:vkd3d-proton:dxgi_vk_swap_chain_recreate_swapchain_in_present_task: Got 3 swapchain images. 10030.179:0020:01f0:info:vkd3d-proton:vkd3d_pipeline_library_disk_thread_main: Flushing disk cache (wakeup counter since last flush = 1791). It seems like application has stopped creating new PSOs for the time being. 01d8:fixme:rawinput:NtUserRegisterRawInputDevices Unhandled flags 0x230 for device 0. 10063.639:0020:0024:info:vkd3d-proton:dxgi_vk_swap_chain_ChangeProperties: Reallocating swapchain (1280 x 720), BufferCount = 3. 01d8:fixme:rawinput:NtUserRegisterRawInputDevices Unhandled flags 0x230 for device 0. 01d8:fixme:rawinput:NtUserRegisterRawInputDevices Unhandled flags 0x230 for device 0. 10109.104:0020:01f4:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4. 10109.104:0020:01f4:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4. 10109.104:0020:01f4:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4. 10109.104:0020:01f4:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4. ^C0264:fixme:console:default_ctrl_handler Terminating process 20 on event 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 5

[Bug 59067] New: some Unreal Engine games don't render correctly with opengl renderer
by WineHQ Bugzilla Dec. 1, 2025

Dec. 1, 2025

http://bugs.winehq.org/show_bug.cgi?id=59067 Bug ID: 59067 Summary: some Unreal Engine games don't render correctly with opengl renderer Product: Wine Version: 10.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)list.winehq.org Reporter: galtgendo(a)o2.pl Distribution: --- Created attachment 79840 --> http://bugs.winehq.org/attachment.cgi?id=79840 console output for vulkan To start off, this seems to be an engine problem as I've seem this in at least 2 UE games. So, I'll be attaching two short logs from one of the games - one for opengl renderer, where the problem can be seen and one for vulkan, where it seems to display correctly. The problem is that the scene is rendered dark with opengl - not sure if it's missing textures, bad lightning or something else. Another one of those games is 'Last Hope' by Poolside Games - just start a new game, the bug is - let's say 'difficult to miss' within first 15 sec. of gameplay. It's on steam, but there were free releases of that one too. PS: unrelated problem - both of the games I'm testing this problem with also turn off my secondary screen at termination...for no apparent reason, as I'm running them windowed anyway. -- 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 57588] New: Guardant USB key drivers: grdkey.sys crashes
by WineHQ Bugzilla Dec. 1, 2025

Dec. 1, 2025

https://bugs.winehq.org/show_bug.cgi?id=57588 Bug ID: 57588 Summary: Guardant USB key drivers: grdkey.sys crashes Product: Wine Version: 10.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)winehq.org Reporter: amorozov(a)etersoft.ru Distribution: --- Created attachment 77697 --> https://bugs.winehq.org/attachment.cgi?id=77697 Log with WINEDEBUG=+ntoskrnl,+plugplay and winedbg output I installed Guardant USB key drivers 7.0.224 from here: https://www.guardant.com/support/users/download/2238/ with WoW64 Wine build. $ md5sum GrdDrivers.exe 731d388d2ee4c1a4f45d655e4b8c9163 GrdDrivers.exe After installation windows/system32/drivers/grdkey.sys appears. And it crashes at Wine start: wine: Unhandled page fault on read access to 0000000000000008 at address 00006FFFFC8A295B (thread 00f0), starting debugger... In AddDevice handler grdkey.sys calls IoOpenDeviceRegistryKey. This results in calling get_device_instance_id -> get_device_id and sending IRP_MJ_PNP/IRP_MN_QUERY_ID with BusQueryDeviceID to the driver which calls IofCallDriver(NULL, ....) and crashes. The crash can be avoided with commenting out this line: device = IoGetAttachedDevice( device ); in get_device_id function in dlls/ntoskrnl.exe/pnp.c But I assume that the correct fix should be in avoiding to send IRPs from IoOpenDeviceRegistryKey. MSDN says that IRP_MN_QUERY_ID is sent before loading driver and calling AddDevice: https://learn.microsoft.com/en-us/windows-hardware/drivers/kernel/adding-a-… -- 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 59065] New: 32-bit foobar2000 crashes when you play files
by WineHQ Bugzilla Dec. 1, 2025

Dec. 1, 2025

http://bugs.winehq.org/show_bug.cgi?id=59065 Bug ID: 59065 Summary: 32-bit foobar2000 crashes when you play files Product: Wine-staging Version: 10.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: just4steam778(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 79838 --> http://bugs.winehq.org/attachment.cgi?id=79838 Log 32-bit foobar2000 crashes when you try to play files. 64-bit foobar2000 works fine. OS: Arch Linux -- 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