wine-bugs June 2022

wine-bugs@winehq.org

1 participants
3974 discussions

[Bug 52919] New: Resident Evil 5 DVD shows E_INVALIDARG:XLiveInitialize(&xii)
by WineHQ Bugzilla 22 Jun '22

22 Jun '22

https://bugs.winehq.org/show_bug.cgi?id=52919 Bug ID: 52919 Summary: Resident Evil 5 DVD shows E_INVALIDARG:XLiveInitialize(&xii) Product: Wine Version: 7.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: BOBBLOG(a)protonmail.com Distribution: --- Created attachment 72299 --> https://bugs.winehq.org/attachment.cgi?id=72299 RE5-D3D Resident Evil 5 DVD shows E_INVALIDARG:XLiveInitialize(&xii) when i launch the game. This was tested with wine-7.7 in a clean wine prefix. I'll attach +d3d log. -- 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 53192] New: FlexiPDF 3.0.3 crashes when moving window: dlls/ntdll/unix/thread.c:1737: ntdll_set_exception_jmp_buf: Assurance »!jmp || !ntdll_get_thread_data()->jmp_buf« not fulfilled
by WineHQ Bugzilla 22 Jun '22

22 Jun '22

https://bugs.winehq.org/show_bug.cgi?id=53192 Bug ID: 53192 Summary: FlexiPDF 3.0.3 crashes when moving window: dlls/ntdll/unix/thread.c:1737: ntdll_set_exception_jmp_buf: Assurance »!jmp || !ntdll_get_thread_data()->jmp_buf« not fulfilled Product: Wine Version: 7.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: postix(a)posteo.eu Distribution: --- Created attachment 72629 --> https://bugs.winehq.org/attachment.cgi?id=72629 Terminal output ### Issue FlexiPDF 3.0.3 crashes when trying to move its window by dragging the titlebar. ### Download link `https://www.softmaker.net/down/flexipdf2022.exe` ### System Operating System: Fedora Linux 36 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.18.5-200.fc36.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Graphics Processor: AMD RENOIR -- 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 50103] i have a error help me
by WineHQ Bugzilla 22 Jun '22

22 Jun '22

https://bugs.winehq.org/show_bug.cgi?id=50103 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |ABANDONED CC| |fgouget(a)codeweavers.com Status|NEEDINFO |RESOLVED --- Comment #2 from François Gouget <fgouget(a)codeweavers.com> --- No answer to a year-old request for information. -- 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 43347] New: valgrind shows an unintialized read in dlls/iphlpapi/ tests/iphlpapi.c
by wine-bugs＠winehq.org 22 Jun '22

22 Jun '22

https://bugs.winehq.org/show_bug.cgi?id=43347 Bug ID: 43347 Summary: valgrind shows an unintialized read in dlls/iphlpapi/tests/iphlpapi.c Product: Wine Version: 2.12 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: iphlpapi Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Gentoo ../../../tools/runtest -q -P wine -T ../../.. -M iphlpapi.dll -p iphlpapi_test.exe.so iphlpapi && touch iphlpapi.ok ==10952== Syscall param ioctl(SIOCGIFINDEX) points to uninitialised byte(s) ==10952== at 0x4338F79: ioctl (syscall-template.S:84) ==10952== by 0x435916D: if_nametoindex (if_index.c:47) ==10952== by 0x4B25E43: getInterfaceIndexByName (ifenum.c:143) ==10952== by 0x4B2EC7E: IPHLP_if_nametoindex (iphlpapi_main.c:3233) ==10952== by 0x488198E: test_interface_identifier_conversion (iphlpapi.c:1958) ==10952== by 0x48831AB: func_iphlpapi (iphlpapi.c:2230) ==10952== by 0x4884014: run_test (test.h:603) ==10952== by 0x4884465: main (test.h:687) ==10952== Address 0x4b0f8c0 is on thread 1's stack ==10952== in frame #1, created by if_nametoindex (if_index.c:35) ==10952== Uninitialised value was created by a stack allocation ==10952== at 0x4359141: if_nametoindex (if_index.c:41) ==10952== -- 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 1

