December 2023 - Wine-bugs - list.winehq.org

[Bug 55268] New: user32:cursoricon - LoadImageA() fails in test_monochrome_icon() on Windows 8+
by WineHQ Bugzilla 16 Apr '25

16 Apr '25

https://bugs.winehq.org/show_bug.cgi?id=55268 Bug ID: 55268 Summary: user32:cursoricon - LoadImageA() fails in test_monochrome_icon() on Windows 8+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com user32:cursoricon - LoadImageA() fails in test_monochrome_icon() on Windows 8+: cursoricon.c:2853: monochrome, bitmap info cursoricon.c:2917: Test failed: LoadImage() failed with 0. See https://test.winehq.org/data/patterns.html#user32:cursoricon The call below has been failing systematically on Windows 8+ for more than 8 months: handle = LoadImageA(NULL, "icon.ico", IMAGE_ICON, 0, 0, LR_LOADFROMFILE); ok(handle != NULL || broken(use_core_info && handle == NULL), /* Win 8, 10 */ "LoadImage() failed with %lu.\n", GetLastError()); So on Windows 8+ we expect to get NULL only if use_core_info is true but in fact we get NULL even if it is false. That makes this test pretty pointless. -- 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 7

[Bug 55724] New: mfmediaengine:mfmediaengine sometimes gets a threadpool assertion in Wine
by WineHQ Bugzilla 16 Apr '25

16 Apr '25

https://bugs.winehq.org/show_bug.cgi?id=55724 Bug ID: 55724 Summary: mfmediaengine:mfmediaengine sometimes gets a threadpool assertion in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: mfplat Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- mfmediaengine:mfmediaengine sometimes gets a threadpool assertion in Wine: mfmediaengine.c:147: created L"C:\\users\\winetest\\Temp\\rgb32frame.bmp" Unhandled exception: assertion failed in 32-bit code (0x7bc24980). [...] Backtrace: =>0 0x7bc24980 raise_status+0x30(status=0x80000101, rec=00000000) [/home/winetest/tools/testbot/var/wine-win32/../wine/dlls/ntdll/exception.c:201] in ntdll (0x0499fd20) 1 0x7bc249a9 in ntdll (+0x249a9) (0x0499fd40) 2 0x7bc24d7b debugstr_a(str="!object->num_running_callbacks", file="../wine/dlls/ntdll/threadpool.c", line=0x84c) [/home/winetest/tools/testbot/var/wine-win32/../wine/include/wine/debug.h:507] in ntdll (0x0499fd70) 3 0x7bc24d7b _assert+0x1b(str="!object->num_running_callbacks", file="../wine/dlls/ntdll/threadpool.c", line=0x84c) [/home/winetest/tools/testbot/var/wine-win32/../wine/dlls/ntdll/exception.c:627] in ntdll (0x0499fd70) 4 0x7bc5cb88 tp_object_release+0x198(object=<register EBX not accessible in this frame>) [/home/winetest/tools/testbot/var/wine-win32/../wine/dlls/ntdll/threadpool.c:2123] in ntdll (0x0499fdb0) 5 0x7bc60645 TpReleaseWait+0x35(wait=013E32C8) [/home/winetest/tools/testbot/var/wine-win32/../wine/dlls/ntdll/threadpool.c:2117] in ntdll (0x0499fde0) 6 0x6b141a08 work_item_Release+0x6e(iface=<internal error>) [/home/winetest/tools/testbot/var/wine-win32/../wine/dlls/rtworkq/queue.c:567] in rtworkq (0x0499fe00) 7 0x6b141a08 work_item_Release+0x88(iface=009E7EA0) [/home/winetest/tools/testbot/var/wine-win32/../wine/dlls/rtworkq/queue.c:580] in rtworkq (0x0499fe00) 8 0x6b142f9a waiting_item_cancelable_callback+0x2a(instance=0499FE90, context=009E7EA0, wait=013E32C8, wait_result=0) [/home/winetest/tools/testbot/var/wine-win32/../wine/dlls/rtworkq/queue.c:769] in rtworkq (0x0499fe30) 9 0x7bc5d55a tp_object_execute+0x14a(object=<register EDI not accessible in this frame>, wait_thread=<register EBX not accessible in this frame>) [/home/winetest/tools/testbot/var/wine-win32/../wine/dlls/ntdll/threadpool.c:2248] in ntdll (0x0499fed0) 10 0x7bc5daf0 threadpool_worker_proc+0x100(param=00249938) [/home/winetest/tools/testbot/var/wine-win32/../wine/dlls/ntdll/threadpool.c:2356] in ntdll (0x0499ff30) 11 0x7b829770 in kernel32 (+0x29770) (0x0499ff48) 12 0x7bc5a557 in ntdll (+0x5a557) (0x0499ff5c) 13 0x7bc5ada0 RtlCreateUserThread(entry=7BC5D9F0, arg=00249938) [/home/winetest/tools/testbot/var/wine-win32/../wine/dlls/ntdll/thread.c:315] in ntdll (0x0499ffec) 0x7bc24980 raise_status+0x30 [/home/winetest/tools/testbot/var/wine-win32/../wine/dlls/ntdll/exception.c:201] in ntdll: sub $0x04, %esp 201 for (;;) RtlRaiseException( &ExceptionRec ); /* never returns */ See https://test.winehq.org/data/patterns.html#mfmediaengine:mfmediaengine There are only two instances so far but both are only days old and the GitLab CI is impacted too: 2023-10-04 MR!4012 (test-linux-32) 2023-10-02 debian11-fr-32 -- 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 8

