Wrong keyboard mapping

Addition: I found with 'xmodmap -pke', that keycode '27' from the Sun Type 6 keyboard is interpreted as 'Q' while it from the PC keyboard results in an 'R'.

Apparently Virtuoso interprets the keycodes as they are originated in a PC keyboard.

Unfortunately 'setxkbmap' leads to 'XKB extension not present on localhost:10.0' (Xsun / X11R6.6.2). But remember - all other applications are okay.

Regards

Kay

Kay,

No idea, I'm afraid, but what you're doing is pretty unusual (I'm not aware of anyone using Solaris boxes for such things nowadays). The fact that xmodmap shows the wrong key assigned is a little strange. You could also try using "xev" and seeing what that shows as the key that is pressed when you hit the keys on the keyboard. If that mapping is wrong, then all bets are off.

I don't know which window manager you're using - presumably that's a Window manager on the Sun (CDE?), but normally you can control the keyboard layout in (say) KDE via the System Settings->Input Devices->Keyboard. Not sure how that's going to work in the case when it's wrongly mapping the keys - or how some applications "are okay". Without seeing the system and what's going on, it's hard to debug, and I wouldn't know where to find anyone with this set up.

Andrew

Kay,

No idea, I'm afraid, but what you're doing is pretty unusual (I'm not aware of anyone using Solaris boxes for such things nowadays). The fact that xmodmap shows the wrong key assigned is a little strange. You could also try using "xev" and seeing what that shows as the key that is pressed when you hit the keys on the keyboard. If that mapping is wrong, then all bets are off.

I don't know which window manager you're using - presumably that's a Window manager on the Sun (CDE?), but normally you can control the keyboard layout in (say) KDE via the System Settings->Input Devices->Keyboard. Not sure how that's going to work in the case when it's wrongly mapping the keys - or how some applications "are okay". Without seeing the system and what's going on, it's hard to debug, and I wouldn't know where to find anyone with this set up.

Andrew

Hi Andrew,

thank you very much for your answer.

Actually CDE 1.6.10 is the Window manager on the Sun. 'xev' (executed on the linux server via ssh from the solaris box) delivers the correct keycode and key.
To enable the XKB extension, I appended '+kb' to '/usr/dt/config/Xservers'. And indeed I'm one step further (on the Solaris box via 'ssh -X' to the Linux server):

$ setxkbmap -v 10 -rules /usr/share/X11/xkb/rules/base -model sun_type6_usb -layout us
Setting verbose level to 10
locale is C
Warning! Multiple definitions of rules file
         Using command line, ignoring X server
Warning! Multiple definitions of keyboard model
         Using command line, ignoring X server
Warning! Multiple definitions of keyboard layout
         Using command line, ignoring X server
Trying to load rules file /usr/share/X11/xkb/rules/base...
Success.
Applied rules from /usr/share/X11/xkb/rules/base:
rules:      /usr/share/X11/xkb/rules/base
model:      sun_type6_usb
layout:     us
Trying to build keymap using the following components:
keycodes:   sun(type6_usb)+aliases(qwerty)
types:      complete
compat:     complete
symbols:    pc+sun_vndr/us+sun_vndr/solaris(defaults)
geometry:   sun(type6)
Error loading new keyboard description

$ setxkbmap -rules /usr/share/X11/xkb/rules/base -query
rules:      /usr/share/X11/xkb/rules/base
model:      type6_usb
layout:     us

It seems to exist a problem with loading the new keyboard layout. But the main trouble is now, that Virtuoso completely fails:

Qt Warning: Qt: couldn't get core keyboard device info
\w Qt Warning: The X11 connection broke: No error (code 0)
IO Error 11 (Resource temporarily unavailable) on Display "localhost:11.0" at UTC 2023.02.06 13:23:25.999
\e IO Error 11 (Resource temporarily unavailable) on Display "localhost:11.0" at UTC 2023.02.06 13:23:25.999
Aborting due to fatal X IO error.

Other (also) QT Applications are still running without a hitch.

Kind regards

Kay