Bug 415197 - screenlocker: After clicking into PW field: return no longer works & Tab does not give fokus to [>] button
Summary: screenlocker: After clicking into PW field: return no longer works & Tab does...
Status: RESOLVED DUPLICATE of bug 415130
Alias: None
Product: kscreenlocker
Classification: Plasma
Component: greeter (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-15 12:25 UTC by Achim Bohnet
Modified: 2019-12-15 16:04 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Achim Bohnet 2019-12-15 12:25:37 UTC
SUMMARY:
after installing plasma 5.17.4 I've noticed that

* the 'return' key did not work in all cases.  When I start typing my PW and press return I get logged in.  But when I click before or after I've entered my PW into the PW field enter does *not* work anymore


STEPS TO REPRODUCE
1. Press Ctrl-Alt-L to activate the lockscreen
2. Type the our PW
3. Press enter
4. You're logged in. Good! As one expects

4. Repeat 1-2
5. Click into PW field
6. Press enter
7. Nothing happens -> Bug

8. Now Press Tab to transfer focus to [>] Button
9. Press enter
10. Nothing happens -> Bug


OBSERVED RESULT
Nothing happens

EXPECTED RESULT
One is logged in


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon User / Plasma 5.17.4
KDE Frameworks 5.65.0
Qt 5.13.2 (kompiliert gegen 5.13.2)
Das xcb Fenstersystem

ADDITIONAL INFORMATION
After clicking into the PW field or pressing (several) times Tab to give the PW field or [>] focus, the only way to unlock the screen is to click on the [>] button.
Comment 1 Achim Bohnet 2019-12-15 12:29:18 UTC
On all four KDE Neon installations, that I have, the can reproduce the described buggy behavoiur since upgrade to 5.17.4 ~ a week ago.
Comment 2 Nate Graham 2019-12-15 15:48:25 UTC

*** This bug has been marked as a duplicate of bug 415204 ***
Comment 3 Nate Graham 2019-12-15 16:04:18 UTC

*** This bug has been marked as a duplicate of bug 415130 ***