HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- wrong keyboard mapping with xdmcp
Operating System - Tru64 Unix
1827459
Members
3947
Online
109965
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-22-2005 08:11 AM
11-22-2005 08:11 AM
wrong keyboard mapping with xdmcp
Dear Tru64 friends,
I'd like to log on remotely on my Tru64 5.1B CDE desktop using xdmcp. Security issues is here not a problem, since it is a closed network.
I start a new X session from my Unix box similarly to:
bash$ X :1 -query
I get immediately the hour glass, but it takes a while to get the "Welcome logging window". The logging works fine, thought it is much slower than logging locally.
The main problem that I have - excepted these performance issues - is that the keyboard mapping is totally wrong.
For instance q maps to q, e -> y, r -> s, t -> a, u -> 2, ENTER -> e etc.
I used this procedure already with Tru64 4.0D without any problem (whether from a performance perspective nor keyboard mapping).
Do you have an idea what I´m doing wrong?
TIA,
Loic.
I'd like to log on remotely on my Tru64 5.1B CDE desktop using xdmcp. Security issues is here not a problem, since it is a closed network.
I start a new X session from my Unix box similarly to:
bash$ X :1 -query
I get immediately the hour glass, but it takes a while to get the "Welcome logging window". The logging works fine, thought it is much slower than logging locally.
The main problem that I have - excepted these performance issues - is that the keyboard mapping is totally wrong.
For instance q maps to q, e -> y, r -> s, t -> a, u -> 2, ENTER -> e etc.
I used this procedure already with Tru64 4.0D without any problem (whether from a performance perspective nor keyboard mapping).
Do you have an idea what I´m doing wrong?
TIA,
Loic.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-23-2005 08:35 AM
11-23-2005 08:35 AM
Re: wrong keyboard mapping with xdmcp
Verify your .profile and .dtprofile. Check if there is a /usr/dt/bin/dxkeyboard -load entry. If so, try commenting that.
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-29-2005 07:46 AM
11-29-2005 07:46 AM
Re: wrong keyboard mapping with xdmcp
Dear Tru64 friends,
the culprit was xmodmap that was executed in $HOME/.dtprofile.
I commented that line out, and performed the corresponding loading in $HOME/.profile depending whether local or remote keyboard is used. Seems to work fine now.
The performance issue was a networking issue. Since the Tru64 box is connected to a switch, I had to set-up manually to Half-Duplex instead of the negotiated Full-Duplex...
Thanks to Ivan for pointing me to the right direction regarding the keyboard issue.
Cheers,
Loic.
the culprit was xmodmap that was executed in $HOME/.dtprofile.
I commented that line out, and performed the corresponding loading in $HOME/.profile depending whether local or remote keyboard is used. Seems to work fine now.
The performance issue was a networking issue. Since the Tru64 box is connected to a switch, I had to set-up manually to Half-Duplex instead of the negotiated Full-Duplex...
Thanks to Ivan for pointing me to the right direction regarding the keyboard issue.
Cheers,
Loic.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP