Operating System - Tru64 Unix
1827459 Members
3947 Online
109965 Solutions
New Discussion

wrong keyboard mapping with xdmcp

 
Loic Domaigne
Occasional Advisor

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.
2 REPLIES 2
Ivan Ferreira
Honored Contributor

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?
Loic Domaigne
Occasional Advisor

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.