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

[Bug 59198] New: Holoearth: Launcher screen flicker on change or UI interaction
by WineHQ Bugzilla Jan. 1, 2026

Jan. 1, 2026

http://bugs.winehq.org/show_bug.cgi?id=59198 Bug ID: 59198 Summary: Holoearth: Launcher screen flicker on change or UI interaction Product: Wine Version: 11.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)list.winehq.org Reporter: amppotato(a)proton.me Distribution: --- Created attachment 80072 --> http://bugs.winehq.org/attachment.cgi?id=80072 Wine stdout when interacting with the Launcher program In winehq-staging (Version 11.0-rc4, winehq-staging_11.0~rc4~trixie-1_amd64.deb), the Holoearth Launcher exhibits heavy flickering on each UI change. For example, if the user mouses over the Install/Start button, a frame of black screen is rendered over the window briefly. This does not happen when winehq-stable (Version 10.0, 10.0.0.0~trixie-1) is used instead. Steps to Reproduce: 1. Get the Holoearth installer from https://holoearth.com/en/download/ 2. Install it following the prompts, including the .NET 6 redistributable. 3. Launch the Launcher program with `wine $WINEPREFIX/drive_c/users/$(whoami)/AppData/Roaming/COVER\ corp/Holoearth\ Launcher/Launcher.exe` 3. Observe the flicker when interacting with the "Install" button on the lower right hand side. Additional Notes: No account creation is required to reproduce this, as it happens in the Launcher prior to any log in for this MMO. winetricks dxvk works around this, but that is not required for 10 / stable. However, a comparison test with wine 10 / stable DOES require `winetricks corefonts` because the launcher program will not start without that. I am not filing a bug report for that because it is does not happen in 11.0-rc4. -- 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

[Bug 51850] New: does not start MediaCreationTool21H1.exe
by WineHQ Bugzilla Jan. 1, 2026

Jan. 1, 2026

https://bugs.winehq.org/show_bug.cgi?id=51850 Bug ID: 51850 Summary: does not start MediaCreationTool21H1.exe Product: Wine Version: 6.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: 79625490833(a)yandex.ru Distribution: --- Created attachment 70744 --> https://bugs.winehq.org/attachment.cgi?id=70744 backtrace Hello. Does not start MediaCreationTool21H1.exe Operating System: ROSA Fresh Desktop 2021.1 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.10.70-generic-2rosa2021.1-x86_64 (64-bit) Graphics Platform: X11 Processors: 6 × AMD FX(tm)-6300 Six-Core Processor Memory: 7.7 ГиБ of RAM Graphics Processor: NVC1 -- 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 8

[Bug 38837] New: STDU (Scientific and Technical Documentation Utility) Viewer v1.6.375 crashes when opening PDF file
by wine-bugs＠winehq.org Jan. 1, 2026

Jan. 1, 2026

