[Bug 53516] New: user32:input failed due to unexpected WM_TIMECHANGE message

[WineHQ Bugzilla]

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

Bug ID: 53516
           Summary: user32:input failed due to unexpected WM_TIMECHANGE
                    message
           Product: Wine
           Version: unspecified
          Hardware: x86-64
                OS: Windows
            Status: NEW
          Severity: normal
          Priority: P2
         Component: user32
          Assignee: [e-mail]
          Reporter: [e-mail]

user32:input failed due to unexpected WM_TIMECHANGE message:

input.c:4525: Test failed: SendInput triggered unexpected message 0x1e

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

This happened on 2022-08-05 in the w10pro64-fr-64 test configuration.
But user32:msg has also received such an unexpected message on 2022-08-02 on
w10pro64-pt-BR-64 (see bug 53273).

It appears this message is sent by Windows when an application modifies the
system time. If the application is another test then it should make sure all
such messages have been sent before continuing.

But it is quite possible that this message is sent when Windows resynchronizes
with some internet time server in which case this message could arrive in any
test at any time.

[Bug 53516] user32:input failed due to unexpected WM_TIMECHANGE message

[WineHQ Bugzilla]

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

François Gouget  changed:

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

[Bug 53516] user32:input failed due to unexpected WM_TIMECHANGE message

[WineHQ Bugzilla]

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

--- Comment #1 from François Gouget  ---
A test shows that the Windows time service (w32time) is not disabled on the
TestBot VMs. It's actually set to "Manual" on Windows 7 to Windows 10 2004, and
"Automatic (Delayed Start, Trigger Start)" on Windows 10 2009 and greater.

The TestBot already sets the time before running a task but that may not be
accurate to the millisecond (depends on the time synchronization of the TestBot
server, network delays, and process startup times). So if the time service ends
up synchronizing the time while a test runs it may cause the time to jump a
little bit forwards or backwards (if the offset is > 128 ms).

So this could be the cause of the unexpected WM_TIMECHANGE messages and may
also mess with timing checks (see bug 53171).

[Bug 53516] user32:input failed due to unexpected WM_TIMECHANGE message

[WineHQ Bugzilla]

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

--- Comment #2 from François Gouget  ---
Note: The Windows time service (w32time) is now disabled in all the TestBot
VMs. See bug 54129.

[Bug 53516] user32:input failed due to unexpected WM_TIMECHANGE message

[WineHQ Bugzilla]

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

Rémi Bernon  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
                 CC|                            |[e-mail]
      Fixed by SHA1|                            |998003bda16a52cd834869f9a0e
                   |                            |987438a130849
             Status|NEW                         |RESOLVED

--- Comment #3 from Rémi Bernon  ---
Should be fixed after 998003bda16a52cd834869f9a0e987438a130849 (which filters
and only check keyboard messages).

[Bug 53516] user32:input failed due to unexpected WM_TIMECHANGE message

[WineHQ Bugzilla]

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

Alexandre Julliard  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #4 from Alexandre Julliard  ---
Closing bugs fixed in 9.1.