XVNC Switching Layouts

[MisterFuntikov]

The keyboard layout does not switch in XVNC.

I use two layouts us and ru. Added the ability to switch layouts using this wiki. All other settings are by default. The second layout appeared on the panel. But when switching to the ru language, characters from the layout that was connected to the xrdp server (us), are still printed.

I exported the us and ru layouts:
xkbcomp $DISPLAY keyboard.xkb
— both files are correct.
us.xkb.txt
ru.xkb.txt

I looked at the output of the currently pressed keys via the xev command in the terminal.

On the us layout:
KeyRelease event, serial 37, synthetic NO, window 0x4eO0001, root 0x2a5, subw 0x4e000O2, time 5691621, (52,29), root:(793,470), state 0x10, keycode 24 (keysym 0x71, q), same_screen YES, XLookupString gives 1 bytes: (71) "q" XFilterEvent returns: False

On the ru layout:
KeyRelease event, serial 43, synthetic NO, window 0x5200001, root 0x2a5, subw 0x5200002, time 4608536, (38,26), root: (811,461), state 0x2010, keycode 253 (keysym 0x71, q), same_screen YES, XKeysymToKeycode returns keycode: 24 XLookupString gives 1 bytes: (71) "q" XFilterEvent returns: False

In xev, everything is correct on the us layout. The ru layout shows that the keycode number 253 is defined, which corresponds to a void in xkb. And with further pressing of different keys, empty xkb_symbols will be filled in us letters. But at the same time, a line appears in xev XKeysymToKeycode, which shows really the keycodes that was pressed. And according to ru.xkb, this code should have been equal to keysym <AD01> Cyrillic_shorti.

Is it possible to implement two layouts in xvnc xrdp?

Cinnamon session
xrdp-0.9.21-1.el7
sesman.ini.txt
startwm.sh.txt

[matt335672]

It may not be at the moment.

The VNC server receives a symbol from us rather than a key code, which is what you need.

More information from the TigerVNC server side can be found here:-

TigerVNC/tigervnc#962

The link mentions a TigerVNC option called -RawKeyboard which could solve this, but we don't support it. The protocol reference for that is here:-

https://github.com/rfbproto/rfbproto/blob/master/rfbproto.rst#qemu-extended-key-event-message