https://bugs.kde.org/show_bug.cgi?id=358775

JKAbrams <j...@jkabrams.se> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |j...@jkabrams.se

--- Comment #6 from JKAbrams <j...@jkabrams.se> ---
I can confirm this.

On the screen locker when the password field has focus, the shift key will
insert characters while being pressed. It's like key repeating but without the
timeout.

This makes it almost impossible to enter a password that contains a character
that needs shift to be pressed (and is not accessible by Caps Lock). I say
almost as I think it should be possible in theory to press shift + [special
key] and keep it down for some time so you are sure to have lots of special
characters of the right type in the middle, then you delete the characters
shift added on both sides, and you should be left with the special character
you need. In practice since the password field is so small it is very hard to
see how many characters actually gets added and there is the very annoying
feature that if you press the right key when the cursor is at the end of the
password focus shifts to New Session and the password is lost. After trying
this for quite some time to get back into a session with unsaved work I gave
up. This assumes that the shift key actually works as a shift key at all, which
I could never confirm.

Disabling the "Switching to another layout" > "Both keys together" setting
makes it work.

I just discovered that if you try to disable it by just unchecking the
"Configure keyboard options" on top it will not actually disable it, you have
to make sure the actual check box is unchecked.

Interestingly, after pressing Apply after doing any change on the Advanced tab,
if you then press Ctrl the Num Lock diode gets disabled (while Num Lock itself
stays on).
The diode stays off until a registered shortcut is triggered.
I have noticed wired behavior with Num Lock for some time, but this is a case
where I found something reproducible.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to