PLZ Fix the CAPS LOCK response time glitch in Linux Distros!
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I think the problem is that the OP is using caps to act as shift, and when after typing the first letter it just stays on for a sec, even after it is turned off.
If this is the case, The most simple solution would be: just use shift for it's intended purpose. To capitalize when needed. and caps for it's purpose, TO BE ABLE TO WRITE A SENTENCE AND NOT HAVE TO HOLD SHIFT.
I use this site as a resource of information many times, but I figured I would register an account to reply to this thread.
I have this issue as well. I've experienced this across many different flavors of Linux and on a Wyse terminal (not sure what OS Wyse was running back in the day).
I do believe it is an issue. Sorry to disagree with some of you all. The problem is that the OS does not detect the keystroke fast enough when turning CAPS Lock off. As soon as I type the letter 't' I see it on the screen that quick. I don't feel I get that same sort of response time when hitting the caps lock key.
How I type (using the CAPS lock key, or a shift key) doesn't really matter, because the issue still would exist. For those of you who say the CAPS lock key is around just to type long strings together in caps "HERE IS MY EXAMPLE", you would still experience the issue if you typed fast enough.
I REGISTERED FOR AN ACCOUNT Just to make this post. - The 'J' in that sentence should have been lower case, but because of the delayed CAPS lock key time, it came out as a capital letter instead.
I've been typing using the CAPS lock key for years. I can type 120wpm or so. I'm not interested in learning to use the shift key just because, or because I could then type faster. As others have mentioned, this isn't an issue within a Windows OS. I'm not saying that to compare Linux to Windows, just making an observation.
The only time this issue really irritates me is when I'm setting a password with capital letters in it and it's masked. Password123Abc is much different than PAssword123ABc!
A possible solution is to use a ps2 keyboard it uses a higher IRQ so that it doesn't have to wait for other IRQ's to finish first. Or you must give your keyboard a higher priority. Don't know if that's possible without a RT-kernel.
I got the same problem with a usb keyboard but a ps2 keyboard worked flawlessly.
The problem is that when you press caps lock linux waits for confirmation from the keyboard controller. This is done with a interrupt that's a signal to the processor that a device has data or can receive data. This confirmation can take 6 to 7 ms. But there are also other devices that send interrupts to the processor. And when there a multiple interrupts they are handled in priorities historically the ps2 keyboard had one of the highest priorities. But with the arrival from usb this has changed. A usb device can have a much lower priority so that it can take 200 or 300 ms before the keyboard interrupt is handled. In this time you can have pressed another key but as long the confirmation from the keyboard is not handled linux says caps lock is not enabled or disabled. So by using a ps2 keyboard you can be assured that a interrupt from the keyboard is handled as quickly as possible. The alternative is giving usb a high priority irq in the bios. Or fiddling with priority schemes as a last resort.