https://bugs.winehq.org/show_bug.cgi?id=38837 Bug ID: 38837 Summary: STDU (Scientific and Technical Documentation Utility) Viewer v1.6.375 crashes when opening PDF file Product: Wine Version: 1.7.46 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, continuation of bug 38510 Trace log: --- snip --- $ WINEDEBUG=+tid,+seh,+relay,+actctx,+ole,+variant,+typelib wine ./STDUViewerApp.exe >>log.txt 2>&1 ... 0026:trace:ole:SysAllocStringLen L"ISTDUImage" 0026:trace:ole:ITypeInfo_fnRelease (0xe28f00)->(1) 0026:trace:ole:ITypeInfo_fnReleaseTypeAttr (0xe2a8d8)->(0xe297d8) ... 0026:Call KERNEL32.lstrcmpW(00e2b73c L"ISTDUImage",7e2843bc L"IDispatch") ret=7e1d59b0 0026:Ret KERNEL32.lstrcmpW() retval=00000001 ret=7e1d59b0 0026:trace:ole:ITypeInfo_fnGetNames (0xe28f00) memid=0x00000096 Maxname=10 0026:trace:ole:SysAllocStringLen L"Buffer" 0026:trace:ole:SysAllocStringLen L"ppVal" ... 0026:trace:ole:deserialize_param vt VT_PTR at 0xe29594 ... 0026:trace:ole:deserialize_param vt VT_PTR at 0xe297d8 0026:trace:ole:_invoke Calling 0xd31ef0(007c9480,00e297d8,) 0026:trace:ole:_invoke returns 00000000 0026:trace:ole:serialize_param (tdesc.vt VT_PTR) 0026:trace:ole:serialize_param (tdesc.vt VT_PTR) 0026:trace:ole:serialize_param (tdesc.vt VT_UI1) ... 0026:trace:ole:ServerRpcChannelBuffer_GetBuffer (0xe29888)->(0x12be7d0,{3905360d-3c87-498c-93d2-27e002b941b1}) ... 0026:trace:ole:ServerRpcChannelBuffer_GetBuffer -- 0 0026:trace:ole:ITypeInfo_fnRelease (0xe28f00)->(0) 0026:trace:ole:ITypeLib2_fnRelease (0xe298a8) ref=2 ... 0026:trace:ole:TMStubImpl_Invoke returning ... 002a:Ret winex11.drv.MsgWaitForMultipleObjectsEx() retval=00000000 ret=7eccf928 002a:Ret user32.MsgWaitForMultipleObjectsEx() retval=00000000 ret=7e3d17ff 002a:trace:ole:CoWaitForMultipleHandles -- 0x00000000 002a:trace:ole:ClientRpcChannelBuffer_SendReceive RPC call status: 0x0 002a:trace:ole:ClientRpcChannelBuffer_SendReceive hrFault = 0x00000000 002a:trace:ole:ClientRpcChannelBuffer_SendReceive -- 0x00000000 ... 002a:trace:ole:deserialize_param vt VT_PTR at 0x12be964 002a:trace:ole:deserialize_param vt VT_PTR at 0x12be994 002a:trace:ole:deserialize_param vt VT_UI1 at (nil) 002a:trace:seh:raise_exception code=c0000005 flags=0 addr=0xf747987c ip=f747987c tid=002a 002a:trace:seh:raise_exception info[0]=00000001 002a:trace:seh:raise_exception info[1]=00000000 002a:trace:seh:raise_exception eax=012be180 ebx=00000000 ecx=00000001 edx=00000000 esi=00e2b180 edi=00e2b180 002a:trace:seh:raise_exception ebp=012be348 esp=012be138 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00210246 002a:trace:seh:call_stack_handlers calling handler at 0x1141498 code=c0000005 flags=0 002a:trace:seh:call_stack_handlers handler at 0x1141498 returned 1 --- snip --- Method call before the crash: --- snip --- Wine-dbg> 0x7e1f4af3 call_method+0x1f in oleaut32: call *0x8(%ebp) Wine-dbg> 0x00d41ef0: movl 0x4(%esp),%eax 0x00d41ef4: movl 0x20(%eax),%ecx 0x00d41ef7: movl 0x8(%esp),%edx 0x00d41efb: movl %ecx,0x0(%edx) 0x00d41efd: xorl %eax,%eax 0x00d41eff: ret $0x8 Wine-dbg>bt Backtrace: =>0 0x00d41eff in stducore (+0x1eff) (0x0033c7f8) 1 0x7e1f4caf _invoke+0x1aa(func=0xd41ef0, callconv=CC_STDCALL, nrargs=0x2, args=0xe269f0) [/home/focht/projects/wine/wine.repo/src/dlls/oleaut32/typelib.c:6421] in oleaut32 (0x0033c868) 2 0x7e1e3d26 TMStubImpl_Invoke+0x712(iface=<couldn't compute location>, xmsg=<couldn't compute location>, rpcchanbuf=<couldn't compute location>) [/home/focht/projects/wine/wine.repo/src/dlls/oleaut32/tmarshal.c:2167] in oleaut32 (0x0033ca78) 3 0x7e416c6b RPC_ExecuteCall+0x3e4(params=0xe268cc) [/home/focht/projects/wine/wine.repo/build-x86/dlls/ole32/../../include/objidl.h:9091] in ole32 (0x0033cb68) 4 0x7e3d9cba apartment_wndproc+0x33(hWnd=<couldn't compute location>, msg=<couldn't compute location>, wParam=<couldn't compute location>, lParam=<couldn't compute location>) [/home/focht/projects/wine/wine.repo/src/dlls/ole32/compobj.c:1475] in ole32 (0x0033cb88) 5 0x7ecdad46 WINPROC_wrapper+0x19() in user32 (0x0033cbc8) 6 0x7ecdaeab call_window_proc+0xbc(hwnd=0x301aa, msg=0x400, wp=0, lp=0xe268cc, result=0x33cd38, arg=0x7e3d9c86) [/home/focht/projects/wine/wine.repo/src/dlls/user32/winproc.c:245] in user32 (0x0033cc08) 7 0x7ecdcfd7 WINPROC_call_window+0x150(hwnd=0x301aa, msg=0x400, wParam=0, lParam=0xe268cc, result=0x33cd38, unicode=0x1, mapping=WMCHAR_MAP_DISPATCHMESSAGE) [/home/focht/projects/wine/wine.repo/src/dlls/user32/winproc.c:901] in user32 (0x0033cc58) 8 0x7eca1178 DispatchMessageW+0x1ad(msg=<couldn't compute location>) [/home/focht/projects/wine/wine.repo/src/dlls/user32/message.c:4023] in user32 (0x0033cd68) Wine-dbg>info share Module Address Debug info Name (111 modules) PE 400000- 650000 Export stduviewerapp PE d40000- d4e000 Export stducore PE 1080000- 11c6000 Deferred stdupdffile PE 10000000-100ba000 Export stduviewer ELF 7b800000-7ba6f000 Dwarf kernel32<elf> \-PE 7b820000-7ba6f000 \ kernel32 ... --- snip --- Crash bt --- snip --- Wine-dbg>bt Backtrace: =>0 0x7e1df59a deserialize_param+0x383(tinfo=0xe26588, readit=0x1, debugout=0, alloc=0, tdesc=0x7e2d2548, arg=0x0(nil), buf=0x12ce7fc) [/home/focht/projects/wine/wine.repo/src/dlls/oleaut32/tmarshal.c:1088] in oleaut32 (0x012ce348) 1 0x7e1dfc97 deserialize_param+0xa7f(tinfo=0xe26588, readit=0x1, debugout=0, alloc=0, tdesc=0xe276b0, arg=0x12ce994, buf=0x12ce7fc) [/home/focht/projects/wine/wine.repo/src/dlls/oleaut32/tmarshal.c:1171] in oleaut32 (0x012ce558) 2 0x7e1dfc97 deserialize_param+0xa7f(tinfo=0xe26588, readit=0x1, debugout=0, alloc=0, tdesc=0xe285e0, arg=0x12ce964, buf=0x12ce7fc) [/home/focht/projects/wine/wine.repo/src/dlls/oleaut32/tmarshal.c:1171] in oleaut32 (0x012ce768) 3 0x7e1e1bd9 xCall+0xd2e(method=<couldn't compute location>, args=<couldn't compute location>) [/home/focht/projects/wine/wine.repo/src/dlls/oleaut32/tmarshal.c:1557] in oleaut32 (0x012ce948) --- snip --- $ sha1sum stduviewer.zip ad56b235048a118b990e12142ca9c8a359e519eb stduviewer.zip $ du -sh stduviewer.zip 3.5M stduviewer.zip $ wine --version wine-1.7.46-43-g9353a36 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.