[Bug 53241] New: wtsapi32:wtsapi - test_WTSEnumerateProcessesW() crashes if a process exits during the test?
by WineHQ Bugzilla 22 Jun '22

22 Jun '22

https://bugs.winehq.org/show_bug.cgi?id=53241 Bug ID: 53241 Summary: wtsapi32:wtsapi - test_WTSEnumerateProcessesW() crashes if a process exits during the test? Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: wtsapi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com wtsapi32:wtsapi - test_WTSEnumerateProcessesW() crashes if a process exits during the test? Here is the failure: wtsapi.c:78: Test failed: failed to find pid 0x20e4 wtsapi.c:82: this is the last test seen before the exception 0618:wtsapi: unhandled exception c0000005 at 0000000000401848 https://test.winehq.org/data/patterns.html#wtsapi32:wtsapi The crash happens when check_wts_process_info() dereferences the NULL pointer returned by find_nt_process_info(). So presumably the test must check that some API does return information about at least some processes but it seems allowances should be made for processes exiting during the test. -- 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 53200] New: WET (a dotnet45 framework for web printing terminal): black block covered the content. i can edit with libreoffice draw. the content is there, but all covered with black block.
by WineHQ Bugzilla 22 Jun '22

22 Jun '22

https://bugs.winehq.org/show_bug.cgi?id=53200 Bug ID: 53200 Summary: WET (a dotnet45 framework for web printing terminal): black block covered the content. i can edit with libreoffice draw. the content is there, but all covered with black block. Product: Wine Version: 7.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P1 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dejoebad(a)yahoo.com Distribution: --- WET (a dotnet45 framework for web printing terminal): black block covered the content. i can edit with libreoffice draw. the content is there, but all covered with black block. https://www.instagram.com/p/Ce33e8vJ-n0 this is the output from windows and wine https://www.instagram.com/p/CfBo3hVPd2d this is what actually behind the black blocks. i'd print the file to pdf and edit with libreoffice draw. -- 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 11

[Bug 44337] New: d3d9/tests/device.ok fails on Nvidia (Nouveau drivers) in test_occlusion_query()
by wine-bugs＠winehq.org 21 Jun '22

21 Jun '22

https://bugs.winehq.org/show_bug.cgi?id=44337 Bug ID: 44337 Summary: d3d9/tests/device.ok fails on Nvidia (Nouveau drivers) in test_occlusion_query() Product: Wine Version: 3.0-rc5 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Distribution: --- with the following lines: device.c:5915: Test failed: Got unexpected hr 0x1. device.c:5919: Test failed: Got unexpected hr 0x1. device.c:5920: Test failed: Got unexpected query result 0xffffffffffffffff. It would be nice to fix this as this is currently the only D3D test failure on the cw2 test machine. -- 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 3

[Bug 48820] New: user32:win "unexpected 0x7fff message" Japanese Windows 10 failures
by WineHQ Bugzilla 21 Jun '22

21 Jun '22

