- Wine-Bugs - list.winehq.org

[Bug 26978] New: tokenadmin.exe crash : Unimplemented function winscard.dll.SCardListReadersA
by wine-bugs＠winehq.org Nov. 30, 2022

Nov. 30, 2022

http://bugs.winehq.org/show_bug.cgi?id=26978 Summary: tokenadmin.exe crash : Unimplemented function winscard.dll.SCardListReadersA Product: Wine Version: 1.3.18 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: fracting(a)gmail.com Created an attachment (id=34407) --> (http://bugs.winehq.org/attachment.cgi?id=34407) LOG: tokenadmin.exe crash tokenadmin.exe is a smart card reader manager from ICBC online bank. 1. donwload http://www.icbc.com.cn/icbc/html/download/dkq/SafeSign_ICBC_Per.exe 2. install SafeSign_ICBC_Per.exe with wine $ LANG=en_US.utf8 wine SafeSign_ICBC_Per.exe 3. run tokenadmin.exe $ cd $WINEPREFIX/"drive_c/Program Files/ICBCEbankTools/G&D/Management Utility" $ wine tokenadmin.exe see LOG: tokenadmin.exe crash -- 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 14

[Bug 53963] New: d3d8:device & d3d9:device sometimes break threading and WineTest
by WineHQ Bugzilla Nov. 30, 2022

Nov. 30, 2022

https://bugs.winehq.org/show_bug.cgi?id=53963 Bug ID: 53963 Summary: d3d8:device & d3d9:device sometimes break threading and WineTest 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: --- d3d8:device & d3d9:device sometimes break threading, causing all the tests that follow to get stuck. The typical symptom is a series of tests returning 258: d3d9:d3d9ex:080c done (0) in 43s 9467B d3d9:device start dlls/d3d9/tests/device.c d3d9:device:0278 done (258) in 120s 0B d3d9:stateblock start dlls/d3d9/tests/stateblock.c d3d9:stateblock:0288 done (258) in 120s 0B d3d9:visual start dlls/d3d9/tests/visual.c d3d9:visual:0290 done (258) in 120s 0B See https://test.winehq.org/data/patterns.html When this happens all the tests that follow get stuck which makes it impossible to run the full WineTest suite, hence the lack of WineTest results on some machines in the patterns page above. Notes: * This can also happen in d3d8:device. Consequently the first test that gets stuck is either d3d8:stateblock or d3d9:stateblock. * winedbg also gets stuck as soon as it displays the prompt :-( * This only impacts dual-screen configurations. This is why this breaks the debian11 and debiant (dual-screen) VMs but not debian11b and fgtbdebian11 (single-screen). Note that in the run above there is no d3d9:device trace which means it did not run right but there is no other indication of what is wrong. Fortunately on one run d3d9:device produced a proper crash dump implicating RtlCreateUserThread() which would make sense given the symptoms: d3d9:device start dlls/d3d9/tests/device.c device.c:780: Test marked todo: Test 0: Got unexpected FVF 0, expected 0x2. device.c:780: Test marked todo: Test 1: Got unexpected FVF 0, expected 0x4. device.c:1119: Tests skipped: Multisampling not supported for D3DFMT_X8R8G8B8, skipping test. device.c:4821: Test failed: Received unexpected WM_SIZE message. device.c:2852: Test failed: Failed to create a D3D object. Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x00434da7). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:00434da7 ESP:0071f7b0 EBP:0071f868 EFLAGS:00010246( R- -- I Z- -P- ) EAX:00000000 EBX:00000000 ECX:0071f750 EDX:00000000 ESI:005a0068 EDI:0071f824 Stack dump: 0x0071f7b0: 00000000 004de71c 004df984 00cf0000 0x0071f7c0: 00000064 00000064 000000a0 000000a0 0x0071f7d0: 00000000 00000000 00000000 00000000 0x0071f7e0: 00000000 00000002 00000012 005a0068 0x0071f7f0: 688e32f0 00001897 00000000 00000000 0x0071f800: 00000000 004df9fc 00000000 00000007 Backtrace: =>0 0x00434da7 in d3d9_test (+0x34da7) (0x0071f868) 1 0x00459367 in d3d9_test (+0x59367) (0x0071fde8) 2 0x004d8151 in d3d9_test (+0xd8151) (0x0071fee8) 3 0x004d7b3f in d3d9_test (+0xd7b3f) (0x0071ff30) 4 0x7b62a1f0 in kernel32 (+0x2a1f0) (0x0071ff48) 5 0x7bc5d727 in ntdll (+0x5d727) (0x0071ff5c) 6 0x7bc5df50 RtlCreateUserThread(entry=004D7AC0, arg=7FFD1000) [Z:\home\winetest\tools\testbot\var\wine\dlls\ntdll\thread.c:306] in ntdll (0x0071ffec) 0x00434da7 d3d9_test+0x34da7: movl 0x0(%ebx),%eax And on stderr: 0658:err:d3d:wined3d_adapter_create_output Failed to initialise output L"\\\\.\\DISPLAY1", hr 0x80070057. wine: Unhandled page fault on read access to 00000000 at address 00434DA7 (thread 0658), starting debugger... The million dollar question: how to reproduce the failure? * First you need a dual-screen test configuration. * The crash is not systematic. It can be necessary to run the test 4 - 8 maybe 10 times to get a crash. It's hard to tell. * After some runs d3d9:device gets an underflow in GenerateRampFromGamma() and crashes from that. I don't have a log of that crash but I remember that the gamma was around 0.00003 (plus or minus a few zeroes). So it is likely that the test does not restore the gamma correctly, resulting in it running with this nonsensically low gamma value after a while. Regardless, this seems to prevent d3d*:device from crashing in the way we want which means after a few runs it may be necessary to restart the X server :-( * Also sometimes, again after running the tests a number of times, one of the screens 'disappears' (virt-viewer says something like 'connecting to display' or it will show a single abnormally wide desktop) and then the issue cannot be reproduced anymore. This also requires restarting the X server :-( This failure started on 2022-11-17 but because it is such a pain to reproduce and even more to bisect I was not able to pinpoint the commit causing it. However Rémi points out that it first appeared in the following merge request: https://gitlab.winehq.org/wine/wine/-/merge_requests/1399 And when that got merged into Wine all hell broke loose: all debian11 test runs started timing out. It's not clear how it's related to threading though. Also it only touches programs/explorer so it's strange that it would cause threading issues in d3d9:device. So it's possible it only triggers a preexisting bug somehow. -- 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 51153] New: A winegstreamer change caused a new quartz:filtergraph failure in Wine
by WineHQ Bugzilla Nov. 30, 2022

