March 2023 - Wine-Bugs - list.winehq.org

[Bug 53216] New: d3d11:d3d11 - test_depth_bias() fails in the TestBot VMs
by WineHQ Bugzilla Nov. 13, 2023

Nov. 13, 2023

https://bugs.winehq.org/show_bug.cgi?id=53216 Bug ID: 53216 Summary: d3d11:d3d11 - test_depth_bias() 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: --- d3d11:d3d11 - test_depth_bias() fails in the TestBot VMs: d3d11.c:28093: Test failed: Got depth 4.99374978e-003, expected 4.99999994e-003. d3d11.c:28093: Test failed: Got depth 4.99374978e-003, expected 4.99999994e-003. d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28093: Test failed: Got depth 7.48750009e-003, expected 7.49999994e-003. d3d11.c:28093: Test failed: Got depth 7.48750009e-003, expected 7.49999994e-003. d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28093: Test failed: Got depth 1.24749998e-002, expected 1.24999999e-002. d3d11.c:28093: Test failed: Got depth 1.24749998e-002, expected 1.24999999e-002. d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28093: Test failed: Got depth 6.40899956e-001, expected 6.42500000e-001. d3d11.c:28093: Test failed: Got depth 6.40899956e-001, expected 6.42500000e-001. d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:27965: Test marked todo: Got 0xffffff00, expected 0x00ffffff at (0, 0, 0), sub-resource 0. d3d11.c:28101: Test failed: Got value 0x14745 (4.99373704e-003), expected 0x147ae (4.99999553e-003). d3d11.c:28101: Test failed: Got value 0x14745 (4.99373704e-003), expected 0x147ae (4.99999553e-003). d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected 0x85293 (3.25099845e-002). d3d11.c:28101: Test failed: Got value 0x1eab3 (7.48747632e-003), expected 0x1eb85 (7.49999329e-003). d3d11.c:28101: Test failed: Got value 0x1eab3 (7.48747632e-003), expected 0x1eb85 (7.49999329e-003). d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected 0x85293 (3.25099845e-002). d3d11.c:28101: Test failed: Got value 0x33190 (1.24750145e-002), expected 0x33333 (1.24999888e-002). d3d11.c:28101: Test failed: Got value 0x33190 (1.24750145e-002), expected 0x33333 (1.24999888e-002). d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected 0x85293 (3.25099845e-002). d3d11.c:28101: Test failed: Got value 0xa41204 (6.40899935e-001), expected 0xa47ae1 (6.42500022e-001). d3d11.c:28101: Test failed: Got value 0xa41204 (6.40899935e-001), expected 0xa47ae1 (6.42500022e-001). d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected 0x85293 (3.25099845e-002). d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected 0x85293 (3.25099845e-002). d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected 0x85293 (3.25099845e-002). d3d11.c:28110: Test failed: Got value 0x28e (9.97940032e-003), expected 0x290 (1.00099184e-002). d3d11.c:28110: Test failed: Got value 0x28e (9.97940032e-003), expected 0x290 (1.00099184e-002). d3d11.c:28110: Test failed: Got value 0x331 (1.24666209e-002), expected 0x334 (1.25123980e-002). d3d11.c:28110: Test failed: Got value 0x331 (1.24666209e-002), expected 0x334 (1.25123980e-002). d3d11.c:28110: Test failed: Got value 0x476 (1.74258030e-002), expected 0x47b (1.75020981e-002). d3d11.c:28110: Test failed: Got value 0x476 (1.74258030e-002), expected 0x47b (1.75020981e-002). d3d11.c:28110: Test failed: Got value 0xa411 (6.40894179e-001), expected 0xa47a (6.42496376e-001). d3d11.c:28110: Test failed: Got value 0xa411 (6.40894179e-001), expected 0xa47a (6.42496376e-001). https://test.winehq.org/data/patterns.html#d3d11:d3d11 These failures: * Don't happen on Debian 11 + Intel / KDE * Happen on Debian 11 + QXL + single-monitor * Happen on Debian 11 + QXL + multi-monitor * Don't happen on Debian Testing + QXL + multi-monitor So they are probably caused by some bug in the Debian 11 QXL support. 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 54642] New: Page fault on read access to 0x0000
by WineHQ Bugzilla Nov. 12, 2023

Nov. 12, 2023