https://bugs.winehq.org/show_bug.cgi?id=48820 Bug ID: 48820 Summary: user32:win "unexpected 0x7fff message" Japanese Windows 10 failures Product: Wine Version: unspecified Hardware: x86 OS: Windows Status: NEW Severity: major Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The TestBot's w1064v1809-zh_CN configuration runs the tests on Windows 10 1809 in a Chinese locale. This test configuration gets unique failures in user32:win: win.c:3852: Test failed: hwnd 007404D2 message 7fff win.c:3858: Test failed: message 7fff available win.c:3931: Test failed: hwnd 007404D2/0054050A message 7fff win.c:3934: Test failed: hwnd 007404D2/0054050A message 7fff Note how these messages are very similar to the IME messages in bug 48819. However 0x7fff is a totally unknown message: all I can say about it is that it's WM_APP-1. So maybe it's another IME system. Maybe not? See: https://test.winehq.org/data/tests/user32:win.html However note that quite often WineTest fails to submit its results to test.winehq.org, typically because it times out. So you can more easily find the latest failure by looking for the "32 bit WineTest: base VMs" jobs on the TestBot. Finally, three of these messages include the window handles which means they are "always new". Because of this the TestBot will mistakenly attribute the failure to any user32 patch submitted to wine-devel, which should cause them to be rejected. So I bumped the priority on this bug. -- 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 53228] New: dxgi:dxgi - test_swapchain_window_styles() sometimes fails on Windows 10
by WineHQ Bugzilla 21 Jun '22

21 Jun '22

https://bugs.winehq.org/show_bug.cgi?id=53228 Bug ID: 53228 Summary: dxgi:dxgi - test_swapchain_window_styles() sometimes fails on Windows 10 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com dxgi:dxgi - test_swapchain_window_styles() sometimes fails on Windows 10: dxgi.c:6125: Test failed: Test 4: Got unexpected exstyle 0x108, expected 0x100. dxgi.c:6141: Test failed: Test 4: Got unexpected exstyle 0x108, expected 0x100. dxgi.c:6169: Test failed: Test 4: Got unexpected exstyle 0x108, expected 0x100. dxgi.c:6196: Test failed: Test 4: Got unexpected exstyle 0x108, expected 0x100. dxgi.c:6212: Test failed: Test 4: Got unexpected exstyle 0x108, expected 0x100. https://test.winehq.org/data/patterns.html#dxgi:dxgi This failure has been seen on Windows 10 1507 to 21H2. Furthermore, because of the test's multi-threading it has an elevated risk of causing 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 1

[Bug 53209] New: GTA San Andreas. Audio bug
by WineHQ Bugzilla 21 Jun '22

21 Jun '22

https://bugs.winehq.org/show_bug.cgi?id=53209 Bug ID: 53209 Summary: GTA San Andreas. Audio bug Product: Wine Version: 7.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jon9097(a)gmail.com Distribution: --- When you rotate the camera around the character, the sound almost completely goes from one speaker to the other and back again. I did not find anything strange in the logs. This problem has been in wine for as long as I can remember, no such thing on windows. I wish that it was solved and the sound was distributed normally. -- 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 53173] New: user32:input - test_Input_mouse() randomly fails to get the expected mouse button or hit-test messages
by WineHQ Bugzilla 21 Jun '22

21 Jun '22

https://bugs.winehq.org/show_bug.cgi?id=53173 Bug ID: 53173 Summary: user32:input - test_Input_mouse() randomly fails to get the expected mouse button or hit-test messages 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:input - test_Input_mouse() randomly fails to get the expected mouse button or hit-test messages: input.c:3398: Test failed: expected WM_LBUTTONDOWN message input.c:3399: Test failed: expected WM_LBUTTONUP message input.c:3426: Test failed: expected WM_NCHITTEST message input.c:3427: Test failed: expected WM_RBUTTONDOWN message input.c:3428: Test failed: expected WM_RBUTTONUP message input.c:3457: Test failed: expected WM_LBUTTONDOWN message input.c:3458: Test failed: expected WM_LBUTTONUP message input.c:3511: Test failed: expected loop with WM_NCHITTEST messages input.c:3564: Test failed: expected WM_LBUTTONDOWN message input.c:3565: Test failed: expected WM_LBUTTONUP message https://test.winehq.org/data/patterns.html#user32:input The failure list is always the same except for the first two which are not always present. This happened on w7u-2qxl, w86 and most Windows 10 1607+ test configurations up to 21H2. So it's not a quirk of a specific Windows version. -- 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 53212] New: d3d11:d3d11 - test_clear_image_unordered_access_view() fails in the TestBot VMs
by WineHQ Bugzilla 21 Jun '22

