Reset the key modifiers upon client connect

VNC should not maintain modifer state upon reconnects With some window managers/vnc clients it will only see a key down event for a modifier followed by immediate disconnect(think Alt-F4), with a net effect of subsequently connected clients operating as if the modifier was never released. git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@5851 c046a42c-6fe2-441c-8c8c-71466251a162

Reset the key modifiers upon client connect
VNC should not maintain modifer state upon reconnects With some window managers/vnc clients it will only see a key down event for a modifier followed by immediate disconnect(think Alt-F4), with a net effect of subsequently connected clients operating as if the modifier was never released. git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@5851 c046a42c-6fe2-441c-8c8c-71466251a162
malc
1 parent 429a8ed3
Showing 1 changed file with 1 additions and 0 deletions
vnc.c
@@ -2246,6 +2246,7 @@ static void vnc_connect(VncState *vs)
     vs->has_hextile = 0;
     vs->ds->dpy_copy = NULL;
     vnc_update_client(vs);
+    reset_keys(vs);
 }
  
 static void vnc_listen_read(void *opaque)