With the previous upgrade to upstream version 2.11, the /usr/share/X11/xkb/keymap.dir file was removed from the xkeyboard-config packages. Consequently, X11 keyboard configuration stopped working for NX connections. This update includes the missing file again, and as a result, the broken functionality is restored.
Description of problem:
Through bug 835284, xkeyboard-config was rebased in RHEL6.4. The current package no longer provides a /usr/share/X11/xkb/keymap.dir file. This breaks NX (both Commercial and FreeNX).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Broken keyboard configuration when connecting to a RHEL6.4 system using NX.
Proper keyboard configuration when connecting to a RHEL6.4 system using NX.
Reportedly, a "touch /usr/share/X11/xkb/keymap.dir" is sufficient to make NX work again.
Bugzilla isn't letting me link this to external trackers
so noting this here for now.
Looking at the NX source, this is indeed the cause and a simple touch of that file is sufficient to fix it.
NXVerifyXkbBaseDirectory() uses that file to verify that a directory path is an xkb directory. It doesn't look at the file otherwise, so shipping an empty file would be sufficient.
We can revert the change in xkeyboard-config, that'll ensure the required files are shipped. Note that this will still not enable NX to work, see Bug 1157866.
Workaround as pointed out in Comments #0 and #2 seems to be:
This assessment is based on the X2go source code  as of version 184.108.40.206. The FreeNX sources are down and unavailable for verification, and the commercial one from nomachine seems to work fine (v4.3.30)
xkeyboard-config-2.11-2.el6 is available in brew
xkeyboard-config-2.11-3.el6 is available in brew
Verified on xkeyboard-config-2.11-3.el6. The file: /usr/share/X11/xkb/keymap.dir has been restored.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.