21 Jun '22

https://bugs.winehq.org/show_bug.cgi?id=53212 Bug ID: 53212 Summary: d3d11:d3d11 - test_clear_image_unordered_access_view() 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_clear_image_unordered_access_view() fails in the TestBot VMs: d3d11.c:16719: Test failed: Dim 0, Test 15: At layer 0, (0,0,0), expected 0x00c01001, got 0x00000000. d3d11.c:16719: Test failed: Dim 1, Test 15: At layer 0, (0,0,0), expected 0x00c01001, got 0x00000000. d3d11.c:16719: Test failed: Dim 2, Test 15: At layer 0, (0,0,0), expected 0x00c01001, got 0x00000000. 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. Despite being systematic these failures someimes cause false positives because of the test's multi-threading: sometimes these failures come before the test_texture() failures (Test 60:), and most of the time they come after. The order change causes the TestBot's diffing algorithm to consider them to be new failures if they come in an order it has not seen before. -- 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 53148] New: mfplay:mfplay - test_media_item() has a rare crash on Windows 8
by WineHQ Bugzilla 21 Jun '22

21 Jun '22

https://bugs.winehq.org/show_bug.cgi?id=53148 Bug ID: 53148 Summary: mfplay:mfplay - test_media_item() has a rare crash on Windows 8 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: mfplat Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com mfplay:mfplay - test_media_item() has a rare crash on Windows 8: mfplay.c:295: Test failed: Unexpected hr 0xc00d3e85. mfplay.c:295: this is the last test seen before the exception 0afc:mfplay: unhandled exception c0000005 at 0040121C https://test.winehq.org/data/patterns.html#mfplay:mfplay This looks like it is specific to the TestBot VMs: there is no record of this failure happening on the cw-gtx560 or cw-rx460 machines. The failure rate is about 6.8%. -- 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 53223] New: shell32:shlfileop - test_sh_path_prepare() fails in the Japanese and Chinese locales in Wine
by WineHQ Bugzilla 21 Jun '22

21 Jun '22

https://bugs.winehq.org/show_bug.cgi?id=53223 Bug ID: 53223 Summary: shell32:shlfileop - test_sh_path_prepare() fails in the Japanese and Chinese locales in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- shell32:shlfileop - test_sh_path_prepare() fails in the Japanese and Chinese locales in Wine: shlfileop.c:2463: Test failed: Could not find unique multibyte representation for directory name using default codepage. https://test.winehq.org/data/patterns.html#shell32:shlfileop Note that the conversion fails on Windows too which probably makes sense for these locales. So the win_skip() should maybe be a regular skip() instead. -- 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 35765] New: gdi32:font / richedit:editor / msvcrt:locale / msvcrt:string fails on newtb-w7u
by wine-bugs＠winehq.org 21 Jun '22

21 Jun '22

http://bugs.winehq.org/show_bug.cgi?id=35765 Bug ID: 35765 Summary: gdi32:font / richedit:editor / msvcrt:locale / msvcrt:string fails on newtb-w7u Product: Wine Version: 1.7.14 Hardware: x86 OS: Linux Status: NEW Keywords: source, testcase Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fracting(a)gmail.com CC: fgouget(a)codeweavers.com http://test.winehq.org/data/770213e16c6918728f69ea33545fafabd59dbc8e/win7_n… It seems these tests are all related to locales, and they fail much more on this machine than other machine. SystemDefaultLCID 411 UserDefaultLCID 409 ThreadLocale 411 UserDefaultUILanguage 411 ThreadUILanguage 411 It doesn't happen frequently that we have a vm with different UserDefaultLCID and SystemDefaultLCID. I'm not very sure if we want to support such a case, it maybe useful in real world for some body. (I personally don't care too much lol) François, is there any chance to try: 1. set all LCIDs to 0x409 (Simplified Chinese) 2. set all LCIDs to 0x411 (Japanese) Then reboot the vm, then resubmit the tests, to see if there is any improvement? Thanks for your great work! Everyone wants your patch/work :) -- 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 23

