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

[Bug 55423] New: dinput:device8 - test_mouse_keyboard() sometimes gets access denied on Windows 10
by WineHQ Bugzilla 09 Aug '23

09 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55423 Bug ID: 55423 Summary: dinput:device8 - test_mouse_keyboard() sometimes gets access denied on Windows 10 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: dinput Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com dinput:device8 - test_mouse_keyboard() sometimes gets access denied on Windows 10: device8.c:695: Test failed: IDirectInputDevice8_Acquire failed: 0x80070005 device8.c:698: Test failed: IDirectInputDevice8_Acquire failed: 0x80070005 device8.c:703: Test failed: GetRegisteredRawInputDevices returned 1, raw_devices_count: 3 device8.c:705: Test failed: Unexpected raw device flags: 0 device8.c:707: Test failed: Unexpected raw device flags: 0 See https://test.winehq.org/data/patterns.html#dinput:device8 Where 0x80070005 == E_ACCESSDENIED This failure mode has been jumping around: * From 2023-01-06 to 2023-03-20 this was happening exclusively on w7u, with one exception, w10pro64-ru-64 on 2023-01-13 (all with "raw_devices_count: 3"). * Then from 2023-03-21 to 2023-05-16 it happened exclusively on various debian11-win32 locales, but with "raw_devices_count: 1". * And since 2023-05-30 it has been happening exclusively on w1064v1507 and w10pro64v2004 (both in 32 and 64-bit) with 12 instances so far, all with "raw_devices_count: 3". See also bug 54558 about other access denied errors in dinput:device8. -- 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 55413] New: ddraw:ddraw1 sometimes fails and crashes on w1064v1507 and w1046v2004
by WineHQ Bugzilla 09 Aug '23

09 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55413 Bug ID: 55413 Summary: ddraw:ddraw1 sometimes fails and crashes on w1064v1507 and w1046v2004 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ddraw:ddraw1 sometimes fails on w1064v1507 and w1046v2004: ddraw1.c:2495: Test failed: Expected message 0x46, but didn't receive it. ddraw1.c:2618: Test failed: Failed to set foreground window. ddraw1.c:2626: Test failed: Failed to set foreground window. ddraw1.c:2652: Test failed: Expected window style 0x14cf0000, got 0x4cf0000. ddraw1.c:2655: Test failed: Expected window extended style 0x108, got 0x100. ddraw1.c:2662: Test failed: Expected window extended style 0x108, got 0x100. ddraw1.c:2671: Test failed: Expected window extended style 0x108, got 0x100. ddraw1.c:2680: Test failed: Expected window extended style 0x108, got 0x100. ddraw1.c:2683: Test failed: Failed to set foreground window. ddraw1.c:2690: Test failed: Expected window style 0x14cf0000, got 0x4cf0000. ddraw1.c:2693: Test failed: Expected window extended style 0x108, got 0x100. ddraw1.c:2706: Test failed: Failed to set foreground window. ddraw1.c:2731: Test failed: Failed to set foreground window. ddraw1.c:2746: Test failed: Failed to set foreground window. ddraw1.c:2755: Test failed: Expected window extended style 0x108, got 0x100. ddraw1.c:2775: Test failed: Expected window extended style 0x108, got 0x100. ddraw1.c:2778: Test failed: Failed to set foreground window. ddraw1.c:2781: Test failed: Expected window style 0x34cf0000, got 0x14cf0000. ddraw1.c:2784: Test failed: Expected window extended style 0x108, got 0x100. ddraw1.c:3129: Test failed: Failed to set foreground window. ddraw1.c:3130: Test failed: Expected message 0x6, but didn't receive it. ddraw1.c:3135: Test failed: Got unexpected screen size 800x600. ddraw1.c:867: Test failed: Got unexpected wparam 0 for message 0x1c, expected 0x1. ddraw1.c:3141: Test failed: Expected message 0x5, but didn't receive it. ddraw1.c:3144: Test failed: Expected (0,0)-(640,480), got (-32000,-32000)-(-31840,-31972). ddraw1.c:3148: Test failed: Got unexpected screen size 1024x768. ddraw1.c:3161: Test failed: Expected message 0x46, but didn't receive it. [...] ddraw1.c:3609: Test failed: Expected (0,0)-(640,480), got (-8,-8)-(648,448). ddraw1.c:4338: Test failed: Expected WM_ACTIVATEAPP, but did not receive it. ddraw1.c:4350: Test failed: Expected WM_ACTIVATEAPP, but did not receive it. ddraw1.c:4362: Test failed: Expected WM_ACTIVATEAPP, but did not receive it. ddraw1.c:4384: Test failed: Expected WM_ACTIVATEAPP, but did not receive it. ddraw1.c:8051: Test failed: Failed to set foreground window. ddraw1.c:8053: Test failed: Got unexpected hr 0. ddraw1.c:8055: Test failed: Got unexpected hr 0. ddraw1.c:8057: Test failed: Got unexpected hr 0. ddraw1.c:8059: Test failed: Got unexpected hr 0. ddraw1.c:8069: Test failed: Got unexpected hr 0. ddraw1.c:8071: Test failed: Got unexpected hr 0. ddraw1.c:8073: Test failed: Got unexpected hr 0. ddraw1.c:8077: Test failed: Failed to set foreground window. ddraw1.c:8079: Test failed: Got unexpected hr 0. ddraw1.c:8081: Test failed: Got unexpected hr 0. ddraw1.c:8087: Test failed: Got unexpected hr 0. ddraw1.c:8135: Test failed: Failed to set foreground window. ddraw1.c:8147: Test failed: Failed to set foreground window. ddraw1.c:13670: Test failed: WM_KILLFOCUS was not received. ddraw1.c:13706: Test failed: Got unexpected hr 0x887600e1. ddraw1.c:13709: Test failed: Got unexpected hr 0x887600ff. 0a60:ddraw1: unhandled exception c0000005 at 00007FF6FFAE2567 See https://test.winehq.org/data/patterns.html#ddraw:ddraw1 Where 0x46 == WM_WINDOWPOSCHANGING and the test window does not seem to be visible: expected: 0x14cf0000 == WS_VISIBLE | 0x04cf0000 This failure happens irregularly and only on w1064v1507 and w1046v2004 so far: * 2022-12-14 win1507_newtb-w1064v1507-64 * 2022-12-15 win1507_newtb-w1064v1507-64 * 2023-01-31 win1507_newtb-w1064v1507-64 * 2023-02-16 win1507_newtb-w1064v1507-64 * 2023-06-07 win1507_newtb-w1064v1507-64 * 2023-06-09 win1507_newtb-w1064v1507-32 * 2023-07-13 win1507_newtb-w1064v1507-64 * 2023-07-27 win2004_newtb-w10pro64v2004-64 -- 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 55388] New: d3d9:visual - add_dirty_rect_test() fails on w11pro64-amd
by WineHQ Bugzilla 09 Aug '23