[Bug 55997] New: Dolphin Emulator crashes from 5.0-17624
by WineHQ Bugzilla 16 Apr '25

16 Apr '25

https://bugs.winehq.org/show_bug.cgi?id=55997 Bug ID: 55997 Summary: Dolphin Emulator crashes from 5.0-17624 Product: Wine Version: 9.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: windows.gaming.input Assignee: wine-bugs(a)winehq.org Reporter: tinozzo123(a)tutanota.com Distribution: --- Created attachment 75609 --> https://bugs.winehq.org/attachment.cgi?id=75609 Wine logs when launching Dolphin Dolphin Emulator doesn't launch on Wine starting from version 5.0-17624. The commit is the following: https://github.com/dolphin-emu/dolphin/commit/50550cf978f3712e333953362e5bb…. I don't know what exactly is missing on Wine, but that commit is all about windows.gaming.input. -- 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 9

[Bug 55765] New: The 32-bit d2d1:d2d1 frequently crashes on the GitLab CI
by WineHQ Bugzilla 16 Apr '25

16 Apr '25

https://bugs.winehq.org/show_bug.cgi?id=55765 Bug ID: 55765 Summary: The 32-bit d2d1:d2d1 frequently crashes on the GitLab CI Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: d2d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The 32-bit d2d1:d2d1 crashes on the GitLab CI: d2d1.c:7400: Test marked todo: Figure does not match. Unhandled exception: page fault on write access to 0x00000000 in wow64 32-bit code (0x79d70bdf). [...] Backtrace: =>0 0x79d70bdf d2d_device_context_Clear+0x7f(iface=<is not available>, colour=<is not available>) [/builds/wine/wine/build32/../dlls/d2d1/device.c:1864] in d2d1 (0x0068fc48) 1 0x004261e4 in d2d1_test (+0x261e4) (0x0068fd08) 2 0x0043bacb in d2d1_test (+0x3bacb) (0x0068fd78) 3 0x0043c5b3 in d2d1_test (+0x3c5b3) (0x0068fe18) 4 0x0043d680 in d2d1_test (+0x3d680) (0x0068fee8) 5 0x0043d384 in d2d1_test (+0x3d384) (0x0068ff30) 6 0x7bbf8a70 in kernel32 (+0x28a70) (0x0068ff48) 7 0x7bd89827 in ntdll (+0x59827) (0x0068ff5c) 8 0x7bd8a048 in ntdll (+0x5a048) (0x0068ffec) 0x79d70bdf d2d_device_context_Clear+0x7f [/builds/wine/wine/build32/../dlls/d2d1/device.c:1864] in d2d1: fst (%eax) See https://test.winehq.org/data/patterns.html#d2d1:d2d1 It's not clear where in the test the crash happens (particularly with the parallel execution) but it always follows the trace on line 7400 so it is likely to be in test_draw_geometry(). Based on the backtrace and current source, the crash happens on this d2d_device_context_Clear() line, probably because ID3D11DeviceContext_Map() silently failed: vs_cb_data->transform_geometry._11 = 1.0f; The first crash happened on 2023-10-03: * 2023-10-03 gitlab-debian-32 * 2023-10-04 gitlab-debian-32 * 2023-10-04 MR!4010 * 2023-10-05 MR!3993 * 2023-10-05 MR!4018 * 2023-10-06 gitlab-debian-32 * 2023-10-06 MR!4037 * 2023-10-09 MR!4048 -- 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 46070] New: Basemark Web 3.0 Desktop Launcher crashes
by wine-bugs＠winehq.org 16 Apr '25

