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

[Bug 54780] New: UndertaleModTool display regression since wine-staging 8.4
by WineHQ Bugzilla 10 Nov '23

10 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=54780 Bug ID: 54780 Summary: UndertaleModTool display regression since wine-staging 8.4 Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: janbidler00(a)protonmail.com Distribution: --- Created attachment 74277 --> https://bugs.winehq.org/attachment.cgi?id=74277 Display bug Starting from wine-staging 5.4 UndertaleModTool has corrupted display at boot. This did not happen on wine-staging 5.3 and earlier. The corrupted display can be fixed temporarily by clicking on any item in the Menubar (i.e. "File"). Happens both on a clean prefix and when upgrading. Issue is specific to wine-staging; wine-development has crashes going back all the way to wine-7.0 if not earlier and I didn't test it with wine-stable. Attached is an image of the display bug. The UndertaleModTool version can be found here (I used the asset "UndertaleModTool_v0.5.0.0.zip"): https://github.com/krzys-h/UndertaleModTool/releases/tag/0.5.0.0 Using Arch Linux. The wine-staging were gotten from here: https://archive.archlinux.org/packages/w/wine-staging/ -- 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 54519] New: d3d9:visual - test_mipmap_upload() fails on AMD and Nvidia GPUs
by WineHQ Bugzilla 10 Nov '23

10 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=54519 Bug ID: 54519 Summary: d3d9:visual - test_mipmap_upload() fails on AMD and Nvidia GPUs 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 - test_mipmap_upload() fails on AMD and Nvidia GPUs. This impacts three VMs: fgtb-w10pro64_rx550 (AMD RX550): visual.c:27986: Test failed: pool 0x2: level 0: Got unexpected color 0x00000000. visual.c:27986: Test failed: pool 0x2: level 1: Got unexpected color 0x00000000. visual.c:27986: Test failed: pool 0x2: level 2: Got unexpected color 0x00000000. visual.c:27986: Test failed: pool 0x2: level 3: Got unexpected color 0x00000000. visual.c:27986: Test failed: pool 0x2: level 4: Got unexpected color 0x00000000. visual.c:27986: Test failed: pool 0x2: level 5: Got unexpected color 0x00000000. w11pro64_amd (AMD RX660): visual.c:404: Test failed: pool 0x2: level 0: Got hr 0x80004005. visual.c:27986: Test failed: pool 0x2: level 0: Got unexpected color 0x00ff0000. visual.c:404: Test failed: pool 0x2: level 1: Got hr 0x80004005. visual.c:27986: Test failed: pool 0x2: level 1: Got unexpected color 0x00ff0000. visual.c:404: Test failed: pool 0x2: level 2: Got hr 0x80004005. visual.c:27986: Test failed: pool 0x2: level 2: Got unexpected color 0x00ff0000. visual.c:404: Test failed: pool 0x2: level 3: Got hr 0x80004005. visual.c:27986: Test failed: pool 0x2: level 3: Got unexpected color 0x00ff0000. visual.c:404: Test failed: pool 0x2: level 4: Got hr 0x80004005. visual.c:27986: Test failed: pool 0x2: level 4: Got unexpected color 0x00ff0000. visual.c:404: Test failed: pool 0x2: level 5: Got hr 0x80004005. visual.c:27986: Test failed: pool 0x2: level 5: Got unexpected color 0x00ff0000. w11pro64_nv (NVIDIA RTX3050): visual.c:195: pool 0x2: level 0: Can't create an offscreen plain surface to read the render target data, hr 0x80004005. visual.c:27986: Test failed: pool 0x2: level 0: Got unexpected color 0x00adbeef. visual.c:27986: Test failed: pool 0x2: level 1: Got unexpected color 0x00000000. visual.c:195: pool 0x2: level 2: Can't create an offscreen plain surface to read the render target data, hr 0x80004005. visual.c:27986: Test failed: pool 0x2: level 2: Got unexpected color 0x00adbeef. visual.c:195: pool 0x2: level 3: Can't create an offscreen plain surface to read the render target data, hr 0x80004005. visual.c:27986: Test failed: pool 0x2: level 3: Got unexpected color 0x00adbeef. visual.c:195: pool 0x2: level 4: Can't create an offscreen plain surface to read the render target data, hr 0x80004005. visual.c:27986: Test failed: pool 0x2: level 4: Got unexpected color 0x00adbeef. visual.c:195: pool 0x2: level 5: Can't create an offscreen plain surface to read the render target data, hr 0x80004005. visual.c:27986: Test failed: pool 0x2: level 5: Got unexpected color 0x00adbeef. See https://test.winehq.org/data/patterns.html#d3d9:visual These failures all started on 2023-01-06 and a bisect shows that, on all three machines, they started with the commit below: commit 2954d3e4a23025657740fb178ddbe110890c0cc8 Author: Zebediah Figura <zfigura(a)codeweavers.com> Date: Tue Dec 20 17:43:39 2022 -0600 d3d9/tests: Test uploading the whole mipmap chain in one map. Signed-off-by: Zebediah Figura <zfigura(a)codeweavers.com> -- 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 53218] New: d3d10core:d3d10core - test_uint_shader_instructions() fails in the TestBot VMs
by WineHQ Bugzilla 10 Nov '23