09 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55388 Bug ID: 55388 Summary: d3d9:visual - add_dirty_rect_test() fails on w11pro64-amd Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3d9:visual - add_dirty_rect_test() fails on w11pro64-amd: visual.c:19496: Test failed: Failed to draw, hr 0x80004005. visual.c:19792: Test failed: Got unexpected color 0x0000ff00. See https://test.winehq.org/data/patterns.html#d3d9:visual These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In particular they do not happen on fgtb-w10pro64-rx550 the only other test machine to have an AMD GPU, nor do they happen on the other Windows 11 test machines (w11pro64 and w11pro64-nv). -- 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 53423] New: Baldur's gate 3 need allocation callbacks for winevulkan
by WineHQ Bugzilla 08 Aug '23

08 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=53423 Bug ID: 53423 Summary: Baldur's gate 3 need allocation callbacks for winevulkan Product: Wine Version: 7.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winevulkan Assignee: wine-bugs(a)winehq.org Reporter: charles2000wang(a)gmail.com Distribution: --- Baldur's gate 3 crashes on startup when using the vulkan renderer. These are the error messages in terminal 0140:fixme:vulkan:wine_vkCreateWin32SurfaceKHR Support for allocation callbacks not implemented yet 0140:fixme:vulkan:__wine_create_vk_device_with_callback Support for allocation callbacks not implemented yet It seems that winevulkan does not have allocation callbacks. -- 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 51122] New: 5.0.3 vs 6.x - slow performance in graphics
by WineHQ Bugzilla 08 Aug '23

08 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=51122 Bug ID: 51122 Summary: 5.0.3 vs 6.x - slow performance in graphics Product: Wine Version: 6.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mondane.woodworker(a)gmail.com Distribution: --- When I use 6.x, even 'winecfg' starts like a slideshow. This doesn't happen with 5.0.3 . No application can be ran like this. Using: * Wine 6.0 - 6.7 * Ubuntu Unity 20.04.1 ( https://ubuntuunity.org/ ) * Laptop: Dell Precision 7550 * Graphics: NVIDIA TU117GLM [Quadro T2000 Mobile / Max-Q] ** Using nvidia-driver-460 -- 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 55419] New: dxgi:dxgi - test_video_memory_budget_notification() is sometimes missing an event in Wine
by WineHQ Bugzilla 08 Aug '23

