Keyboard maps to US when client and server are UK

Forums / NoMachine for Linux / Keyboard maps to US when client and server are UK

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #2825
    AvatarzSeries
    Participant

    Hi,

    I was a user of NX 3.5 on Ubuntu 10.04 for many months, perhaps years with no problems what so ever. Recently I have upgraded to Lubuntu 12.04 LTS on my desktop server and Lubuntu 12.10 on my dell laptop client. I am running the latest NX 4.1.29 on both although I have tried several previous 4.1 releases. My problem is that both machines are UK machines, UK keyboards and I have never had a problem with keyboard mapping on any application including NX 3.5. Now in 4.1 NX it thinks I am using a US keyboard on the client. When I type @”@ sign I get “. You see I am using right now for this posting and that was supposed to be double quote, the at sign follow by another double quote. Similarly when I type multiple UK pounds signs I get ########. Where is the keyboard definition for NX? Is must be getting it from the wrong place.

    #2886
    Avatargraywolf
    Moderator

    Hello zSeries.

    can you send the client and server log files? You can gather logs in this way:

    Create a compressed archive of the NoMachine /var/log directory

    The NoMachine /var/log directory on Linux is: /usr/NX/var/log. Create a compressed archive (tar.gz) archive from command line.

    Run a terminal and move to /usr/NX/var :

    $ cd /usr/NX/var/
    $ sudo tar cvfz NoMachine-log.tar.gz log
    Create a compressed archive of the .nx directory in the user’s home

    Run from a terminal:

    $ tar -cvp –exclude ‘cache*’ –exclude ‘images’ –exclude ‘recording’ -f – $HOME/.nx | gzip -c >nxdir.tar.gz

     

    How to gather client side logs

    Run from a terminal:

    $ tar -cvp –exclude ‘cache*’ –exclude ‘images’ –exclude ‘recording’ -f – $HOME/.nx | gzip -c >nxdir.tar.gz

    • This reply was modified 7 years, 1 month ago by Avatargraywolf.
    #2922
    AvatarzSeries
    Participant

    Hi graywolf, here are the logs. I hope they help identify the problem.

    Thank you.

    #2935
    Avatargraywolf
    Moderator

    Sorry, we’d need content of .nx directory from server side, too.

    Please, connect to the server and run form a  terminal:

    $ tar -cvp –exclude ‘cache*’ –exclude ‘images’ –exclude ‘recording’ -f – $HOME/.nx | gzip -c >nxdir.tar.gz

    Other pieces of information that could help can be gathered running the commands:

    $ xmodmap -pke > xmodmap.txt

    $ xprop -root | grep XKB > xprop.txt

    Please note that a new version (4.2.17) is available. Let we know if you find the same problem after the upgrade.

Viewing 4 posts - 1 through 4 (of 4 total)

Closed because the user did not provide further feedback. Please notify us if you confirm that it is resolved or open a new topic if you have the same problem.