16 Apr '25

https://bugs.winehq.org/show_bug.cgi?id=46070 Bug ID: 46070 Summary: Basemark Web 3.0 Desktop Launcher crashes Product: Wine Version: 3.19 Hardware: x86 URL: http://web.basemark.com/downloads/Basemark_web_30_laun cher.exe OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: the.ideals(a)gmail.com Distribution: --- Created attachment 62675 --> https://bugs.winehq.org/attachment.cgi?id=62675 crash log Fatal Python error: Py_Initialize: can't initialize sys standard streams OSError: [WinError 6] Invalid handle sha1sum Basemark_web_30_launcher.exe c92f5548c62f43353f2dea743854d7edb0f45d70 Basemark_web_30_launcher.exe du -sh Basemark_web_30_launcher.exe 9.6M Basemark_web_30_launcher.exe -- 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 13

[Bug 55876] New: Acrom Controller Updater broken due to oleaut32 install
by WineHQ Bugzilla 16 Apr '25

16 Apr '25

https://bugs.winehq.org/show_bug.cgi?id=55876 Bug ID: 55876 Summary: Acrom Controller Updater broken due to oleaut32 install Product: Wine Version: 8.19 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- During installation you get a bunch of errors, terminal shows > 0160:err:module:import_dll Loading library OLEAUT32.dll (which is needed by L"C:\\windows\\system32\\msvbvm60.dll") failed (error c000007b). When restalling the installer, it affects that as well > 01a4:err:module:import_dll Loading library oleaut32.dll (which is needed by L"Z:\\tmp\\ramdisk\\Updater2561installer7_0_3.exe") failed (error c000007b). > 01a4:err:module:loader_init Importing dlls for L"Z:\\tmp\\ramdisk\\Updater2561installer7_0_3.exe" failed, status c0000135 The installer installs a native oleaut32, but even setting oleaut32 to builtin doesn't help. -- 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 12

[Bug 55282] New: Flutter SDK can't find "aapt" program (where.exe is a stub)
by WineHQ Bugzilla 16 Apr '25

16 Apr '25

https://bugs.winehq.org/show_bug.cgi?id=55282 Bug ID: 55282 Summary: Flutter SDK can't find "aapt" program (where.exe is a stub) Product: Wine Version: 8.12 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 74894 --> https://bugs.winehq.org/attachment.cgi?id=74894 Terminal output Steps to reproduce: 1. Download Flutter SDK from https://storage.googleapis.com/flutter_infra_release/releases/stable/window… 2. cd flutter/bin 3. Work around Bug 32679 by removing "|| GOTO acquire_lock" from the following line in internal/shared.bat: CALL :subroutine %* 2>&3 9> "%cache_dir%\flutter.bat.lock" || GOTO acquire_lock 4. Run `wine flutter.bat` The SDK fails to load and the following messages are printed: 0238:fixme:where:wmain stub: L"C:\\windows\\system32\\where.exe" L"aapt" Unhandled exception: FileSystemException: Cannot resolve symbolic links, path = '' (OS Error: Path not found. , errno = 3) -- 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 51285] New: The bmpcoreimage test in user32:cursoricon fails on most Windows versions
by WineHQ Bugzilla 16 Apr '25

16 Apr '25