Nov. 30, 2022

https://bugs.winehq.org/show_bug.cgi?id=51153 Bug ID: 51153 Summary: A winegstreamer change caused a new quartz:filtergraph failure in Wine Product: Wine Version: 6.8 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winegstreamer Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- quartz:filtergraph started failing in Wine on 2021-04-26: http://winetest.dolphin/data/patterns.html#quartz:filtergraph filtergraph.c:440: Test failed: GetState() failed: 40237 Strangely this failure only happens on the TestBot's debiant2 VM. A bisect showed this failure to be caused by the patch below: commit d7fecebe93938bf1ef2349ac74413e28d6b8e153 Author: Anton Baskanov <baskanov(a)gmail.com> Date: Mon Apr 26 09:51:24 2021 +0700 winegstreamer: Allow setting the stop position to the stream duration. Since we no longer stop the GStreamer pipeline, it does not reset the stop position for us. Fixes a hang during intro video playback in RC Cars. Signed-off-by: Anton Baskanov <baskanov(a)gmail.com> Signed-off-by: Zebediah Figura <z.figura12(a)gmail.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> See also: https://www.winehq.org/pipermail/wine-devel/2021-April/185904.html -- 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 53998] New: vbscript tests fail in englisch UTF8 locale
by WineHQ Bugzilla Nov. 30, 2022

Nov. 30, 2022

https://bugs.winehq.org/show_bug.cgi?id=53998 Bug ID: 53998 Summary: vbscript tests fail in englisch UTF8 locale Product: Wine Version: 7.22 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: vbscript Assignee: wine-bugs(a)winehq.org Reporter: sloper42(a)yahoo.com Distribution: --- After #52872 was fixed, we get now test failures. === w10pro64_en_AE_u8 (64 bit report) === vbscript: run.c:1206: Test failed: api.vbs: L"Err.number = 0" run.c:1206: Test failed: api.vbs: L"Err.description = " run.c:1206: Test failed: api.vbs: L"Err.number = 0" This happens because chr(-1) now succeeds in utf8 locale. We need to fix the tests. -- 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 54018] New: kernel32:fiber has many failures on Windows 11
by WineHQ Bugzilla Nov. 30, 2022

Nov. 30, 2022

https://bugs.winehq.org/show_bug.cgi?id=54018 Bug ID: 54018 Summary: kernel32:fiber has many failures on Windows 11 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com kernel32:fiber has many failures on Windows 11 21H2: fiber.c:338: Test failed: Got nonzero FlsListHead. fiber.c:339: Test failed: Got unexpected FlsHighIndex 1701. fiber.c:359: Test failed: Got unexpected size 000000C4. fiber.c:377: Test failed: Got unexpected unknown FFFFFFFF, i 0, j 5. fiber.c:380: Test failed: Got unexpected callback 00000000, i 0, j 5. [...] fiber.c:359: Test failed: Got unexpected size 00000304. [...many many more failures on lines 359, 377 and 380...] fiber.c:395: Test failed: Got unexpected status 0. fiber.c:400: Test failed: Got unexpected status 0xc000000d. fiber.c:401: Test failed: Got unexpected callback call count 0. fiber.c:406: Test failed: Got unexpected callback 00457190. fiber.c:425: Test failed: Got unexpected status 0xc00000a0. fiber.c:453: Test failed: Got unexpected size 0000002C. [...many more failures on line 453...] See https://test.winehq.org/data/patterns.html#kernel32:fiber -- 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 54017] New: dwmapi:dwmapi - test_DwmGetCompositionTimingInfo() fails on AMD GPUs
by WineHQ Bugzilla Nov. 30, 2022

