https://bugs.winehq.org/show_bug.cgi?id=53910
--- Comment #24 from Rafał Mużyło galtgendo@o2.pl --- So, the race triggered again and the results were...odd.
First of all, a xwininfo/wmctrl dance was needed to make the applet window appear on screen, but that wasn't all that surprising.
What was, was what the applet displayed.
According to it, only one of my monitors was active and it was the DVI one, one with the flaky edid. And it was still labeled as DISPLAY2. The windows were obviously not moved from the monitor they were on - the primary.
Given that one is the smaller one, that 'explains' the odd mouse behavior. But given the one that survives is the one doing fake shutdown (which I believe to be a slower reaction...unless I'm wrong about that) makes me wonder...
I'll need to find the part of the source that handles this...