graphic: 0.810
vnc: 0.727
user-level: 0.709
device: 0.662
semantic: 0.615
arm: 0.609
network: 0.578
permissions: 0.564
performance: 0.554
socket: 0.521
virtual: 0.505
PID: 0.479
register: 0.446
ppc: 0.435
debug: 0.412
mistranslation: 0.389
hypervisor: 0.386
peripherals: 0.372
kernel: 0.337
risc-v: 0.317
architecture: 0.309
files: 0.305
assembly: 0.301
VMM: 0.297
boot: 0.294
KVM: 0.268
TCG: 0.224
i386: 0.215
x86: 0.195

Sending certain keysyms results in wrong symbol input

I develop bVNC, an Android VNC client. I noticed that when I connect to qemu VMs that have a VNC console, Keysyms that are usually sent over with SHIFT modifier when connecting from a PC have wrong symbols typed within the VM. A very short list of examples: 

exclam                              33     0x0021

results in "1" typed in the VM.

at                                  64     0x0040

results in "2"

plus                                43     0x002b

results in "="

asterisk                            42     0x002a

results in "8"

On Android, KEYCODEs that correspond to the above keysyms do not come with SHIFT metastate. Therefore, the keysyms that they correspond to are not sent over with any modifiers and must just work.

The issue was reproduced with bVNC and RealVNC viewers connecting to many versions of qemu (Ubuntu 14.04, oVirt 3.4, oVirt 4.1, etc.). The qemu version that comes with oVirt 4.1 is 2.6.0, commit hash bfc766d38e1fae5767d43845c15c79ac8fa6d6af.

Sincerely,
iordan

There have been quite a bunch of improvements in the keysyms handling during the past years ... can you still reproduce your issue with the latest version of QEMU?

Seems to work fine now. Thank you!!

iordan

Thanks for testing! So I'm closing the ticket now.