I found something interesting using showkey in the VM. This is all assuming en-US everywhere, note. On a US keyboard, "<" is a shifted comma (shift-,), ">" is a shifted period (shift-.), and "|" is a shifted backslash (shift-\).
If I run showkey and try the affected characters in virt-manager, the results are kinda what I'd expect. It reports keycode 42 for the shift key, keycode 51 for comma key, keycode 52 for period key, and keycode 43 for backslash key. If I do shift-, (to get a <), it shows keycode 42 down, keycode 51 down, keycode 51 up, keycode 42 up - just what you'd expect. Ditto for > and |: it shows 42d/52d/52u/42u and 42d/43d/43u/42u in those cases. But if I do this while typing in tigervnc, it reports something quite different. Just pressing the keys alone gives the right codes - 51, 52, 43. But when I try the shifted combinations, it reports keycode *86* for all three keys. That is, so long as shift is held down, pressing the comma, period or backslash key reports keycode 86 - not 51, 52 or 43. Somehow this results in the generation of a > character, not sure how. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1738283 Title: 'Less than' (<), 'more than' (>), and 'pipe' (|) can't be typed via VNC Status in QEMU: New Bug description: If I start QEMU 2.11 (from https://build.opensuse.org/package/show/Virtualization/qemu) VM with VNC, I am unable to type following three characters: 'less than' (<), 'more than' (>), and 'pipe' (|) on en_US QWERTY keyboard. Other characters work fine. QEMu version 2.10.1 worked fine. /usr/bin/qemu-kvm -m 2048 -cpu kvm64 -drive media=cdrom,if=none,id=cd0,format=raw,file=OI-hipster- minimal-20171031.iso -device ide-cd,drive=cd0 -boot once=d,menu=on ,splash-time=5000 -device usb-ehci -device usb-tablet -smp 1 -enable- kvm -vnc :91,share=force-shared The ISO can be downloaded here: https://www.openindiana.org/download/ Also tried Fedora-Server-dvd-x86_64-25-1.3.iso and it's the same situation. If I run the same command without '-vnc :91,share=force-shared', everything works just fine. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1738283/+subscriptions