08 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55419 Bug ID: 55419 Summary: dxgi:dxgi - test_video_memory_budget_notification() is sometimes missing an event in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- dxgi:dxgi - test_video_memory_budget_notification() is sometimes missing an event in Wine: dxgi.c:7876: Test failed: Expected event fired. See https://test.winehq.org/data/patterns.html#dxgi:dxgi The first known instance goes back to 2023-01-26 and it has been happening a bit over twice per month since, mostly on the debiant VM but also on the GitLab CI environment and fg-deb64 (my desktop). -- 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 55418] New: quartz:vmr9 - test_surface_allocator_notify_refcount() sometimes crashes on w11pro64_nv
by WineHQ Bugzilla 08 Aug '23

08 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55418 Bug ID: 55418 Summary: quartz:vmr9 - test_surface_allocator_notify_refcount() sometimes crashes on w11pro64_nv Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: quartz Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com quartz:vmr9 - test_surface_allocator_notify_refcount() sometimes crashes on w11pro64_nv: vmr9.c:3475: this is the last test seen before the exception 1828:vmr9: unhandled exception c0000005 at 000000000049805A See https://test.winehq.org/data/patterns.html#quartz:vmr9 This is crash happened only twice so far and both times on w11pro64_nv, the TestBot's Windows 11 Nvidia RTX 3050 VM: * 2023-08-04 w11pro64-nv-64 * 2023-03-03 w11pro64-nv-64 -- 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 55396] New: advapi32:registry breaks test_registerOIDFunction() in crypt32:oid on w8adm
by WineHQ Bugzilla 07 Aug '23

07 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55396 Bug ID: 55396 Summary: advapi32:registry breaks test_registerOIDFunction() in crypt32:oid on w8adm Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: crypt32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com advapi32:registry breaks test_registerOIDFunction() in crypt32:oid on w8adm: oid.c:297: Test failed: CryptUnregisterOIDFunction failed: 2 oid.c:303: Test failed: CryptUnregisterOIDFunction failed: 2 oid.c:305: Test failed: Could not delete bogus key oid.c:314: Test failed: CryptUnregisterOIDFunction failed: 2 oid.c:321: Test failed: CryptUnregisterOIDFunction failed: 2 oid.c:325: Test failed: Could not delete CryptDllEncodeObject key oid.c:336: Test failed: CryptUnregisterOIDFunction failed: 2 oid.c:340: Test failed: Could not delete CryptDllEncodeObject key oid.c:343: Test failed: Could not delete 'EncodingType 3' key oid.c:377: Test failed: Expected ERROR_FILE_EXISTS, got 00000000 oid.c:382: Test failed: Expected ERROR_FILE_EXISTS, got 00000000 oid.c:390: Test failed: Expected key to exist, RegOpenKeyA failed: 2 oid.c:412: Test failed: CryptUnregisterDefaultOIDFunction failed: 00000002 oid.c:416: Test failed: CryptUnregisterDefaultOIDFunction failed: 00000002 oid.c:430: Test failed: CryptUnregisterDefaultOIDFunction failed See https://test.winehq.org/data/patterns.html#crypt32:oid More precisely these failures only happen if running advapi32:registry before crypt32:oid. Furthermore the failures started on 2023-07-27 which is when the w8 VM's memory was increased to 4GB, and older WineTest builds still produce the failures. So the 2023-07-27 VM change is the cause of these failures but it's not clear why. -- 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 657] Many games and applications need 'mfc42.dll' ('winetricks -q mfc42' is a workaround)
by WineHQ Bugzilla 07 Aug '23

07 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=657 Bartosz <gang65(a)poczta.onet.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gang65(a)poczta.onet.pl -- 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 55412] New: Super Bubsy crashes before the intro
by WineHQ Bugzilla 06 Aug '23

06 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55412 Bug ID: 55412 Summary: Super Bubsy crashes before the intro Product: Wine Version: 8.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: spzakulec(a)gmail.com Distribution: --- Created attachment 74972 --> https://bugs.winehq.org/attachment.cgi?id=74972 wine console output and backtrace from crash When I try to install & run Super Bubsy as specified in the AppDB page: https://appdb.winehq.org/objectManager.php?sClass=version&iId=19820 the game crashes right away. Per the AppDB instructions (reproduced below), I've tried to install the game and run it with the videomemorysize=512M winetricks verb. WINEPREFIX="$HOME/SuperBubsy" WINEARCH=win32 wine wineboot WINEPREFIX="$HOME/SuperBubsy" winecfg ---> set Windows 95, do not allow to decorate windows, emulate desktop WINEPREFIX="$HOME/SuperBubsy" winetricks videomemorysize=512 Install the game and to run it: WINEPREFIX="$HOME/SuperBubsy" wine $HOME/SuperBubsy/drive_c/SUPER\ BUBSY/Bubsy.exe I'm on KDE Neon 5.27, using Wine 8.13. -- 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