Skip to content
Permalink
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
106 lines (63 sloc) 2.98 KB
original_url created_at updated_at closed_at status type resolution reporter owner priority milestone component version
2011-03-01 23:13:33 -0800
2015-08-13 02:03:03 -0700
2011-04-13 08:47:54 -0700
closed
usability
Cannot Reproduce
hkkf1970@…
jeremyhu@…
Important
2.6.2
xserver
2.6.0 (xserver-1.9.3)

keyboard mapping is broken by NX

When using XQuartz 2.6.0 with 10.6.6 and NX Client 3.4.0-8, the keyboard gets garbled, exactly in the manner posted here by someone else 2 years ago:

http://forums.macnn.com/82/applications/392366/x11-keyboard-has-been-remapped/

In particular, the mapping gets crazy like this:

q = '-'
w = '='
e = BACKSPACE
r = NOT SURE
t = 'w'
y = 'q'

z = 5
x = 6
c = 7
v = 8
b = 0
n = 'x'
m = 'c'

DELETE = ','

I have had to uninstall XQuartz and revert back to X11 2.3.5 to get my keyboard working again under NX Client.


jeremyhu@… commented on Mar 1, 2011

  • Status changed from new to assigned
  • Summary changed from keyboard mapping screwed to keyboard mapping is broken by NX
  • Milestone set to 2.6.2

You don't need to uninstall XQuartz to use 2.3.6 ... they co-exist... just use 2.3.6 (X11.app) instead of 2.6.0 (XQuartz.app)

There's really not much info to go on here. Do the following (from 2.6.0):

1) Run xterm.
2) Type in the xterm ... is it broken?
3) Run NX
4) Type in NX ... assuming broken...
5) Go back to your xterm
6) Type in xterm ... is it broken?

Please provide the output of 'xmodmap -pke' for both the working and broken state (you may need to copy/paste the command into xterm while "broken"


jeremyhu@… commented on Mar 1, 2011

  • Description modified

jeremyhu@… commented on Apr 12, 2011

Ping. Please provided the requested information, or the bug will be closed.


krahn@… commented on Apr 13, 2011

From my experience using NX in Linux, NX is badly designed. It sends keycodes instead of KeySyms to the remote NX session. This causes the remote session to behave badly, unless you install the local keyboard map into the remote X session. It is a problem with NX and not the X server. However, that should have no effect on the local keyboard mapping.


jeremyhu@… commented on Apr 13, 2011

  • Status changed from assigned to closed
  • Resolution changed from to worksforme

Closing unless more information can be provided.

You can’t perform that action at this time.