Bug 76553
Summary: | Xnest does not use local keyboard definitions | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | romano |
Component: | XFree86-Servers | Assignee: | Mike A. Harris <mharris> |
Status: | CLOSED NOTABUG | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-10-23 11:27:44 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
romano
2002-10-23 11:27:37 UTC
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 either. 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 and someone can assist you in configuration of any custom scripts you may need. Hope this helps. Closing bug NOTABUG. |