https://bugs.winehq.org/show_bug.cgi?id=54642 Bug ID: 54642 Summary: Page fault on read access to 0x0000 Product: Wine-staging Version: 8.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: santafejayyt(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 74172 --> https://bugs.winehq.org/attachment.cgi?id=74172 Wine debugger backtrace on game start I'm attempting to run Konami's E-Amusement Cloud Sound Voltex Exceed Gear game, and the launcher and its components work fine, however when attempting to launch the game, the window opens, but the game does not start, and stays on a black screen. I have installed the required dependencies for the game via winetricks (DXVK / D3DX9, FAudio, & XACT). -- 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 24

[Bug 54183] New: wineserver crash when running d3d9:visual
by WineHQ Bugzilla Nov. 10, 2023

Nov. 10, 2023

https://bugs.winehq.org/show_bug.cgi?id=54183 Bug ID: 54183 Summary: wineserver crash when running d3d9:visual Product: Wine Version: 8.0-rc1 Hardware: x86-64 OS: Linux Status: NEW Keywords: testcase Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com CC: rbernon(a)codeweavers.com Distribution: --- d3d9:visual on this machine breaks somewhere in the middle, apparently while trying to do mode switches, and leaves the display switched off. Not sure what triggers it exactly; I've certainly had working runs on other machines. What's important is that then when d3d9_test.exe exits, it triggers a wined3d crash. Simple tl;dr version is that set_cursor_pos gets triggered not from a client request, and tries to access current->process, which crashes. The backtrace is: Core was generated by `/home/elizabeth/git/wine64/loader/../server/wineserver -d'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00005598e8b43ac0 in set_cursor_pos (desktop=desktop(a)entry=0x5598ea1ce5d0, x=32767, y=32767) at ../wine/server/queue.c:427 427 if ((device = current->process->rawinput_mouse) && (device->flags & RIDEV_NOLEGACY)) (gdb) bt #0 0x00005598e8b43ac0 in set_cursor_pos (desktop=desktop(a)entry=0x5598ea1ce5d0, x=32767, y=32767) at ../wine/server/queue.c:427 #1 0x00005598e8b43c7b in set_clip_rectangle (desktop=desktop(a)entry=0x5598ea1ce5d0, rect=rect(a)entry=0x0, send_clip_msg=send_clip_msg(a)entry=1) at ../wine/server/queue.c:476 #2 0x00005598e8b43da1 in set_foreground_input (input=0x0, desktop=0x5598ea1ce5d0) at ../wine/server/queue.c:483 #3 set_foreground_input (input=0x0, desktop=0x5598ea1ce5d0) at ../wine/server/queue.c:480 #4 thread_input_destroy (obj=0x5598ea1ba430) at ../wine/server/queue.c:1106 #5 0x00005598e8b3b144 in release_object (ptr=0x5598ea1ba430) at ../wine/server/object.c:451 #6 release_object (ptr=0x5598ea1ba430) at ../wine/server/object.c:440 #7 0x00005598e8b43800 in msg_queue_destroy (obj=0x5598ea1ae4d0) at ../wine/server/queue.c:1077 #8 0x00005598e8b3b144 in release_object (ptr=0x5598ea1ae4d0) at ../wine/server/object.c:451 #9 release_object (ptr=ptr(a)entry=0x5598ea1ae4d0) at ../wine/server/object.c:440 #10 0x00005598e8b3224e in release_object_from_handle (obj=0x5598ea1ae4d0) at ../wine/server/handle.c:115 #11 handle_table_destroy (obj=0x5598ea1d3810) at ../wine/server/handle.c:185 #12 0x00005598e8b3b144 in release_object (ptr=0x5598ea1d3810) at ../wine/server/object.c:451 #13 release_object (ptr=0x5598ea1d3810) at ../wine/server/object.c:440 #14 0x00005598e8b3260f in close_process_handles (process=process(a)entry=0x5598ea1ce7a0) at ../wine/server/handle.c:197 #15 0x00005598e8b3d990 in process_killed (process=0x5598ea1ce7a0) at ../wine/server/process.c:970 #16 remove_process_thread (process=0x5598ea1ce7a0, thread=thread(a)entry=0x5598ea1d4020) at ../wine/server/process.c:1020 #17 0x00005598e8b5b37f in kill_thread (thread=0x5598ea1d4020, violent_death=<optimized out>, violent_death(a)entry=0) at ../wine/server/thread.c:1294 #18 0x00005598e8b3dcb0 in kill_process (violent_death=0, process=0x5598ea1ce7a0) at ../wine/server/process.c:1077 #19 kill_process (process=0x5598ea1ce7a0, violent_death=<optimized out>) at ../wine/server/process.c:1058 #20 0x00005598e8b2d587 in fd_poll_event (event=<optimized out>, fd=<optimized out>) at ../wine/server/fd.c:542 #21 main_loop_epoll () at ../wine/server/fd.c:636 #22 0x00005598e8b2d7ee in main_loop () at ../wine/server/fd.c:992 #23 0x00005598e8b1ea7d in main (argc=2, argv=0x7ffd26625e48) at ../wine/server/main.c:237 Rémi, do you have any immediate insight on what we should be doing here? -- 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 16552] New: CreateIoCompletionPort fails in Chromium unit tests
by wine-bugs＠winehq.org Nov. 10, 2023

