I’m pretty sure I’ve seen this a few times over the years.
I learned to type on a mechanical monster, and later on moved on to electric typewriters.
The key locks on these were mechanical…
This means you press the key down and it gets stuck down (locked) and then the caps lock is on.
To release the (mechanical key) you have to press it down to ‘unhook’ it and then release it to turn caps lock off.
Linux is correct in this regard… test it if you like.
ff <press/hold capslock> FF FF <PRESS/HOLD CAPSLOCK> FF ff
For me this is totally normal.
However, today I was roundly criticized, because this is NOT the way it happens in Windows and Mac. And we all know that Windows and Mac define correct behaviour don’t we???
So some folks use Capslock instead of Shift, and if they type fast, they have issues WIth CAps not releasing (it’s a product of behaviour learned in Windows and Mac) and so they post comments about ‘Manjaro Caps Lock Delay’ or ‘Mint Caps Lock Delay’ or some other misinformed idea.
So I decided to fix it for them… so here goes:
METHOD:
Start by creating a copy of your keyboard map:
xkbcomp -xkb $DISPLAY keyboardmap
Edit the exported file (keyboardmap) and enter the text (find the section starting with key and paste over it)
key <CAPS> { repeat=no, type[group1]="ALPHABETIC", symbols[group1]=[ Caps_Lock, Caps_Lock ], actions[group1]=[ LockMods(modifiers=Lock), Private(type=3,data[0]=1,data[1]=3,data[2]=3) ] };
To apply your edited keyboard, file you do this:
xkbcomp keyboardmap $DISPLAY
Now do the typing test again. The caps lock is released when you press - and before you release the capslock key.
If you want to automate this, then write a script and put it in your startup.
#!/bin/sh
xkbcomp ~/keyboardmap $DISPLAY