Red Hat Bugzilla – Bug 76553
Xnest does not use local keyboard definitions
Last modified: 2007-04-18 12:47:53 EDT
Description of Problem:
When running Xnest, the keyboard map in the clients is everytime
the US map. The keyboard works perfectly in all the other windows.
Version-Release number of selected component (if applicable):
Steps to Reproduce:. Run a X session with a keyboard map not US, for
Note that I do not run with es_ES locale, I hate this, but simply with
the appropriate Xmodmap.
2. run Xnest :1 &
3. xterm -dispaly :1
Keyboard map for the xterm in the Xterm window is US
Keyboard map for the xterm in the Xterm window is the same as the
"main" X server
This is the expected behaviour from the commands that you are running.
You are running the Xnest server directly by hand by typing "Xnest :1"
and getting just what you asked for. Running Xnest in this way is
identical to starting up X by typing "X" - you don't get xmodmap there
If you want the Xnest server to start up similaraly to XFree86 server
then you need to invoke it properly with startx or xinit. If you need
further assistance for this problem, please subscribe to the XFree86
user/developer mailing list firstname.lastname@example.org and someone can assist
you in configuration of any custom scripts you may need.
Hope this helps.
Closing bug NOTABUG.