10 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=53218 Bug ID: 53218 Summary: d3d10core:d3d10core - test_uint_shader_instructions() fails in the TestBot VMs Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- d3d10core:d3d10core - test_uint_shader_instructions() fails in the TestBot VMs: d3d10core.c:13215: Test failed: Got {0x80000000, 0x00000000, 0x00000000, 0x00000000}, expected {0x00000000, 0xffffffff, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d10core.c:13215: Test failed: Got {0x00000000, 0x80000000, 0x00000000, 0x00000000}, expected {0xffffffff, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d10core.c:13215: Test failed: Got {0xffffffff, 0x00000001, 0x00000000, 0x00000000}, expected {0x00000000, 0x00000001, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d10core.c:13215: Test failed: Got {0x00000001, 0xffffffff, 0x00000000, 0x00000000}, expected {0x00000001, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. https://test.winehq.org/data/patterns.html#d3d10core:d3d10core These failures: * Don't happen on Debian 11 + Intel / KDE * Happen on Debian 11 + QXL + single-monitor * Happen on Debian 11 + QXL + multi-monitor * Happen on Debian Testing + QXL + multi-monitor (it actually has a couple extra) So they are probably related to QXL. Note that despite being systematic these failures could cause false positives due to the test multi-threading (see bug 53212). -- 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 55316] New: d3d10core:d3d10core fails systematically on w11pro64-amd
by WineHQ Bugzilla 10 Nov '23

10 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=55316 Bug ID: 55316 Summary: d3d10core:d3d10core fails systematically 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 d3d10core:d3d10core fails systematically on w11pro64-amd: test_pipeline_statistics_query(): d3d10core.c:4922: Test failed: Got unexpected GSInvocations count: 2. d3d10core.c:4941: Test failed: Got unexpected GSInvocations count: 2. test_sample_c_lz(): d3d10core.c:8553: Test failed: Got 1.00000000e+000, expected 0.00000000e+000 at (100, 100), sub-resource 0. d3d10core.c:8553: Test failed: Got 1.00000000e+000, expected 0.00000000e+000 at (100, 100), sub-resource 0. See https://test.winehq.org/data/patterns.html#d3d10core:d3d10core These failures have been happening forever and are specific to the Windows 11 + AMD RX6600 configuration. In particular they never happened on fgtbw10pro64_rx550 (Windows 10 + AMD RX550). Also, except for 2023-05-10 to 2023-05-12 (3 days) they are present in all nightlies. -- 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 55608] New: NAM won't open on new update
by WineHQ Bugzilla 10 Nov '23

10 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=55608 Bug ID: 55608 Summary: NAM won't open on new update Product: Wine Version: 8.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zardivorku(a)gufum.com Distribution: --- Created attachment 75145 --> https://bugs.winehq.org/attachment.cgi?id=75145 Log Report https://github.com/sdatkinson/NeuralAmpModelerPlugin/releases On latest wine staging update NAM crashes, didn't happen before on prior update. Linux Mint Cinnamon -- 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 19

[Bug 55679] New: warframe doesn't start in experimental wow64 mode
by WineHQ Bugzilla 10 Nov '23

10 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=55679 Bug ID: 55679 Summary: warframe doesn't start in experimental wow64 mode Product: Wine Version: 8.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: pmargeti34(a)gmail.com Distribution: --- Created attachment 75201 --> https://bugs.winehq.org/attachment.cgi?id=75201 warframe doesn't start in experimental wow64 mode Game launcher fails to run properly, it spawns it's own error dialog which offers to send crash related data to Digital Extremes. Attached is the output of launching it from the terminal. -- 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 53217] New: d3d11:d3d11 - test_cube_maps() crashes in Wine
by WineHQ Bugzilla 10 Nov '23

10 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=53217 Bug ID: 53217 Summary: d3d11:d3d11 - test_cube_maps() crashes in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- d3d11:d3d11 - test_cube_maps() crashes in Wine: $ WINETEST_REPORT_SUCCESS=1 WINETEST_NO_MT_D3D=1 ./wine dlls/d3d11/tests/d3d11_test.exe d3d11 Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x70baff74). [...] 0614:err:d3d:wined3d_debug_callback 00165DA0: "GL_OUT_OF_MEMORY in glMapBufferRange(map failed)". 0614:err:d3d:wined3d_allocator_chunk_gl_map Failed to map chunk memory. 0614:err:d3d:wined3d_bo_gl_map Failed to map chunk. 0614:err:d3d:wined3d_context_gl_map_bo_address Failed to map bo. Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x70baff74). [...] Backtrace: =>0 0x70baff74 memset+0x24(dst=0x000000000, c=0, n=0x4b0000) [Z:\home\winetest\tools\testbot\var\wine\dlls\msvcrt\string.c:3150] in ucrtbase (0x020ef908) 1 0x715283e3 wined3d_texture_load_location+0x423(texture=0016C8C0, sub_resource_idx=0, context=0016D920, location=0x8) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\texture.c:853] in wined3d (0x020ef9a8) 2 0x715173ae surface_cpu_blt+0x9ee(dst_texture=0016C8C0, dst_sub_resource_idx=0, dst_box=020EFB38, src_texture=00171550, src_sub_resource_idx=0, src_box=020EFB50, flags=0x20000000, fx=020EFB68, filter=WINED3D_TEXF_POINT) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\surface.c:752] in wined3d (0x020efaf8) 3 0x71518ea2 cpu_blitter_blit+0xc2(blitter=0016E408, op=WINED3D_BLIT_OP_RAW_BLIT, context=0016D920, src_texture=00171550, src_sub_resource_idx=0, src_location=0x10, src_rect=020EFE10, dst_texture=0016C8C0, dst_sub_resource_idx=<is not available>, dst_location=0x8, dst_rect=020EFE20, color_key=00000000, filter=WINED3D_TEXF_POINT, resolve_format=00000000) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\surface.c:1328] in wined3d (0x020efb98) 4 0x715368a2 ffp_blitter_blit+0xa2(blitter=0016E420, op=WINED3D_BLIT_OP_RAW_BLIT, context=0016D920, src_texture=00171550, src_sub_resource_idx=0, src_location=0x10, src_rect=020EFE10, dst_texture=0016C8C0, dst_sub_resource_idx=0, dst_location=0x8, dst_rect=020EFE20, colour_key=00000000, filter=WINED3D_TEXF_POINT, resolve_format=00000000) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\texture.c:6213] in wined3d (0x020efc58) 5 0x714dc91d glsl_blitter_blit+0x1ad(blitter=0016E438, op=WINED3D_BLIT_OP_RAW_BLIT, context=0016D920, src_texture=00171550, src_sub_resource_idx=0, src_location=0x10, src_rect=020EFE10, dst_texture=0016C8C0, dst_sub_resource_idx=0, dst_location=0x8, dst_rect=020EFE20, colour_key=00000000, filter=WINED3D_TEXF_POINT, resolve_format=00000000) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\glsl_shader.c:13270] in wined3d (0x020efd78) 6 0x7151a181 texture2d_blt+0x3c1(dst_texture=0016C8C0, dst_sub_resource_idx=0, dst_box=013EFAC4, src_texture=00171550, src_sub_resource_idx=0, src_box=013EFAE4, flags=0x20000000, fx=013EFB00, filter=WINED3D_TEXF_POINT) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\surface.c:1639] in wined3d (0x020efe48) 7 0x7149b07d wined3d_cs_exec_blt_sub_resource+0xcd(cs=013E0020, data=013EFAB8) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\cs.c:2579] in wined3d (0x020efec8) 8 0x7149cb2b wined3d_cs_command_unlock(queue=<internal error>, cs=<internal error>) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\cs.c:3310] in wined3d (0x020eff28) 9 0x7149cb2b wined3d_cs_execute_next+0x53(queue=<internal error>, cs=<internal error>) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\cs.c:3309] in wined3d (0x020eff28) 10 0x7149cb2b wined3d_cs_run+0x11b(ctx=<internal error>) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\cs.c:3375] in wined3d (0x020eff28) 11 0x7b62a170 in kernel32 (+0x2a170) (0x020eff48) 12 0x7bc5a937 in ntdll (+0x5a937) (0x020eff5c) 13 0x7bc5aff0 RtlCreateUserThread(entry=7149CA10, arg=013E0020) [Z:\home\winetest\tools\testbot\var\wine\dlls\ntdll\thread.c:261] in ntdll (0x020effec) 0x70baff74 memset+0x24 [Z:\home\winetest\tools\testbot\var\wine\dlls\msvcrt\string.c:3150] in ucrtbase: movl %eax,0x0(%ebx) 3150 *(unaligned_ui64 *)(d + 0) = v; https://test.winehq.org/data/patterns.html#d3d11:d3d11 The crash happens with sub_resource_idx = 30. This impacts Debian 11 + QXL (the TestBot VMs), Intel (fg-deb64) and AMD RX460 (cw-rx460)... but only for 32-bit builds. -- 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 21