Nov. 10, 2023

http://bugs.winehq.org/show_bug.cgi?id=16552 Summary: CreateIoCompletionPort fails in Chromium unit tests Product: Wine Version: 1.1.10 Platform: Other URL: http://chromium.org OS/Version: other Status: NEW Keywords: download, source Severity: normal Priority: P2 Component: wineserver AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com http://src.chromium.org/viewvc/chrome/trunk/src/base/message_pump_win.cc contains the code port_.Set(CreateIoCompletionPort(INVALID_HANDLE_VALUE, NULL, NULL, 1)); DCHECK(port_.IsValid()); ... HANDLE port = CreateIoCompletionPort(file_handle, port_, key, 1); DCHECK(port == port_.Get()); The DCHECK fires when running one of the Chromium unit tests: wine Debug/ui_tests.exe ... 001b:Call KERNEL32.CreateFileW(00ed7208 L"\\\\.\\pipe\\chrome.ChromeTestingInterface:8.1",c0000000,00000000,00000000,00000003,40110000,00000000) ret=010e0220 001b:Ret KERNEL32.CreateFileW() retval=000000c0 ret=010e0220 ... 0021:Call KERNEL32.CreateIoCompletionPort(ffffffff,00000000,00000000,00000001) ret=01a304b3 0021:Ret KERNEL32.CreateIoCompletionPort() retval=000000c8 ret=01a304b3 0021:Call KERNEL32.CreateIoCompletionPort(000000c0,000000c8,00ed5aa0,00000001) ret=01a30760 trace:ntdll:NtSetInformationFile (0xc0,0x7cdee318,0x7cdee320,0x00000008,0x0000001e) 0021:Ret KERNEL32.CreateIoCompletionPort() retval=00000000 ret=01a30760 0021:Call KERNEL32.OutputDebugStringA(00ed95a8 "[26:33:1249:FATAL:message_pump_win.cc(428)] Check failed: port == port_.Get(). \r\n") ret=019a7af3 I think it's failing in wineserver for some reason during NtSetInformationFile in set_completion_info. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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 52792] New: Error messages for invalid .exe files could be improved
by WineHQ Bugzilla Nov. 10, 2023

Nov. 10, 2023

https://bugs.winehq.org/show_bug.cgi?id=52792 Bug ID: 52792 Summary: Error messages for invalid .exe files could be improved Product: Wine Version: 7.6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: aros(a)gmx.com Distribution: --- Trying to run a 0 byte .exe file under Wine will get you this: Application could not be started, or no application associated with the specified file. ShellExecuteEx failed: File not found. This doesn't look correct. -- 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 48004] New: winserver memory overflow
by WineHQ Bugzilla Nov. 10, 2023

Nov. 10, 2023

https://bugs.winehq.org/show_bug.cgi?id=48004 Bug ID: 48004 Summary: winserver memory overflow Product: Wine Version: 4.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: heiko(a)stark-jena.de Distribution: --- with default and 'wineserver -d2 -f -p10' settings I run simulations with the software Opensim (https://opensim.stanford.edu/) and restart the Opensim one after the other with a script. This seems to cause a memory overflow (> 64 GB). Kill wineserver helps to fix the memory overflow. Is there a way to debug this? Best regards, Heiko -- 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 52716] New: Sending key stroke (using [System.Windows.Forms.SendKeys]::SendWait) fails (seems to go into a loop?)
by WineHQ Bugzilla Nov. 10, 2023

Nov. 10, 2023