[Bug 53221] New: user32:winstation - test_enumdesktops() sometimes fails to open the desktop on Windows 7 & 8
by WineHQ Bugzilla 21 Jun '22

21 Jun '22

https://bugs.winehq.org/show_bug.cgi?id=53221 Bug ID: 53221 Summary: user32:winstation - test_enumdesktops() sometimes fails to open the desktop on Windows 7 & 8 Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- user32:winstation - test_enumdesktops() sometimes fails to open the desktop on Windows 7 & 8: winstation.c:411: desktop_callbackA called with argument WinSta0 winstation.c:411: desktop_callbackA called with argument winsta_test winstation.c:420: open_desktop_callbackA called with argument new_desk winstation.c:426: Test failed: Could not open desktop new_desk! winstation.c:420: open_desktop_callbackA called with argument rawinput_test_desktop winstation.c:420: open_desktop_callbackA called with argument Default winstation.c:420: open_desktop_callbackA called with argument Winlogon winstation.c:452: Test failed: LastError is set to 00000002 winstation.c:411: desktop_callbackA called with argument rawinput_test_desktop https://test.winehq.org/data/patterns.html#user32:winstation These failures have been seen on w7u-adm, w7u-el, w8 and w8adm but the failure rate is pretty low (<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 1

[Bug 53219] New: winmm:mci - test_asyncWAVE() sometimes fails due to a timing issue
by WineHQ Bugzilla 21 Jun '22

21 Jun '22

https://bugs.winehq.org/show_bug.cgi?id=53219 Bug ID: 53219 Summary: winmm:mci - test_asyncWAVE() sometimes fails due to a timing issue Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com winmm:mci - test_asyncWAVE() sometimes fails due to a timing issue: mci.c:980: Test failed: 706ms is not in the expected 350-600ms range https://test.winehq.org/data/patterns.html#winmm:mci This only happened once on the TestBot but happens a bit more frequently on fgtb-w10pro64 where the host is typically more busy. -- 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 53214] New: d3d11:d3d11 - test_negative_viewports() fails in the TestBot VMs
by WineHQ Bugzilla 21 Jun '22

21 Jun '22

https://bugs.winehq.org/show_bug.cgi?id=53214 Bug ID: 53214 Summary: d3d11:d3d11 - test_negative_viewports() 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_negative_viewports() fails in the TestBot VMs: d3d11.c:28330: Test succeeded inside todo block: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28339: Test succeeded inside todo block: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28330: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28339: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28330: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28339: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. 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 * Happen on Debian Testing + QXL + multi-monitor So they seems to be related to the VMs QXL GPU. 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 1

[Bug 53215] New: d3d11:d3d11 - test_fractional_viewports() fails in the TestBot VMs
by WineHQ Bugzilla 21 Jun '22

21 Jun '22

https://bugs.winehq.org/show_bug.cgi?id=53215 Bug ID: 53215 Summary: d3d11:d3d11 - test_fractional_viewports() 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_fractional_viewports() fails in the TestBot VMs: d3d11.c:28276: Test failed: Got texcoord {8.43750119e-001, 1.56249881e-001}, expected {8.43750000e-001, 1.56250000e-001} at (3, 3), offset 1.25000000e-001. d3d11.c:28276: Test failed: Got texcoord {8.71093690e-001, 1.28906310e-001}, expected {8.71093750e-001, 1.28906250e-001} at (3, 3), offset 1.56250000e-002. d3d11.c:28276: Test failed: Got texcoord {7.51953065e-001, 2.48046935e-001}, expected {7.51953125e-001, 2.48046875e-001} at (3, 3), offset 4.92187500e-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 * Happen on Debian Testing + QXL + multi-monitor So they seems to be related to the VMs QXL GPU. 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 1

