Bug 414875

Summary:	After entering the password, SDDM doesn't respond to pressing "Enter", you need to click on the ">" button to it's right
Product:	[Plasma] plasmashell	Reporter:	David de Cos <david.decos>
Component:	general	Assignee:	David Edmundson <kde>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	bugseforuns, filipfila.kde, kontakt, nate, plasma-bugs, tnbrev, uhhadd
Priority:	NOR	Keywords:	regression, usability
Version:	5.17.5
Target Milestone:	1.0
Platform:	Neon
OS:	Linux
Latest Commit:	https://commits.kde.org/plasma-workspace/c2bc5243d460c306f995130880494eec6f54b18a	Version Fixed In:	5.17.5
Sentry Crash Report:

Description David de Cos 2019-12-05 20:08:34 UTC

After entering the password, SDDM doesn't respond to pressing "Enter", you need to click on the ">" button on the right of the password dialog. This happens:

- After a failed attempt to login (e.g. wrong password). The second time you type your password, pressing "Enter" does nothing. I can reproduce this every time.

- The first time you enter your password, this bug can happen too, but not always. I don't know why, haven't seen a pattern.

I have only noticed this bug in the last couple of days, after updating to 5.17.4 (not sure if it's related). 

STEPS TO REPRODUCE
1. Log out of your Plasma session and go to SDDM.
2. Enter a wrong password -> login failed
3. Type again a password (the correct one or not), and press enter. Nothing happens. You have to click on the ">" button on the screen for it to read your password.

Comment 1 Patrick Silva 2019-12-06 00:34:20 UTC

same thing on Neon unstable edition:
click on the dropdown to select a user session
focus the password field
type your password and press enter
nothing happens

Comment 2 Filip Fila 2019-12-07 22:14:26 UTC

This looks like the only possible explanation: https://cgit.kde.org/plasma-workspace.git/commit/lookandfeel?h=Plasma/5.17&id=e7803ecc58272236a6dd491a9d05cf230202d88c

because the patch should have only landed in master as t's a fix for changes in master.

The patch doesn't seem to exist in Arch packaging of 5.17.4. fwiw.

Comment 3 Nate Graham 2019-12-07 22:19:40 UTC

Git commit c2bc5243d460c306f995130880494eec6f54b18a by Nate Graham.
Committed on 07/12/2019 at 22:18.
Pushed by ngraham into branch 'Plasma/5.17'.

Revert "[sddm-theme] Fix initial focus after SDDM QQC2 Port"

This reverts commit e7803ecc58272236a6dd491a9d05cf230202d88c.

This was supposed to be master-only. Sorry everyone!
FIXED-IN: 5.17.5

M  +1    -1    lookandfeel/contents/components/SessionManagementScreen.qml
M  +0    -1    lookandfeel/contents/lockscreen/LockScreenUi.qml

https://commits.kde.org/plasma-workspace/c2bc5243d460c306f995130880494eec6f54b18a

Comment 4 soee 2019-12-07 23:13:49 UTC

I have the same problem also on lock screen. I have to press the button to be able to unlock it.

KDE neon 5.17
Plazma KDE: 5.17.4
Frameworks: 5.64.0
Qt: 5.13.2
Kernel: 5.0.0-37-generic

Comment 5 Bhushan Shah 2019-12-10 21:00:13 UTC

*** Bug 414926 has been marked as a duplicate of this bug. ***

Comment 6 David de Cos 2020-01-09 14:31:48 UTC

After updating to 5.17.5 I still have this bug, although the 5.17.5 changelog claimed to fix it:

Revert "[sddm-theme] Fix initial focus after SDDM QQC2 Port". Commit. Fixes bug #414875

Comment 7 Christoph Feck 2020-01-21 09:35:42 UTC

Could someone please confirm if this issue is still reproducible?

Comment 8 Patrick Silva 2020-01-22 12:46:58 UTC

Still reproducible on Neon unstable edition.
Cannot reproduce on Arch Linux with Plasma 5.17.5 or 5.18 beta.

Comment 9 Christoph Feck 2020-01-22 13:20:13 UTC

Thanks Patrick, let's reopen for further investigation.

Comment 10 Patrick Silva 2020-01-22 13:51:23 UTC

Nate thinks it's a Qt bug. Read bug 415130 comment 14

Comment 11 Nate Graham 2020-01-22 15:12:14 UTC

Same issue as Bug 415130.

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