Hello all,
I've been fighting a VNC bug for a long time now with no answer in sight. When connecting to a VM through either the built in noVNC, an external noVNC client, or guacamole, some keys get "stuck".
Using shift to type lower and upper case characters works as expected, as do the numbers, but some keys like , < . > seem to get "stuck" until I press the key again. The observed behaviour is the key being repeatedly typed into the VM until I press the key again to stop the input. This results in long strings like <,,,,,,,,,,,,,,,,,,, when typing Shift+, to get the < character. I cannot find any setting that has stopped this behaviour.
The closest workaround has been to disable keyboard repeat in the accessibility options of the VM OS.
Any ideas what I can look at next to try and fix this?
I've been fighting a VNC bug for a long time now with no answer in sight. When connecting to a VM through either the built in noVNC, an external noVNC client, or guacamole, some keys get "stuck".
Using shift to type lower and upper case characters works as expected, as do the numbers, but some keys like , < . > seem to get "stuck" until I press the key again. The observed behaviour is the key being repeatedly typed into the VM until I press the key again to stop the input. This results in long strings like <,,,,,,,,,,,,,,,,,,, when typing Shift+, to get the < character. I cannot find any setting that has stopped this behaviour.
The closest workaround has been to disable keyboard repeat in the accessibility options of the VM OS.
Any ideas what I can look at next to try and fix this?