[Bug 53204] New: shell32:autocomplete - test_custom_source() sometimes gets DropDown failures on Windows
by WineHQ Bugzilla 20 Jun '22

20 Jun '22

https://bugs.winehq.org/show_bug.cgi?id=53204 Bug ID: 53204 Summary: shell32:autocomplete - test_custom_source() sometimes gets DropDown failures on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com shell32:autocomplete - test_custom_source() sometimes gets DropDown failures on Windows: autocomplete.c:778: Test failed: AutoComplete DropDown should be visible autocomplete.c:788: Test failed: AutoComplete DropDown should be hidden https://test.winehq.org/data/patterns.html#shell32:autocomplete The second failure is not always present. They only happen on Windows 10. -- 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 53203] New: shell32:autocomplete - test_aclist_expand() sometimes fails on Windows
by WineHQ Bugzilla 20 Jun '22

20 Jun '22

https://bugs.winehq.org/show_bug.cgi?id=53203 Bug ID: 53203 Summary: shell32:autocomplete - test_aclist_expand() sometimes fails on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com shell32:autocomplete - test_aclist_expand() sometimes fails on Windows: autocomplete.c:534: Test failed: Expected 3 expansions, got 2 autocomplete.c:535: Test failed: Expected L"test\\foo\\bar\\baz_bbq\\", got L"test\\foo\\bar\\" autocomplete.c:536: Test failed: Expected 3 resets, got 2 autocomplete.c:541: Test failed: Expected 4 expansions, got 3 autocomplete.c:543: Test failed: Expected 4 resets, got 3 autocomplete.c:547: Test failed: Expected 4 expansions, got 3 autocomplete.c:548: Test failed: Expected 5 resets, got 4 autocomplete.c:553: Test failed: Expected 5 expansions, got 4 autocomplete.c:555: Test failed: Expected 6 resets, got 5 autocomplete.c:560: Test failed: Expected 6 expansions, got 5 autocomplete.c:562: Test failed: Expected 7 resets, got 6 https://test.winehq.org/data/patterns.html#shell32:autocomplete These failures have been seen on Windows 10 1809 and 21H1. The w8adm VM also got pretty similar failures once: autocomplete.c:541: Test failed: Expected 4 expansions, got 3 autocomplete.c:542: Test failed: Expected L"test\\", got L"test\\foo\\bar\\baz_bbq\\" autocomplete.c:543: Test failed: Expected 4 resets, got 3 autocomplete.c:547: Test failed: Expected 4 expansions, got 3 autocomplete.c:548: Test failed: Expected 5 resets, got 4 autocomplete.c:553: Test failed: Expected 5 expansions, got 4 autocomplete.c:555: Test failed: Expected 6 resets, got 5 autocomplete.c:560: Test failed: Expected 6 expansions, got 5 autocomplete.c:562: Test failed: Expected 7 resets, got 6 -- 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 32083] New: Diablo III: Missing logo on startup
by wine-bugs＠winehq.org 20 Jun '22

20 Jun '22

http://bugs.winehq.org/show_bug.cgi?id=32083 Bug #: 32083 Summary: Diablo III: Missing logo on startup Product: Wine Version: 1.5.16 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: sworddragon2(a)aol.com Classification: Unclassified On starting Diablo III the logo before the game starts is transparent. If I'm going with the mouse over it the cursor will be hidden. -- 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 34

[Bug 35213] New: Kane & Lynch: Dead Men demo needs native d3dx9_31
by wine-bugs＠winehq.org 20 Jun '22

20 Jun '22

