[Bug 54853] New: Locking the KDE screen causes user32:input to fail systematically
https://bugs.winehq.org/show_bug.cgi?id=54853 Bug ID: 54853 Summary: Locking the KDE screen causes user32:input to fail systematically 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: --- Locking the KDE screen causes user32:input to fail systematically. Specifically it gets failures in test_rawinput(): input.c:2918: Test marked flaky: 4: unexpected WM_MOUSEMOVE message input.c:2929: Test failed: 4: Unexpected cursor movement input.c:2929: Test failed: 5: Unexpected cursor movement input.c:2929: Test failed: 6: Unexpected cursor movement input.c:2502: Test marked todo: Expected wparam 1, got 0 input.c:2929: Test failed: 7: Unexpected cursor movement input.c:2929: Test failed: 8: Unexpected cursor movement input.c:2918: Test marked flaky: 9: unexpected WM_MOUSEMOVE message input.c:2645: Test marked flaky: 9: foreground process expected WM_MOUSEMOVE message input.c:2929: Test failed: 9: Unexpected cursor movement input.c:2502: Test marked todo: Expected wparam 1, got 0 input.c:2645: Test marked flaky: 10: foreground process expected WM_MOUSEMOVE message input.c:2929: Test failed: 10: Unexpected cursor movement input.c:2502: Test marked todo: Expected wparam 1, got 0 input.c:2645: Test marked flaky: 11: foreground process expected WM_MOUSEMOVE message input.c:2929: Test failed: 11: Unexpected cursor movement input.c:2645: Test marked flaky: 12: foreground process expected WM_MOUSEMOVE message input.c:2929: Test failed: 12: Unexpected cursor movement input.c:2921: Test marked todo: 13: expected WM_INPUT message input.c:2929: Test failed: 13: Unexpected cursor movement input.c:2929: Test failed: 14: Unexpected cursor movement input.c:2929: Test failed: 15: Unexpected cursor movement input.c:2929: Test failed: 16: Unexpected cursor movement and in test_GetMouseMovePointsEx_process(): input.c:1730: Test failed: expected to get 64 mouse move points but got -1 input.c:1741: Test failed: expected to get 64 mouse move points but got -1 input.c:1787: Test marked todo: expected to get -1 mouse move points but got 64 input.c:1788: Test marked todo: expected ERROR_ACCESS_DENIED got -559038737 See https://test.winehq.org/data/patterns.html#user32:input Only my development desktop runs the Wine tests in KDE and I normally avoid locking the screen when doing so. But it is quite remarkable that only three tests units have an issue with this configuration: this one, comctl32:tooltips and user32:win. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=54853 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |source, testcase -- 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.
https://bugs.winehq.org/show_bug.cgi?id=54853 --- Comment #1 from François Gouget <fgouget(a)codeweavers.com> --- Locking the KDE screen also causes failures in two other test units: comctl32:tooltips (bug 54852) and user32:win (bug 54854). -- 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.
https://bugs.winehq.org/show_bug.cgi?id=54853 Neko-san <nekoNexus(a)protonmail.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nekoNexus(a)protonmail.ch -- 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.
participants (1)
-
WineHQ Bugzilla