[Bug 55072] New: msctf:inputprocessor sometimes gets unexpected activation callbacks on Windows 10

[WineHQ Bugzilla]

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

Bug ID: 55072
           Summary: msctf:inputprocessor sometimes gets unexpected
                    activation callbacks on Windows 10
           Product: Wine
           Version: unspecified
          Hardware: x86-64
                OS: Windows
            Status: NEW
          Severity: normal
          Priority: P2
         Component: msctf
          Assignee: [e-mail]
          Reporter: [e-mail]

msctf:inputprocessor sometimes gets unexpected activation callbacks:

inputprocessor.c:1012: TextService_Activate
inputprocessor.c:750: Got OnActivated: {dwProfileType 00000001, langid
00000409, clsid {ede1a7ad-66de-47e0-b620-3e92f8246bf3}, catid
{34745c63-b2f0-4784-8b67-5e12c8701a31}, guidProfile
{ede1a7ad-66de-47e0-b620-3e92f8246bf3}, 00000000, dwFlags 00000003}
inputprocessor.c:840: Got OnActivated: {clsid
{ede1a7ad-66de-47e0-b620-3e92f8246bf3}, guidProfile
{ede1a7ad-66de-47e0-b620-3e92f8246bf3}, activated 1}
inputprocessor.c:2288: found {544D6A63-E2E8-4752-BBD1-000960BCA083}
inputprocessor.c:2288: found {EDE1A7AD-66DE-47E0-B620-3E92F8246BF3}
inputprocessor.c:2288: found {575F3783-70C8-47C8-AE5D-91A01A1F7592}
inputprocessor.c:1020: TextService_Deactivate
inputprocessor.c:750: Got OnActivated: {dwProfileType 00000001, langid
00000409, clsid {ede1a7ad-66de-47e0-b620-3e92f8246bf3}, catid
{34745c63-b2f0-4784-8b67-5e12c8701a31}, guidProfile
{ede1a7ad-66de-47e0-b620-3e92f8246bf3}, 00000000, dwFlags 00000003}
inputprocessor.c:759: Test failed: OnActivated: Activation came unexpectedly
inputprocessor.c:840: Got OnActivated: {clsid
{ede1a7ad-66de-47e0-b620-3e92f8246bf3}, guidProfile
{ede1a7ad-66de-47e0-b620-3e92f8246bf3}, activated 0}
inputprocessor.c:1249: Disabling

See https://test.winehq.org/data/patterns.html#msctf:inputprocessor

This is similar to one of the failure that is happening systematically on the
GitLab Windows VM (bug 55068). The difference are:
* This failure started on 2023-05-30 whereas on gitlab-win10-21h2 it has been
there from the start.
* This failure happens roughly every couple of days whereas on
gitlab-win10-21h2 it is systematic.
* This failure is alone whereas gitlab-win10-21h2 has 14 other failures, 3 of
which are related to activation.
* So far this has only happened on w1064v1507 and w10pro64v2004, both in 32-
and 64-bit tests.