https://bugs.winehq.org/show_bug.cgi?id=47945
Bug ID: 47945 Summary: dinput:mouse regression on Wine Product: Wine Version: 4.17 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-dinput Assignee: wine-bugs@winehq.org Reporter: fgouget@codeweavers.com Distribution: ---
dinput:mouse has regressed on the debian10 TestBot VM. It used to have a single failure:
mouse.c:178: Test failed: GetDeviceData() failed: 00000000 cnt:0
And now it has four new failures:
mouse.c:152: Test failed: Failed: 00000001 mouse.c:158: Test failed: Failed: 80070005 mouse.c:161: Test failed: Failed: 00000001 mouse.c:164: Test failed: Failed: 80070005
The four new failures have been introduced by the following commit:
commit 0555209757e842818c16c6868e73bf076daa349b Author: Alistair Leslie-Hughes leslie_alistair@hotmail.com Date: Mon Oct 7 22:56:06 2019 +0000
dinput/tests: Add checks for Acquire/Unacquire.
Signed-off-by: Alistair Leslie-Hughes leslie_alistair@hotmail.com Signed-off-by: Alexandre Julliard julliard@winehq.org
Interestingly all these failures (the old one and four new ones) happen on the exact same set of VMs, the debian10 TestBot VMs: the test succeeds on cw-rx460 and cw-gtx560 for instance.
One thing that's different in the TestBot VMs is that they have two pointer devices: * a PS/2 mouse * a tablet that provides absolute position information
Maybe that's the reason for the difference?
Note that some Windows VMs (not all) also have this tablet device (e.g. w7pro64, w864 and wxppro) and we don't get failures on any of the TestBot Windows VMs.