http://bugs.winehq.org/show_bug.cgi?id=35213 Bug ID: 35213 Summary: Kane & Lynch: Dead Men demo needs native d3dx9_31 Product: Wine Version: 1.7.9 Hardware: x86 URL: http://www.gamefront.com/files/9394790/Kane___Lynch__D ead_Men_Demo OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com CC: wine-bugs(a)winehq.org Classification: Unclassified First d3dx9_36 should be installed. Demo crashes with fixme:d3dx:D3DXCreateEffectEx (0x20f000, 0x1e71cb58, 45008, (nil), (nil), (nil), 0x10900, 0x1685a8, 0x1a99cf4, 0x1a99cec): semi-stub after the same issue as for bug 35137, but this time should be d3dx9_31. -- 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 15

[Bug 51158] New: advapi32:lsa fails in French on Windows 2004
by WineHQ Bugzilla 20 Jun '22

20 Jun '22

https://bugs.winehq.org/show_bug.cgi?id=51158 Bug ID: 51158 Summary: advapi32:lsa fails in French on Windows 2004 Product: Wine Version: 6.8 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- advapi32:lsa fails in French on Windows 2004 because the name of the 'Everyone' group does not seem to be translated anymore: lsa.c:407: Test failed: expected L"Tout le monde", got L"Everyone" That's a bit surprising. Maybe the Windows translation was slightly out of date? * This should be checked on Windows 2009 but we don't have a test configuration for it. * The test also has a translation for German but we don't have a test configuration for German. There should really be one so we can validate the test. Once the results for German and Windows 2009 are known the test can be updated. -- 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 48108] New: kernel32:comm - QEmu's serial baud rate emulation is broken
by WineHQ Bugzilla 20 Jun '22

20 Jun '22

https://bugs.winehq.org/show_bug.cgi?id=48108 Bug ID: 48108 Summary: kernel32:comm - QEmu's serial baud rate emulation is broken Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- kernel32:comm got a failure when running on Wine on the TestBot VM: comm.c:932: Test failed: OutQueue should not be empty This happens in test_waittxempty(): // Open the serial device hcom = test_OpenComm(TRUE); // Here it is already set to 150 bps because that's how a // previous test left it ... // Write 17 bytes in overlaped mode. // At 150 bauds this should take at least 900 ms res = WriteFile(hcom, tbuf, sizeof(tbuf), &bytes, &ovl_write); // Leaving us plenty of time to get to ClearCommError(hcom, &errors, &stat); ... // And here we expect the serial device to still have data to send. // But because QEmu sends the data at > 400 kbps this often fails ok(stat.cbOutQue != 0, "OutQueue should not be empty\n"); That QEmu does not enforce the set baud rate can also be verified from the command line: # stty -F /dev/ttyS0 speed 9600 baud; line = 0; -brkint -imaxbel # dd if=/dev/zero of=/dev/ttyS0 bs=1 count=10000 10000+0 records in 10000+0 records out 10000 bytes (10 kB, 9.8 KiB) copied, 0.224432 s, 44.6 kB/s # stty -F /dev/ttyS0 300 # stty -F /dev/ttyS0 speed 300 baud; line = 0; -brkint -imaxbel # dd if=/dev/zero of=/dev/ttyS0 bs=1 count=10000 10000+0 records in 10000+0 records out 10000 bytes (10 kB, 9.8 KiB) copied, 0.679127 s, 14.7 kB/s Back to the kernel32:comm failure: * It did not happen for a long time and started happening on the debian10 VM on 2019-10-03. That corresponds to the time I added the winetest user to the dialout group, thus giving it access to /dev/ttyS0. * The same issue happens in the Windows VMs, but the ok() call has a broken() clause which hides the issue there. So: 1. The bug needs to be reported to QEmu. 2. See why speeds below 9600 bps are not allowed. 3. We may want a better check for this issue: directly check that the baud rate is respected. This would allow us to skip tests that depend on the baud rate and ditch the broken() clause. 4. If the above does not work out the serial device should be removed from the Wine QEmu VMs. -- 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs June 2022