3 8

[Bug 59197] New: comctl32 hotkey should not accept "Left Super" and "Menu" keyboard keys as shortcuts
by WineHQ Bugzilla Jan. 1, 2026

Jan. 1, 2026

http://bugs.winehq.org/show_bug.cgi?id=59197 Bug ID: 59197 Summary: comctl32 hotkey should not accept "Left Super" and "Menu" keyboard keys as shortcuts Product: Wine Version: 11.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)list.winehq.org Reporter: kyle.kcsoftwares(a)gmail.com Distribution: --- Created attachment 80069 --> http://bugs.winehq.org/attachment.cgi?id=80069 sample test app comctl32 hotkey should not accept "Left Super" ("left" windows key on keyboard) and "Menu" (RMB, next to right CTRL) keyboard keys as shortcuts According to specification: https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-shllink/8c… Included test application -- 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 59037] New: CLIP Studio Paint 4.10: Application performance issue when selecting a material-based tool from the tool panel
by WineHQ Bugzilla Jan. 1, 2026

Jan. 1, 2026

http://bugs.winehq.org/show_bug.cgi?id=59037 Bug ID: 59037 Summary: CLIP Studio Paint 4.10: Application performance issue when selecting a material-based tool from the tool panel Product: Wine Version: 10.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: fun(a)fefes.co.uk Distribution: --- Created attachment 79801 --> http://bugs.winehq.org/attachment.cgi?id=79801 Terminal log showing the err:sync CSP hangs for about one minute when starting a new session and selecting a material-based tool, for example, a downloaded G-pen material, from the tool panel. Selecting another similar tool will also cause the hang, but as long as you do not switch tool groups, selecting the first material is instant. There is also a lag when first attempting to use the tool on the canvas, and I believe it is likely related, but I am happy to raise a new bug for that behaviour. CSP also hangs for longer when switching tool groups, if that tool group contains at least one tool that uses a material. >From what I can gather, this might be related to a thread being locked by another thread, but is then waiting 60 seconds to try again, as seen in lines such as: 0158:err:sync:RtlpWaitForCriticalSection section 0000713087FB7238 "?" wait timed out in thread 0158, blocked by 02b8, retrying (60 sec). In the attached log is just the basic example of selecting a new material. Download link: https://vd.clipstudio.net/clipcontent/paint/app/410/CSP_410w_setup.exe OS & DE: Linux Mint Cinnamon 22.2 Zara Architecture: AMD x86_64 Workarounds utilised: All listed for Clip Studio Paint 4.10 at https://appdb.winehq.org/objectManager.php?sClass=version&iId=42586 except for using wine-stable 10.4 where performance was worse. -- 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 5

