Bug 705643

Description of problem:
Fight over mouse, between X-servers and VNC, might lead to instability.
Sometimes an X crashes.

Version-Release number of selected component (if applicable):


How reproducible:
easy, everytime

Steps to Reproduce:
1. On Host1, login in to main x-server, open a application or something like a gnome-terminal for easy identification, make sure vino is enabled
2. On Host1, Ctrl-Alt-2 to a conosle, login
3. On Host1, startx -- :1 
A second X server starts on '7', start some application, play around
4. from a remote computer VNC to :1
5. move mouse on remote cursor, everything works fine
play around with mouse, observe that things in sync between VNC client and X-server-2
6. On Host1, With VNC active, Ctrl-Alt-1 to the other first X-server
note that 
7. On Host1, the cursor on the first X server will be stuck

Things may fall apart in various ways here.

Actual results:
instability

Expected results:
stability

Speculations:
There is a local mouse on Host1. There are two X-servers and 1 VNC client

When the remote VNC client connects X-server-2, and the active console on Host-1 is X-server-2, the remote mouse and the local mouse control the mouse pointer. 
When Ctrl-Alt-1 is pressed on Host 1, local mouse must be detached from X-server-2 and attached to X-server-1

Either the vino backend is grabbing the mouse pointers of both X-servers
or the local mouse is not properly attached detached from the X servers.

Additional info:

An additional test case would be two remote VNC clients connecting to both X-servers, and locally switching between the two consoles on Host-1.