[Bug 54854] New: Locking the KDE screen causes user32:win to fail systematically

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=54854

Bug ID: 54854
           Summary: Locking the KDE screen causes user32:win to fail
                    systematically
           Product: Wine
           Version: unspecified
          Hardware: x86-64
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: user32
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Locking the KDE screen causes user32:win to fail systematically.

Specifically it gets failures in test_nonclient_area():

win.c:1581: Test failed: Got unexpected color 0xc0c0c0.
win.c:1581: Test failed: Got unexpected color 0xc0c0c0.
win.c:1581: Test failed: Got unexpected color 0xc0c0c0.
win.c:1581: Test failed: Got unexpected color 0xc0c0c0.
win.c:1581: Test failed: Got unexpected color 0xc0c0c0.
win.c:1581: Test failed: Got unexpected color 0xc0c0c0.
win.c:1581: Test failed: Got unexpected color 0xc0c0c0.
win.c:1581: Test failed: Got unexpected color 0xc0c0c0.
win.c:1581: Test failed: Got unexpected color 0xc0c0c0.
win.c:1581: Test failed: Got unexpected color 0xc0c0c0.
win.c:1581: Test failed: Got unexpected color 0xc0c0c0.
win.c:1581: Test failed: Got unexpected color 0xc0c0c0.

in test_activateapp():

win.c:11013: Test failed: Expected foreground window 0, got 00FE0060
win.c:11019: Test failed: Expected foreground window 002D0142, got 00FE0060
win.c:11082: Test marked todo: Expected WM_ACTIVATEAPP(0), did not receive it.

and in test_topmost():

win.c:11683: Test failed: 01ED0126: expected prev 005D00BE, got 00000000
win.c:11697: Test failed: hwnd should NOT be topmost
win.c:11699: Test failed: 01ED0126: expected NOT topmost
win.c:11643: Test failed: 1: hwnd 01ED0126 is still topmost
win.c:11724: Test marked todo: owner should be topmost
win.c:11727: Test marked todo: hwnd2 should be topmost
win.c:11750: Test marked todo: hwnd should NOT be topmost
win.c:11764: Test marked todo: hwnd should NOT be topmost
win.c:11805: Test marked todo: hwnd should be topmost
win.c:11807: Test succeeded inside todo block: child should be topmost
win.c:11809: Test marked todo: child2 should be topmost
win.c:11810: Test failed: grandchild should be topmost
win.c:11818: Test failed: child should NOT be topmost
win.c:11821: Test succeeded inside todo block: grandchild should NOT be topmost
win.c:11824: Test failed: 0007012A: expected NOT topmost
win.c:11643: Test succeeded inside todo block: 5: hwnd 01070060 is still
topmost
[... more todos ...]

See https://test.winehq.org/data/patterns.html#user32:win

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
(bug 54582) and user32:input (bug 54583).

[Bug 54854] Locking the KDE screen causes user32:win to fail systematically

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=54854

François Gouget  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |source, testcase

[Bug 54854] Locking the KDE screen causes user32:win to fail systematically

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=54854

--- Comment #1 from François Gouget  ---
I mistyped the bug numbers. The correct references are: comctl32:tooltips (bug
54852) and user32:input (bug 54853).

[Bug 54854] Locking the KDE screen causes user32:win to fail systematically

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=54854

Neko-san  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]