Mouse movement duplicated on second monitor

[github-k8n]

With my current settings (see below) it seems that sometimes my mouse movement on the right monitor (Linux, Output A) is duplicated on the left one (Windows, 2 monitors, one builtin and one connected, the connected monitor is exactly the same as the one from the Linux system.
Only mouse movement is duplicated not any clicks or keyboard entries. I can fix it by moving the mouse all way to the left (over the connected monitor of the Windows system and on to the builtin monitor) and then back again to the Linux system then everything is ok again for a while.
I have a suspicion that it could be related to either the Cursor park position or the Screensaver mode.

[hrvach]

Thank you for a good problem description! If you reconfigure the cursor park position to something else, does that seem to change the behaviour?

[github-k8n]

Cursor park position does not affect it (set to Top), it still mirrors the movement. However when I set the Screensaver mode from Jitter to Pong, it does no longer cause the same "mirrored mouse" behavior (obviously the mouse will now move in the "pong" zigzag movement on the left (B, Windows) screen which is expected.

=====

I also noticed another behavior, maybe I should open another case for that (let me know and I'll copy/paste it) but wanted to mention it here as well.
(Again, the physical screen layout from left to right: (B: Builtin Windows, B: External Windows, A: External Linux)

When moving the mouse cursor to the left until it reaches the Builtin Windows screen, it seems the acceleration is suddenly no longer working. Cursor becomes slow (non-accelerated) even when back on the External Windows screen. It only goes back to normal once it reaches the A: External Linux screen. As long as I keep the mouse on the External screens (B: External Windows, A: External Linux) the mouse acceleration will work fine. (maybe some issue with the dual screen stuff on Windows)?

[github-k8n]

Oh and just because I didn't mention it earlier: it seems to start (the mirrored mouse movement) reproducibly after the screensaver timeout (when using "Jitter").

[hrvach]

I am struggling to reproduce this, but I'm convinced you get sort of a "split brain" scenario. Next release should have a fix for that, but I'm still unsure of the scenario how it might happen.