[Bug 52108] New: user32:monitor breaks user32:win on Win10 1809

[WineHQ Bugzilla]

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

            Bug ID: 52108
           Summary: user32:monitor breaks user32:win on Win10 1809
           Product: Wine
           Version: unspecified
          Hardware: x86-64
                OS: Windows
            Status: NEW
          Severity: normal
          Priority: P2
         Component: user32
          Assignee: wine-bugs at winehq.org
          Reporter: fgouget at codeweavers.com

Created attachment 71132
  --> https://bugs.winehq.org/attachment.cgi?id=71132
Windows 10 1809 "blurry popup"

On 2021-09-01 user32:monitor started breaking user32:win on Windows 10 1809:

win.c:3322: Test failed: GetActiveWindow() = 00220510
win.c:3325: Test failed: GetFocus() = 00000000
win.c:3337: Test failed: GetFocus() = 00000000
win.c:3340: Test failed: GetFocus() = 00000000
win.c:3343: Test failed: GetFocus() = 00000000
win.c:3346: Test failed: GetActiveWindow() = 00220510
win.c:3350: Test failed: GetFocus() = 00000000
win.c:3353: Test failed: GetFocus() = 00000000
win.c:4047: Test failed: hwnd 004A050A/003600CA message 0737
win.c:4052: Test failed: hwnd 003600CA/003600CA message 0202
win.c:4057: Test failed: hwnd 003600CA/003600CA message 0203
win.c:4061: Test failed: message 0202 available

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

A bisect shows that the failures started with this commit:

commit 2d51077a22b7d8faa9587d02a84181f58d1203aa
Author:     Zhiyi Zhang <zzhang at codeweavers.com>
AuthorDate: Wed Sep 1 14:37:21 2021 +0800

    user32/tests: Add DisplayConfigSetDeviceInfo() tests.

    Test that DisplayConfigSetDeviceInfo() can be used for getting and setting
display DPI.

    Signed-off-by: Zhiyi Zhang <zzhang at codeweavers.com>
    Signed-off-by: Alexandre Julliard <julliard at winehq.org>


What happens is that the new display tests cause Windows 10 1809 to display a
notification that the "apps might be blurry". This notification stays up after
user32:monitor completes and then steals the focus from the user32:win tests
and causes them to fail.

So there's not really anything wrong in either user32:monitor nor user32:win
but this still causes test failures :-(

-- 
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.