https://bugs.winehq.org/show_bug.cgi?id=51285 Bug ID: 51285 Summary: The bmpcoreimage test in user32:cursoricon fails on most Windows versions Product: Wine Version: 6.10 Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The bmpcoreimage test in user32:cursoricon fails on most Windows versions. The failure is either: cursoricon.c:1217: Test failed: BMP (coreinfo): IMAGE_BITMAP failed. or cursoricon.c:1162: Test failed: BMP (coreinfo): Pixel is 0x00000000 https://test.winehq.org/data/patterns.html#user32:cursoricon A given Windows version can have different results. The result seems to depend on the user32.dll version, as if Microsoft issued a security fix that changed the handling of this bitmap and progressively converged on the "Pixel is 0" result. Here's the detailed result per platform and user32 version: vista 6.0.6002.18005 ok vistau64 6.0.6002.18005 ok w2008 6.0.6002.19714 ok w7pro64 6.1.7601.23594 ok w7u 6.1.7601.24546 Pixel is 0x00000000 w8 6.3.9600.17031 ok w864 6.3.9600.17031 ok w8.gtx 6.3.9600.17415 ok w8.rx 6.3.9600.19920 Pixel is 0x00000000 w1507 10.0.10240.16384 ok w1507.gtx 10.0.10240.16384 ok w1507.rx 10.0.10240.16384 ok w1607 10.0.14393.0 ok w1709.rx 10.0.16299.15 ok w1709 10.0.16299.125 ok w1709.gtx 10.0.16299.125 ok w1809.gtx 10.0.17763.168 ok w1809.rx 10.0.17763.168 ok w1809 10.0.17763.1339 IMAGE_BITMAP failed w1909.gtx 10.0.18362.719 IMAGE_BITMAP failed w1909.rx 10.0.18362.719 IMAGE_BITMAP failed w1909 10.0.18362.1110 Pixel is 0x00000000 w2004 10.0.19041.388 IMAGE_BITMAP failed w2009.fg 10.0.19041.610 Pixel is 0x00000000 w2009 10.0.19041.685 Pixel is 0x00000000 w2009.gtx 10.0.19041.906 Pixel is 0x00000000 w2009.rx 10.0.19041.906 Pixel is 0x00000000 Note that w1507, w1607 and w1709 may be missing updates (but installing them without upgrading to the next Windows version would be hard), which may be why they don't fail. So either this test should be removed, or it should be changed to expect 'pixel == 0' and allow for broken results (which does not fit with the way test_LoadImageFile() is currently implemented). We may also want to update Wine's BITMAP_Load() implementation to match the current Windows behavior. For reference this test bitmap was introduced in the commit below: commit 0dfedd50c38356c8049aef48e69b630204de0f79 Author: Wolfram Sang <wolfram(a)the-dreams.de> AuthorDate: Sat Jun 5 05:57:19 2010 +0200 user32: No sanity checks for BITMAPCOREINFO in BITMAP_Load. -- 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 7

[Bug 56122] New: LANCommander won't start, prints "error code 0x8007046C" (ERROR_MAPPED_ALIGNMENT)
by WineHQ Bugzilla 16 Apr '25

16 Apr '25

https://bugs.winehq.org/show_bug.cgi?id=56122 Bug ID: 56122 Summary: LANCommander won't start, prints "error code 0x8007046C" (ERROR_MAPPED_ALIGNMENT) Product: Wine Version: 8.21 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 75792 --> https://bugs.winehq.org/attachment.cgi?id=75792 Terminal output On start, LANCommander.exe prints: Failed to load System.Private.CoreLib.dll (error code 0x8007046C) Path: Z:\home\alex\Downloads\LANCommander-v0.4.0\System.Private.CoreLib.dll Error message: Failed to create CoreCLR, HRESULT: 0x8007046C 0x8007046C is HRESULT_FROM_WIN32(ERROR_MAPPED_ALIGNMENT). I've never seen that one before. `winetricks dotnet48` does not help. $ sha256sum LANCommander-v0.4.0.zip 00d9ca25c982c15a1934055805cba0a89be0400237d3273457ae523a5bba3359 -- 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 9

[Bug 53934] New: __unDName bug
by WineHQ Bugzilla 16 Apr '25

16 Apr '25

https://bugs.winehq.org/show_bug.cgi?id=53934 Bug ID: 53934 Summary: __unDName bug Product: WineHQ Bugzilla Version: unspecified Hardware: x86-64 OS: Windows Status: UNCONFIRMED Severity: normal Priority: P2 Component: bugzilla-unknown Assignee: wine-bugs(a)winehq.org Reporter: info(a)vmpsoft.com CC: austinenglish(a)gmail.com __unDName is unable to demangle the following symbol: ??$forward(a)AEAUFFIValue@?1??call(a)FFIFunctionBinder@@CAHPEAUlua_State@@@Z@@std@@YAAEAUFFIValue@?1??call(a)FFIFunctionBinder@@CAHPEAUlua_State@@@Z(a)AEAU1?1??23(a)CAH0@Z@@Z -- 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 10