https://bugs.winehq.org/show_bug.cgi?id=52716 Bug ID: 52716 Summary: Sending key stroke (using [System.Windows.Forms.SendKeys]::SendWait) fails (seems to go into a loop?) Product: Wine Version: 7.4 Hardware: x86-64 URL: https://github.com/PowerShell/PowerShell/releases/down load/v7.0.3/PowerShell-7.0.3-win-x64.msi OS: Linux Status: NEW Keywords: dotnet, download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com Distribution: --- Created attachment 72077 --> https://bugs.winehq.org/attachment.cgi?id=72077 ps script Hi, I have a powershell script where I need to send a keystroke to a program. I found code snippet on the internet and made little script that I tested in windows (using powershell core) and it works. It sends ctrp^p to notepad, and that opens the printer-dialog correctly on windows. On wine however it doesn`t work, cpu-usage goes up so it seems to get into loop(???) Script (also see attachment): ################################################################### Start-Process "notepad.exe" Sleep 3 $WindowHandle = Get-Process | Where-Object { $_.MainWindowTitle -Match "Notepad" } | Select-Object -ExpandProperty MainWindowHandle [void][System.Reflection.Assembly]::LoadWithPartialName('System.Windows.Forms') [System.Windows.Forms.SendKeys]::SendWait("^{p}") ##################################################################### Steps to reproduce: 1. winetricks -q dotnet48 2. wget https://github.com/PowerShell/PowerShell/releases/download/v7.0.3/PowerShel… 3. wine PowerShell-7.0.3-win-x64.msi 4. Save the script from attachment as a.ps1 in current folder 5. wine pwsh -file ./a.ps1 Notepad opens but nothing really happens and cpu-usage goes up -- 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 53213] New: d3d11:d3d11 - test_texture() fails in the TestBot VMs
by WineHQ Bugzilla Nov. 10, 2023

Nov. 10, 2023

https://bugs.winehq.org/show_bug.cgi?id=53213 Bug ID: 53213 Summary: d3d11:d3d11 - test_texture() 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: --- d3d11:d3d11 - test_texture() fails in the TestBot VMs: d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff0000ff at (0, 0). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff00ffff at (1, 0). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff00ff00 at (2, 0). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffffff00 at (3, 0). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffff0000 at (0, 1). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffff00ff at (1, 1). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff000000 at (2, 1). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff7f7f7f at (3, 1). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffffffff at (0, 2). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffffffff at (1, 2). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffffffff at (2, 2). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff000000 at (3, 2). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffffffff at (0, 3). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff000000 at (2, 3). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff000000 at (3, 3). https://test.winehq.org/data/patterns.html#d3d11:d3d11 These failures don't happen on my box which has an Intel graphics card instead of QEmu's QXL graphics card. Note also that these failures still happen on my debian11 VM which has a single monitor instead of the TestBot VMs' multi-monitor setup. So this seems to be related to the VMs QXL GPU. Note that despite being systematic these failures could cause false positives (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 5

[Bug 54519] New: d3d9:visual - test_mipmap_upload() fails on AMD and Nvidia GPUs
by WineHQ Bugzilla Nov. 10, 2023

Nov. 10, 2023

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 54399] New: d3d11:d3d11 - test_vertex_formats() fails on Windows 11 + AMD
by WineHQ Bugzilla Nov. 10, 2023

Nov. 10, 2023

https://bugs.winehq.org/show_bug.cgi?id=54399 Bug ID: 54399 Summary: d3d11:d3d11 - test_vertex_formats() fails on Windows 11 + 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 d3d11:d3d11 - test_vertex_formats() fails on Windows 11 + AMD: d3d11.c:34906: Test failed: Format 0x58: Got {3.96078438e-001, 2.62745112e-001, 1.29411772e-001, 1.42236653e-019}, expected {3.96078438e-001, 2.62745112e-001, 1.29411772e-001, 1.00000000e+000} at (0, 0), sub-resource 0. See w11pro64-amd in https://test.winehq.org/data/patterns.html#d3d11:d3d11 The failures started on 2023-01-24, that is on the date the test was added by this commit: commit dc19f5c517af5d04bebb4f26bd79220b02f1ba64 Author: Zebediah Figura <zfigura(a)codeweavers.com> AuthorDate: Wed Jan 11 19:25:11 2023 -0600 d3d11/tests: Add a basic test for vertex formats. -- 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