Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 76553 - Xnest does not use local keyboard definitions
Xnest does not use local keyboard definitions
Product: Red Hat Linux
Classification: Retired
Component: XFree86-Servers (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Mike A. Harris
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2002-10-23 07:27 EDT by romano
Modified: 2007-04-18 12:47 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-10-23 07:27:44 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description romano 2002-10-23 07:27:37 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):


How Reproducible:

Steps to Reproduce:. Run a X session with a keyboard map not US, for 
example,   spanish.
   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

Actual Results:
Keyboard map for the xterm in the Xterm window is US

Expected Results:
Keyboard map for the xterm in the Xterm window is the same as the 
"main" X server

Additional Information:
Comment 1 Mike A. Harris 2002-10-23 12:10:42 EDT
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 xpert@xfree86.org and someone can assist
you in configuration of any custom scripts you may need.

Hope this helps.

Closing bug NOTABUG.

Note You need to log in before you can comment on or make changes to this bug.