"{Darkavich} Steven Misrack" <[EMAIL PROTECTED]> wrote:
> Has anyone else had a problem with caps lock and shift not working
> once they upgraded to the 3.1 software? This happens when we use a
> KVM and a sun keyboard. Everything worked fine with the 2.x
> firmware.
>
> I have a ticket open, but am being told that it's not Sun's
> problem. <sigh>. Anyone from sun reading, it's ticket: 64902695
This sounds like bug 6344241, "When upgrading from Sunray 3.0 to 3.1
the Num lock and Shift keys don't work via KVM". The root cause in
that case really is not Sun's problem, the KVM is misbehaving.
However, the KVM's misbehaviour exposes a bug in the Sun Ray Xserver
(not in the firmware). The fix for that bug will be included in the
first 3.1 patch which should be publically available in the next few
days. So you should plan to install that patch. You should install
it anyway, it contains some important fixes.
If your KVM is misbehaving in the same way as the KVM in that bug
then with that patch installed the lock keys should stop going
insane. You'll still be left with the problem that the KVM is
reporting the wrong country/layout code for the keyboard. Depending
on the actual bad code reported by the switch you could end up with
the Xserver applying the wrong keyboard table or (the case in this
particular bug) you could end up with the Xserver having no clue
about what keytable to use. In the latter case the 3.1 FCS Xserver
tried to continue to use whatever keytable it had been using earlier
but the failure to find a keytable led to its lock-handling logic
getting confused. The patch fixes the lock-handling logic and
instead of continuing with whatever table happened to be loaded it
will apply the system's default keytable to the "unrecognised"
keyboard. It will also complain in /var/dt/Xerrors so you'll be
able to discover that something unpleasant is happening.
Until the patch comes out, as a workaround you could try editing
/usr/openwin/share/etc/keytables/keytable.map and adding a line that
says:
6 3 US6.kt
to the Type 6 keyboard list at the bottom of the file. (I'm
assuming that you have a US-layout keyboard.) Then log out to
terminate your current Xserver and get a new one that will use
the new configuration. The bad KVM in 6344241 was reporting a
layout code of 3 even though the keyboard itself correctly reports
a layout code of 33. I have not tried this workaround so I can't
guarantee that it will work, even assuming that your KVM is
misbehaving in the same way as the one in 6344241.
OttoM.
__
ottomeister
Disclaimer: These are my opinions. I do not speak for my employer.
--
___________________________________________________
Play 100s of games for FREE! http://games.mail.com/
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
