It's not a security feature, that's ridiculous.
Either don't use caps lock to capitalise individual letters when touch-typing, or file a bug report with Xorg to maybe have the problem fixed in later versions of X.
It's not a security feature, that's ridiculous.
Either don't use caps lock to capitalise individual letters when touch-typing, or file a bug report with Xorg to maybe have the problem fixed in later versions of X.
I try to treat the cause, not the symptom. I avoid the terminal in instructions, unless it's easier or necessary. My instructions will work within the Ubuntu system, instead of breaking or subverting it. Those are the three guarantees to the helpee.
Come to #ubuntuforums! We have cookies! | Basic Ubuntu Security Guide
Tomorrow's an illusion and yesterday's a dream, today is a solution...
You could try opening a terminal and using sudo for something trivial, then sudo -k, then sudo something trivial etc etc. If you recorded your desktop whilst doing this repeatedly you'd end up with a video and timeline. Perhaps change your password before posting it. Be worth seeing. If it's not a feature maybe look at your short cut keys, could be that when typed slowly the keys are seen individually but when fast you are unwittingly using a key combination ( more than one being held down at the same time ) which your system is set to recognise.
This is your problem. It has been known about for years and is a "problem" with xorg. Nothing to do with Ubuntu and certainly not a security feature.
You've correctly identified the delay - when you press caps lock the second time, the character typed immediately after will render as a capital if you are typing too fast. I've seen people describe this as a bug, but I don't know whether there has been a bug report raised with xorg. I've also seen debates about whether it is appropriate to use caps-lock in situations like this, some fast touch typists saying it is more efficient than using shift, and others disagreeing. I have no view since I am not a touch typist, and have no view whether this is a bug or not, but I have a pragmatic suggestion. Since the bug/feature is unlikely to go away soon, and since it is entirely out of Canonical's control, use the shift key for caps when typing in your password.
Ubuntu 20.04 Desktop Guide - Ubuntu 22.04 Desktop Guide - Forum Guide to BBCode - Using BBCode code tags
Member: Not Canonical Team
If you need help with your forum account, such as SSO login issues, username changes, etc, the correct place to contact an admin is here. Please do not PM me about these matters unless you have been asked to - unsolicited PMs concerning forum accounts will be ignored.
Bug was reported a while ago and there is a workaround : https://bugs.freedesktop.org/show_bug.cgi?id=27903
Basically, Xorg turns off Caps Lock when Caps Lock no longer registers as being "down" after being pressed the second time. Windows turns off Caps Lock when it registers the second press of the Caps Lock key.
I try to treat the cause, not the symptom. I avoid the terminal in instructions, unless it's easier or necessary. My instructions will work within the Ubuntu system, instead of breaking or subverting it. Those are the three guarantees to the helpee.
Noticed this a while ago, good for stopping someone from attempting to use my long, strong & hard pass phrase but every now and again I have to slow down and move my lips as I type.
Just remember to keep your keyboard crud free as just a little something caught under a key can give the impression of a fully depressed key when the reverse may well be true often causing all sorts of pass phrase problems.
Bookmarks