Comment 83 for bug 296167

I _think_ the cause is a race condition in WindowsRestructured() which calls
CheckMotion(). CheckMotion in turn sets the wrong screen, if the mouse already
moved into a position on the other screen. Not sure yet though, but that's a
path to look at if you have time.