Nov. 30, 2022

https://bugs.winehq.org/show_bug.cgi?id=54017 Bug ID: 54017 Summary: dwmapi:dwmapi - test_DwmGetCompositionTimingInfo() fails on AMD GPUs Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: dwmapi Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com dwmapi:dwmapi - test_DwmGetCompositionTimingInfo() fails on (PCI passthrough) AMD and NVIDIA VMs: * the TestBot's Windows 11 NVIDIA RTX3050 VM * the TestBot's Windows 11 AMD RX6600 VM * my Windows 10 22H2 AMD RX550 VM RTX3050 + HDMI/DisplayPort dongle: dwmapi.c:81: Test failed: Got wrong monitor refresh period 28b07. RX6600 + HDMI/DisplayPort dongle: dwmapi.c:81: Test failed: Got wrong monitor refresh period 28b20. RX550 + HDMI screen: dwmapi.c:81: Test failed: Got wrong monitor refresh period 28bb1. See https://test.winehq.org/data/patterns.html#dwmapi:dwmapi Note that this test succeeds on both of the TestBot's plain QEmu w11pro64 test configuration (virtual QXL GPU). This test has two other failures that also impact QXL (see bug 54016). -- 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 53265] New: mmdevapi:capture - test_capture() has timing-related failures on Windows
by WineHQ Bugzilla Nov. 29, 2022

Nov. 29, 2022

https://bugs.winehq.org/show_bug.cgi?id=53265 Bug ID: 53265 Summary: mmdevapi:capture - test_capture() has timing-related failures on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: mmdevapi Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com mmdevapi:capture - test_capture() has timing-related failures on Windows: capture.c:282: Test failed: Position 1719 last 896 frames 448 https://test.winehq.org/data/patterns.html#mmdevapi:capture The failures happen randomly but frequently on Windows 8 to Windows 10 1809. However, because the message includes a duration, it is prone to cause false positives (see also bug 53126 for a similar failure in mmdevapi:render). Furthermore mmdevapi:capture has other systematic failures on Windows 10 1909+ that probably just mask this one (see bug 53264). So one should assume that this timing-related failure impacts all Windows 10 versions. -- 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 53433] New: mmdevapi:capture - test_capture() sometimes fails after resuming capture
by WineHQ Bugzilla Nov. 29, 2022

Nov. 29, 2022

https://bugs.winehq.org/show_bug.cgi?id=53433 Bug ID: 53433 Summary: mmdevapi:capture - test_capture() sometimes fails after resuming capture Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: mmdevapi Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com mmdevapi:capture - test_capture() sometimes fails after resuming capture: capture.c:301: Cont'ed position 2103 pad 21548 flags 0, amount of frames locked: 448 capture.c:325: Restart position 2615 pad 21100 flags 1, amount of frames locked: 448 capture.c:330: Test failed: Position 2615 expected 2551 capture.c:331: Test failed: flags 1 https://test.winehq.org/data/patterns.html#mmdevapi:capture As of today there are 3 known instances of these failures (2022-06-28, 2022-07-11, 2022-07-28) and all 3 happened on Windows 8. Also are independent from the failures in bug 53265. -- 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 53281] New: d3d9:d3d9ex - test_wndproc() sometimes gets an unexpected WM_WINDOWPOSCHANGED on Windows 8+
by WineHQ Bugzilla Nov. 29, 2022

Nov. 29, 2022

https://bugs.winehq.org/show_bug.cgi?id=53281 Bug ID: 53281 Summary: d3d9:d3d9ex - test_wndproc() sometimes gets an unexpected WM_WINDOWPOSCHANGED on Windows 8+ 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 d3d9:d3d9ex - test_wndproc() sometimes gets an unexpected WM_WINDOWPOSCHANGED on Windows 8+: d3d9ex.c:3117: Test failed: Received WM_WINDOWPOSCHANGED but did not expect it, i=0. (also happens with i=1) https://test.winehq.org/data/patterns.html#ddraw:ddraw1 Note that a similar failure seems to happen with KDE in Wine but there is more than one WM_WINDOWPOSCHANGED message so it may be different (see fg-deb64). -- 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 53979] New: d3d9:d3d9ex - test_wndproc() is sometimes missing a WM_WINDOWPOSCHANGING message in Wine
by WineHQ Bugzilla Nov. 29, 2022

Nov. 29, 2022

https://bugs.winehq.org/show_bug.cgi?id=53979 Bug ID: 53979 Summary: d3d9:d3d9ex - test_wndproc() is sometimes missing a WM_WINDOWPOSCHANGING message 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: --- d3d9:d3d9ex - test_wndproc() is sometimes missing a WM_WINDOWPOSCHANGING message in Wine: d3d9ex.c:3115: Test failed: Expected message 0x46 for window 0x1, but didn't receive it, i=1. See https://test.winehq.org/data/patterns.html#d3d9:d3d9ex This seems to be mostly happening on my desktop (Intel + KDE), but it also happened on the debian11 VM in MR!1538 (unrelated heap refactoring). So it's not specific to KDE and can indeed happen on the TestBot 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 2