[Bug 53522] New: Need for Speed III: joystick doesn't work after evdev removal
by WineHQ Bugzilla 10 Nov '23

10 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=53522 Bug ID: 53522 Summary: Need for Speed III: joystick doesn't work after evdev removal Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dinput Assignee: wine-bugs(a)winehq.org Reporter: DirtY.iCE.hu(a)gmail.com CC: rbernon(a)codeweavers.com Regression SHA1: adfee25b45af8160848f94fdb24279d63d5f91f4 Distribution: Gentoo Created attachment 72888 --> https://bugs.winehq.org/attachment.cgi?id=72888 WINEDEBUG=+dinput, ds4 usb, overriden, nfs3 demo with git master wine I decided to try NFS3 after some time and realized that joystick no longer works with newer releases. Git bisect lead me to commit adfee25b45af8160848f94fdb24279d63d5f91f4, where the evdev and js backends were removed. With the new backend, in NFS3 deadzone calibration screen, all axes are at constant 0, and it doesn't respond to any keypress either. I've tried it with DualShock 4 (both usb and bt), DS3 (only usb), and some noname cheap controller, the same results. Interestingly, in joy.cpl the joysticks do work, I've tried to click on override to move the controller from the xinput to the non-xinput list, but no change. I also have no force-feedback support with the new backend. Tested it with the retail version of nfs3 and also with this patch, the results are the same: https://veg.by/en/projects/nfs3/ Also tested it with the demo version and the latest git (bfc73b0b80a1da2b137b5da4a2fcf530ee3a9d7d), same results. 1. Download demo from here: https://archive.org/details/nfs3_demo 2. Create a new 32-bit wine prefix (I've only compiled a 32-bit wine) 3. In winecfg, set windows compatibility to 98 (otherwise the install refuses to start), go to drives and add a (fake) cdrom device (otherwise setup refuses to start), and probably you should set a virtual desktop (the game likes to mess with your resolution) 4. Run setup.exe (it will throw a registry error but still installs the game) 5. Start the game with taskset: `taskset -c 0 path/to/wine nfs3demo -d3d0` (the game crashes/freezes if run on multicore cpu) 6. After the race countdown, press esc, controls, and try to bind some keys or click on dead zone to see axes values. I'm attaching a log with WINEDEBUG=+dinput and overridden joystick on joy.cpl. -- 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 49988] New: NosTale (and probably some other games) doesn't handle mouse clicks correctly
by WineHQ Bugzilla 10 Nov '23

