Keyboard mapping

[earthcare]

Hi all

I’m connecting to a Windows 10 PC from a Linux-Mint 19 PC. After the last NoMachine upgrade, the keyboard (a US-Intl kb) is mapped wrongly. The Windows PC is mapped to a US-Intl kb as well.

Running xkbcomp … in a command line for the physical and virtual keyboards on the Linux box shows identical results:
me@DEEP-THOUGHT:~$ xkbcomp -i 5 -xkb $DISPLAY – | grep “xkb_keycodes\|xkb_types\|xkb_compatibility\|xkb_symbols\|xkb_geometry”
xkb_keycodes “evdev+aliases(qwerty)” {
xkb_types “complete” {
xkb_compatibility “complete” {
xkb_symbols “pc+us+inet(evdev)” {
xkb_geometry “pc(pc105)” {
me@DEEP-THOUGHT:~$ xkbcomp -i 8 -xkb $DISPLAY – | grep “xkb_keycodes\|xkb_types\|xkb_compatibility\|xkb_symbols\|xkb_geometry”
xkb_keycodes “evdev+aliases(qwerty)” {
xkb_types “complete” {
xkb_compatibility “complete” {
xkb_symbols “pc+us+inet(evdev)” {
xkb_geometry “pc(pc105)” {

Can anyone shed a light on this?

Thanks

[graywolf]

Are you using Linux to connect to Windows?

Would you describe how the keyboard is mapped wrong?

In any case, NoMachine does not change the keyboard layout of the server when sharing the desktop.

[earthcare]

Well, that’s weird!

To respond to your questions, yes, Linux to Windows. The numeric keypad, arrow keys and Insert/Delete/Home/End/Page Up/Page Down keys all seemed to be assigned to different functions.

But when I came back to it 2 days later – the Windows box gets shut down when not in use, and the Linux box gets shutdown every evening – it was all normal. I hate it when a problem just goes away.

[graywolf]

OK. Should it happen again, please take note of the expected symbol/behavior and the actual wrong symbol/behavior for the affected keys.

[Author]

Posts