Keyboard Problems, Mac client, Linux Host

[ThomasZ]

Hello,

I’m connecting from my Mac OS Sierra (10.12.6) Client to a Fedora 26 Linux host. Connection is fast, but the keyboard mapping is weird. A German Mac keyboard is connected to the Mac, a German standard keyboard is connected to the Linux box.

But NoMachine (5.3.12) seems to think that an English keyboard is connected to the Mac. I do not have the German Umlauts at the right place and so on.

Any Hints?

Thanks,

Thomas

[graywolf]

Please, in the remote session open a terminal window and check the output of command setxkbmap -print.

Search file /usr/NX/var/log/node/C-.../session for errors referring to xkb or xkbcomp.

[ThomasZ]

The output of the command setxkbmap -print on the linux host is:

xkb_keymap {
xkb_keycodes { include “evdev+aliases(qwertz)” };
xkb_types { include “complete” };
xkb_compat { include “complete” };
xkb_symbols { include “pc+de(nodeadkeys)+inet(evdev)” };
xkb_geometry { include “pc(pc105)” };
};

Meanwhile, I’ve connected from a Windows Client to the Linux host and got the same result, incorrect German keyboard mapping. So I guess it must be a problem on the host.

[ThomasZ]

I forgot: in the session logs are no errors.

[graywolf]

Please, give a try to the “xev” test tool. Then gather logs and send to forum (at) nomachine (dot) com : https://www.nomachine.com/DT07M00098

[debaba]

Hi,

had the same problems. Newer versions of nxclient don’t seem to be looking for the used keyboard on remote side. These versions inspite use English.

If you have a working connection, go to your keyboard settings, set it once to the keyboard-model and language you wish.

Test the settings by opening an terminal in the connected machine and execute ‘setxkbmap -print’. Should produce something like the following (for German keyboard with German, Greek and Turkish language)

schindler@phenom:~$ setxkbmap -print
xkb_keymap {
xkb_keycodes  { include “evdev+aliases(qwertz)” };
xkb_types     { include “complete”      };
xkb_compat    { include “complete”      };
xkb_symbols   { include “pc+de(nodeadkeys)+gr:2+tr:3+inet(evdev)+terminate(ctrl_alt_bksp)”      };
xkb_geometry  { include “pc(pc104)”     };
};

Good luck

[graywolf]

debaba, the client doesn’t force a keyboard layout in the server and it is expected. Did you find that behavior changed at some point? Do you know in which version of NoMachine it happened, more or less?

[Author]

Posts