Keyboard mapping wrong (OSX Lion/RedHat
Status: Beta
Brought to you by:
felfert
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).
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.
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.
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:
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)
Do you use the X11 server which comes with 10.7 or do you use the X11 server from here
http://xquartz.macosforge.org/
?
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:
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...
I can' say why, but this fixes the keyboard mapping issues which only seem to occur when using OpenNX to Linux-based hosts.
If you have a newer version of xkeyboard-config (on RHEL/CentOS) missing this file will indeed cause problems:
https://bugs.freedesktop.org/show_bug.cgi?id=50553#c19
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)?
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)" (!)
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.
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.