[Bug 59196] New: MyWhoosh crashes on RoResolveNamespace stub for Windows.Devices.Bluetooth.Advertisement
by WineHQ Bugzilla Jan. 1, 2026

Jan. 1, 2026

http://bugs.winehq.org/show_bug.cgi?id=59196 Bug ID: 59196 Summary: MyWhoosh crashes on RoResolveNamespace stub for Windows.Devices.Bluetooth.Advertisement Product: Wine Version: 11.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: smirky(a)smirky.net Distribution: --- Created attachment 80068 --> http://bugs.winehq.org/attachment.cgi?id=80068 WINEDEBUG=+bluetooth,+winrt,+seh wine ./MyWhoosh/Binaries/Win64/MyWhoosh.exe &>wine-debug.log MyWhoosh (indoor cycling application) crashes when attempting to initialize Bluetooth support due to unimplemented RoResolveNamespace for Windows.Devices.Bluetooth.Advertisement namespace. **Application:** MyWhoosh (https://mywhoosh.com/) **Wine Version:** 11-rc4 (compiled from git) **OS:** Arch Linux (up to date) **BlueZ Status:** Running and functional **What happens:** 1. MyWhoosh launches successfully (to a black screen) 2. Graphics/DirectX initialize correctly (I believe) 3. Application attempts to load Windows.Devices.Bluetooth.Advertisement namespace 4. RoResolveNamespace returns as stub (not implemented) 5. Application throws C++ exception (code e06d7363) immediately after 6. Crash reporter opens but app terminates **Relevant log output:** 0024:fixme:wintypes:RoResolveNamespace name L"Windows.Devices.Bluetooth.Advertisement", windowsMetaDataDir L"", metaDataFilePaths 00007FFFFEC78B88, subNamespaces 0000000000000000 stub! 0024:trace:seh:dispatch_exception code=e06d7363 (EXCEPTION_WINE_CXX_EXCEPTION) flags=1 addr=00006FFFFFBFD887 **Expected behavior:** RoResolveNamespace should load Windows Metadata (.winmd) for the Bluetooth.Advertisement namespace, allowing the application to instantiate Bluetooth LE classes like BluetoothLEAdvertisementWatcher. **Notes:** - With Wine 10.20, the app crashed earlier with TypeLoadException for Windows Runtime assemblies - With Wine 11-rc4, significant progress has been made - the app now reaches Bluetooth initialization - The basic Bluetooth driver infrastructure (winebth.sys) and BLE support appear to be present - The issue is specifically with the WinRT metadata resolution system **Reproduction:** 1. Install MyWhoosh for Windows (available from their website) 2. Run MyWhoosh.exe with Wine 11-rc4 3. Application crashes during Bluetooth initialization The application requires Bluetooth LE connectivity to communicate with fitness equipment (smart trainers, heart rate monitors, etc.). -- 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 59057] New: Lego Indiana Jones 2: image flickers rapidly in shifting colors
by WineHQ Bugzilla Dec. 31, 2025

Dec. 31, 2025

http://bugs.winehq.org/show_bug.cgi?id=59057 Bug ID: 59057 Summary: Lego Indiana Jones 2: image flickers rapidly in shifting colors Product: Wine Version: unspecified Hardware: x86-64 OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: Alexander88207(a)Protonmail.com Created attachment 79828 --> http://bugs.winehq.org/attachment.cgi?id=79828 LegoIndy2.log Hello, when starting Lego Indiana Jones 2 the image flickers rapidly in shifting colors so fast that's not great for epileptic people. The console gets spammed with: vkd3d:0234:fixme:D3DCompile2VKD3D Ignoring flags 0x200. Tested with wine-devel 10.19 Thank you. -- 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 3