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!
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.
I just tested your theory on my debian box using OpenOffice Writer and GNOME-terminal. I specifically did not release the Caps lock while I was typing. I use a USB keyboard, and It still types caps even on Keypress. GNOME responds on Keypress. I do have this problem that he mentions, but I'm not a buffoon who uses his Caps Lock to type single capital letters. I learned a long time ago to not be stupid.
What? Caps Lock is activated on key press but only deactivated on a subsequent key release (not press). This isn't a "theory", it's a fact, read the X server source code.
Quote:
Also, Whizje had the right answer
No, he didn't. I use a PS/2 keyboard, interrupt latency is irrelevant. As I have stated several times, this "problem" occurs because the X server only deactivates Caps Lock (and Num/Scroll Lock) on key RELEASE. As for USB, potential latency is not actual latency. I hope nobody is stupid enough to suggest that every keypress has a reproducible 200-300ms delay?
Last edited by lej; 09-12-2011 at 12:03 AM.
1 members found this post helpful.
Click here to see the post LQ members have rated as the most helpful post in this thread.
Distribution: Ubuntu 11.4,DD-WRT micro plus ssh,lfs-6.6,Fedora 15,Fedora 16
Posts: 3,233
Rep:
sheesh, all this effort working against a well established system.
back in the days of manual typewriters, all the caps lock key DID was mechanically latch the shift key into place until released, hence the name caps LOCK, it was often pressed if i am not mistaken at the same time as the shift key, or perhaps was mechanically linked to the shift key in some models, either way, it would probably have a similar delay if not even greater in length. I would personally learn to use the shift key instead of continuing on with a broken way of doing things. Your complaint that there is a 'problem' is kinda like asking why a staple gun isn't good at stapling together a stack of paper, yeah it uses staples but it wasn't designed for stapling a stack of paper together.
sheesh, all this effort working against a well established system.
back in the days of manual typewriters, all the caps lock key DID was mechanically latch the shift key into place until released, hence the name caps LOCK, it was often pressed if i am not mistaken at the same time as the shift key, or perhaps was mechanically linked to the shift key in some models, either way, it would probably have a similar delay if not even greater in length. I would personally learn to use the shift key instead of continuing on with a broken way of doing things. Your complaint that there is a 'problem' is kinda like asking why a staple gun isn't good at stapling together a stack of paper, yeah it uses staples but it wasn't designed for stapling a stack of paper together.
LOL... I think overall, people should think about what they are trying to say, and realize that this is linux, and linux wasn't made for complete newbies. That's only my two cents Pretty much, what I am trying to say is get over it, and don't use the caps lock for normal typing.
I don't find the last 2 posts helpful. I agree w/ the thoughts, but at this point in the thread they are no longer helpful, because the ground rules just changed: OP is now offering to pay for the fix he wants.
One of the virtues of Linux is the possibility of "having it your way"; whether by writing your own customization, or hiring someone to do it. We've warned OP over & over, but he is now putting his money on the table & so it's time to shut up about "why not" & instead discuss "who" & "how".
That is true also. I'm not even in it for the money.... I just like to help. That being said though, maybe we can collaborate on what to do, what the original problem is, and what we need to do in order to tackle this problem. I'm down for anything, and my previous post is what I only thought at the time to speak my mind. Like Rick said, let's do this and try/attempt to fix this.
I have already explained what the problem is, and provided an example patch. I don't know if it works as I don't feel like recompiling X (not my problem), but that is the root cause of the issue.
Again, caps lock is turned on when you PRESS it, but only turned off when you press AND RELEASE the key. This is what is causing the perveived delay.
When I say turned off, I mean the X server only updates its internal state when the key is released, the LED is turned off when you press the key, but the server's modifier bit remains on until you release it. You can see this with xev, as I also mentioned previously.
I have already ... provided an example patch. I don't know if it works as I don't feel like recompiling X (not my problem), but that is the root cause of the issue. ....
That will depend on how long it will take and how much work there is needed to be done. If someone can provide details and quote a price for me, we can work something out. PM me. Note, I would like this modification done on my Mint distro.
I don't think the OP fully understands what it does.
Will he pay for every xorg update (using lej's patch)?
Quote:
Originally Posted by cedricsm
That will depend on how long it will take
It will take as long as you plan using GNU/Linux.
I agree with lej here.
Unless it's done at distro level, it's no more than a couple of commands.
Are you willing to pay a debian package maintainer?
Paying for a such a weird package means paying for everyting.
Edit: Their exist a few projects using scripts to modify your system, it might be better to ask them to do (and automate) this.
Example: http://smxi.org/site/about.htm
Last edited by jens; 10-06-2011 at 11:59 AM.
Reason: Sorry for the the many edits, i'm having wifi problems :(
Distribution: Ubuntu 11.4,DD-WRT micro plus ssh,lfs-6.6,Fedora 15,Fedora 16
Posts: 3,233
Rep:
honestly if it's that much of a bother to you why not learn to make the necessary changes yourself? that is the beauty of open source software such as Linux after all, nobody is stopping you from making the changes yourself. Seriously, short of paying someone enough, which would probably be prohibitively expensive, i can't think of many people who really would want to bother taking on a task that will only benefit a group of people small enough to count on one hand and especially one that really is imho counterproductive, not when there are security holes that allow remote execution of arbitrary code, or bugs that cause a total crash of the system to search for.
*edit* and i'm not just saying this to be mean, but if you really understood what it took just to make a 'simple' change, you might not be so insistent that people who by and large volunteer their time to a common cause fix something they don't see as a problem to begin with.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.