10 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=49988 Bug ID: 49988 Summary: NosTale (and probably some other games) doesn't handle mouse clicks correctly Product: Wine Version: 5.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: theszczepancio(a)gmail.com Distribution: --- Created attachment 68390 --> https://bugs.winehq.org/attachment.cgi?id=68390 Wine-staging 5.19 log Releated issues: https://bugs.winehq.org/show_bug.cgi?id=42999 https://bugs.winehq.org/show_bug.cgi?id=21739 Some info: Tested the issue with wine and wine-staging. Bug persists in 5.17, 5.18, 5.19 versions of wine. I have installed Arch Linux on r5 3600/rx5700 XT. I use D9VK (newest) for improvements of performance. Installing dinput8 is not fixing anything. I use Sway/wlroots on wayland, also I own newest kernel. Game works as should on steam proton with same version of D9VK. OpenGL backend works fine. Wine log in attachement. -- 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 14

[Bug 52444] New: Regression prevent eclipse from hitting breakpoints
by WineHQ Bugzilla 09 Nov '23

09 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=52444 Bug ID: 52444 Summary: Regression prevent eclipse from hitting breakpoints Product: Wine Version: 7.0-rc6 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- I usually use eclipse with normal gdb for debugging. For that I compile without mingw, since it doesn't find the symbols when using real dlls. Since a while this is broken, and eclipse doesn't hit any breakpoints anymore. Bisected to commit 28fe84da45bea7de56539b50eac8ebcec54342de Author: Alexandre Julliard <julliard(a)winehq.org> Date: Wed Mar 24 10:53:53 2021 +0100 ntdll: Load the main image from the Unix side. Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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