CAPS and Num Lock Don't work on applications running from a remote server
FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
CAPS and Num Lock Don't work on applications running from a remote server
Hi there --
We have several Fedora Core 2 systems running a remote application that resides on an HP-UX 11.11 server. The CAPS and Num Lock keys work on programs that are local to the workstations, but do not work on the remote application.
The LED's on the system keyboards illuminate, but the actual funtionality is not there. If you use the shift key, the appropriate character does appear. If we run the same remote application on a Windows system with Exceed, this problem does not occur.
Is this a keyboard mapping or definition issue that can be fixed?
This is very likely a problem with the configuration of the program that you are using to access the remote server, or with the kind of terminal that program tells the HPUX system that you are using.
First off, if you can, ask the HPUX system what kind of terminal it thinks is connected to your session (the shell variable TERM contains this. Second, check that HPUX has that terminal type in its termcap database (I forgot where they keep that, but look for /etc/termcap).
Then, if that terminal type is either not defined, or does not match the termtype that your local machine is using, you may need to inform the access program to send the right termtype when it connects to the HPUX machine.
I have the same issue. I'm using Cygwin w/ XDMCP to remotely login to an HP-UX system.
dkm999, I don't quite follow your suggestion, but I'm thinking it only applies for someone running remote terminals, as opposed to a full desktop through XDMCP; correct?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.