CDE problem on Tru64 5.1B

• Previous message: Bill Sadvary: "SDLT hotswap?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Date: Thu, 16 Dec 2004 22:22:40 +0100
To: "'tru64-unix-managers@ornl.gov'" <tru64-unix-managers@ornl.gov>

Hi managers.

I've run into a very strange problem, I cannot get a grip on. This is
the background.

An AlphaServer was installed in Spain with a spanish keyboard. The
machine came over to us, without the keyboard, mouse, just a bare
machine. We hooked a vanilla plain US keyboard on it. The problem is,
the keyboard is messed up. No application using keys is showing wrong
keys being pressed - dtterm, dtpad, dtcalc,...

Another funny thing is that this mixup is in place only for one user,
which was setup in Spain. "root" is OK, other users are OK and any newly
created user is OK. The mixup is present in both local X sessions and a
remote one (via X-Deep 32).

My conclusion is that the keyboard mapping is wrong. Trouble is I cannot
locate this mapping. From my expirience, any keyboard mapping is done
via "dxkeycaps", which generates a ".dxkeycaps" file, which you should
load via "${HOME}/.dt/sessions/sessionetc" script. There is no such
thing and no file mentions "xmodmap" (used for applying the mapping).

Furthermore, running "dxkeycaps", choosing a keyboard
"keyboard_us->pcxal", saving the mapping and invoking it from
"sessionetc", leads to no improvement in keyboard, but messes up mouse
in X-Deep 32!!! How can that come to be, is beyond me.

Invoking "xmodmap" from ${HOME}/.dtsession (as sugested by "dxkeycaps")
blocks the session initialization - we get past login, but it freezes
after that.

Is there anything I can lookup further?
Is there some global setting for keyboard type?
If so, why is it not being applied on all users?
If it is local, where is it?

TYIA,
Nix.

• Previous message: Bill Sadvary: "SDLT hotswap?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]