... this doesn't seem to be a VNC-only issue.. I get quite the big of repeat/stuck key presses with the GTK frontend as well.. Also, lines like these frequently show up in the logs:
> [15512.846716] psmouse serio1: VMMouse at isa0060/serio1/input0 lost sync at > byte 1 > [15513.031586] psmouse serio1: VMMouse at isa0060/serio1/input0 - driver > resynced. > [15513.931140] psmouse serio1: VMMouse at isa0060/serio1/input0 lost sync at > byte 1 > [15513.935319] psmouse serio1: VMMouse at isa0060/serio1/input0 - driver > resynced. > [15994.802058] psmouse serio1: VMMouse at isa0060/serio1/input0 lost sync at > byte 1 > [15994.807817] psmouse serio1: VMMouse at isa0060/serio1/input0 - driver > resynced. > [18243.163746] psmouse serio1: VMMouse at isa0060/serio1/input0 lost sync at > byte 1 > [18243.165704] psmouse serio1: VMMouse at isa0060/serio1/input0 - driver > resynced. > [18243.372671] psmouse serio1: VMMouse at isa0060/serio1/input0 lost sync at > byte 1 > [18243.374203] psmouse serio1: VMMouse at isa0060/serio1/input0 - driver > resynced. > [18576.754033] psmouse serio1: VMMouse at isa0060/serio1/input0 lost sync at > byte 1 > [18576.771257] psmouse serio1: VMMouse at isa0060/serio1/input0 - driver > resynced. > [18584.556247] psmouse serio1: VMMouse at isa0060/serio1/input0 lost sync at > byte 1 > [18585.168172] psmouse serio1: VMMouse at isa0060/serio1/input0 - driver > resynced. > [18628.989958] psmouse serio1: VMMouse at isa0060/serio1/input0 lost sync at > byte 1 > [18628.992058] psmouse serio1: VMMouse at isa0060/serio1/input0 - driver > resynced. > [20227.153135] psmouse serio1: VMMouse at isa0060/serio1/input0 lost sync at > byte 1 > [20227.161066] psmouse serio1: VMMouse at isa0060/serio1/input0 - driver > resynced. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1502884 Title: Super important feature req: QEMU VNC server: Introduce a keyboard "norepeat" option! Status in QEMU: New Bug description: Hi, A big issue when using QEMU's VNC server (VNC KVM) is that, when there's a network lag, unintended keypresses go through to the QEMU guest VM. This is frequently "enter" keypresses, causing all kinds of unintended consequences in the VM. So basically it's extremely dangerous. This is because the VNC protocol's keyboard interaction is implemented in terms of key down - key up events, making the server's keyboard autorepeat kick in when it should not. For this reason, it would be great if QEMU's VNC server part would be enhanced with an option such that when a VNC protocol key down is received, then locally that is treated as one single keypress only (I don't know how that should be implemented but I guess either as an immediate key down - key up sequence locally, or key down + key up after say 0.05 seconds), instead of waiting for the key up event from the VNC client. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1502884/+subscriptions
