Comment 235 for bug 296167

Peter and I worked on this problem some more.

My configuration is proprietary nvidia driver, two GEForce cards
and three screens (screen0=card0,0. screen1=card0,1. screen2=card1,0.)
All screens are running at 1280x1024 resolution, and I've got xinarama.

I can recreate the problem easily by dragging my mouse from screen1 to
screen2, which spans between the two nvidia cards. During a gdb
debugging session, during which every slowed down, my mouse cursor
intermittently jumped from its current location (call it x,y) on screen1
to the same (x,y) on screen2, and back.

I tried to recreate the problem between screen0 and screen1 (staying
within the same video card) and was unable. However, this morning the
problem recreated "by accident" between screen0 and screen1, and my
mouse cursor was no where near screen2. So the problem is easily
recreated when switching between card screens and difficult (but still
possible) to recreate when switching between screens on the same card.

Yesterday, I was able to recreate the problem, even with auto-raise
turned off. I just had to move the cursor from screen to screen and
click on windows instead of having auto-raise bring them to the top.

Peter seemed to think this is a scaling issue.

Again, once the mouse stops responding, the problem can be corrected
by using <alt-tab> to select a window, then <alt-f7> to move the window
to screen0 (and only screen0). Once the mouse cursor is moved back to
screen0 via the keyboard arrow keys, the mouse starts working again.

Edward: This does seem like a different issue from the original problem
so maybe you should create a clone bug record.