Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#31 Keyboard mapping wrong (OSX Lion/RedHat

open
Fritz Elfert
None
5
2015-02-13
2011-11-10
Arun Rao
No

The Linux host is running the NX server, and I'm able to connect to it using the latest build of OpenNX. But the keyboard mapping is completely messed up. Yes, I tried the workaround suggested elsewhere (editing ~/.nx/config/<host>.nxs, but that appears to do absolutely nothing.

My Mac is recent vintage iMac.

(Also, attempting to resume a session causes OpenNX to crash ... but that's a separate bug).

Discussion

  • JM
    JM
    2011-11-29

    The keyboard mapping is correct with version 0.16.0.648, so switch back to this version… it fixed the problem for me. With the current version 0.16.0.649 the keyboard mapping is completely messed up.

     
  • Keith Nesson
    Keith Nesson
    2011-12-06

    I have been working on a Lion (10.7.2), MacBook Pro running the .648 build with no sucess in getting proper keyboard mappings. Seems to be totally random as another machine works with no problem.

     
  • Fritz Elfert
    Fritz Elfert
    2012-02-04

    Except for .249 (which used an experimental attemt to fix the prob) all newer versions (>= 250) use the same handling. Using my new Mac (Thanks to all donors!) i was able to analyze a bit more now. The actual problem is a combination of multiple things:

    1. The main prob: Apple broke XKB query support in X11 on 10.7 but provides the newer Xinput2 extension.
    2. The proper necessary changes would involve both server (the nxagent) and client side - so far as as OpenNX is concerned, this not really an option.
    3. As a side-effect it does work, if connecting to X11 Desktops on the remote side and if using default keyboard settings. (The "empty/empty" XKB rule results in the server switching to "transparent" mapping which works in almost all cases.)
    4. What definitively does not work out of the box: Connecting to remote RDP (Windows) Sessions, because in those cases, the server side requires a country-specific layout in order to produce the right parameters for running rdesktop resp. vncviewer.

    For (4), there is a server-side workaround:
    If using FreeNX, set the following options in node.conf:

    ENABLE_EXTERNAL_NXDESKTOP_KEYBOARD="0"
    AGENT_EXTRA_OPTIONS_RDP="-k XX"

    (XX=Your language code)

     
  • JM
    JM
    2012-07-19

    Do you use the X11 server which comes with 10.7 or do you use the X11 server from here

    http://xquartz.macosforge.org/

    ?

     
  • JM
    JM
    2012-07-19

    With version 713 "only" the key 'p' and 'tab' are broken, the rest of the keyboard mapping is correct. I tired all workarounds but nothing helps. Of course without the letter 'p' and 'tab' it's…well... difficult to work.

     
    • I too had this problem with characters p and Tab not working (local OpenNX 0.16.0.725, XQuartz 2.7.4 and Mac OS X 10.8.3; remote Ubuntu 12.04.2, Xfce 4.8). It seems that the X11 server thinks that the Super key (which I guess is Command in Mac OS X) is stuck, and Xfce contains a default binding for Super-Tab and Super-p. These can be removed with the commands:

      sed -i '/property name="&lt;Super&gt;p"/d' \
        ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-keyboard-shortcuts.xml
      sed -i '/property name="&lt;Super&gt;Tab"/d' \
        ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-keyboard-shortcuts.xml
      
       
  • Joe Neuhaus
    Joe Neuhaus
    2013-03-24

    I know this post is ancient, however, I've been seeing this issue on and off the past year and just stumbled on a fix that seems to solve my problem...on the host computer you're connecting to, simply run the following command after any O/S upgrades or changes to xorg files, etc...

    # touch /usr/share/X11/xkb/keymap.dir
    

    I can' say why, but this fixes the keyboard mapping issues which only seem to occur when using OpenNX to Linux-based hosts.

     
  • JM
    JM
    2013-06-29

    The problem still exist, I tried all workarounds... but the keyboard mapping is completely messed up. Is there a chance to fix this bug?

     
    • Have the .725 version more keys than 'p' and 'tab' not working? What is the remote system which you are connecting to (operating system, desktop environment)?

       
      • JM
        JM
        2013-06-29

        Yes, the layout is messed up, looks like random keys.. you press x and get k, press j and get 4 and so on, for all keys. The client system is Mac OS X 10.8.4 with XQuartz 2.7.4 (xorg-server 1.13.0), the remote system is CentOS 6.4 with nxserver-3.5.0-11.x86_64 (from NoMachine) and Gnome 2.28.2 as desktop environment.

         
        • OK, one more work-around which I discovered to get to the "only-p-and-tab" state: In the Advanced Configuration dialog, select [X] Use custom language and then pick "English", NOT "English (United States)" (!)

           
          • JM
            JM
            2013-06-30

            Nope, not me for, still the same result. OpenNX is completely useless for MacOS X :-(

            The NXPlayer from NoMachine works but it is still a Preview...

             
  • This still doesn't work right. I'm running 0.16.0.729 on Mac OS X Mavericks (that's 10.9 right?). What I have found though is that resuming a session that was started on some other OS (Linux in my case) gets me a keyboard mapping that works just fine. I don't know if that helps, but since OpenNX is the best client for Mac OS, hopefully we can fix this.

     
    • Scott Givan
      Scott Givan
      2014-01-10

      Resuming a session worked for me, too. I'm running Mac OS 10.9.1 & OpenNX 0.16.0.725. On a Fedora 19 box I'm running freenx-server 0.7.3-31.fc19.