On 8/17/2018 11:51 AM, Daniel P. Berrangé wrote: > Since you're using tightvnc on Windows, it won't be using the raw scancode > extension to RFB, so it'll be sending X keysyms across the wire eg > > "|" has X11 keysym 0x7c (XK_bar) > "\" has X11 keysym 0x5c (XK_backslash) > > First thing is the converting keysym number to a name, which > uses name2keysym[] data table. This gives 'bar' and 'backslash' > as names, respectively > > The names are now looked up in the keymap (pc-bios/keymaps/en-us) > which says > > backslash 0x2b > bar 0x2b shift
Thanks. I checked out the 2.11 version that Ubuntu 18.04 shipped and
found the problem:
commit a7815faffb2bd594b92aa3542d7b799cc89c5414
Author: Gerd Hoffmann <kra...@redhat.com>
Date: Thu Oct 5 17:33:30 2017 +0200
pc-bios/keymaps: keymaps update
Update the keymaps with the ones generated by qemu-keymap
Signed-off-by: Gerd Hoffmann <kra...@redhat.com>
Message-id: 20171005153330.19210-4-kra...@redhat.com
Prior to this commit, this file said it was generated from XKB, and was
much smaller, not including the scan code for that other key. This
commit added the 0x56 bar translation with altgr, and it wasn't until
after 2.12 those smarts were inserted to pick the scancode that matches
the current modifier keys.
signature.asc
Description: OpenPGP digital signature
