Hello, again.

Really sorry if I'm posting in the wrong places, I'm not sure if it's the Guided Posting or me - this is my second question and both times it has been about something not in the provided applications list. Either I'm missing something really obvious, or I am having issues nobody else has had (which is about right for me lol)

On first boot and after resuming from stand-by, the login/desktop/session(?) manager SDDM fails to recognise my [Return] key. However, the keypad [Enter] key works just fine.

I enter my password and hit [Return] nothing happens, if I then simply press [Enter] I log in.

After a successful log-in/unlock, the Return key is recognised in SDDM again.

It's a strange one and I have never come across it before.

It would be awesome if I could post videos of my issues as text descriptions leave too much to assume - I haven't seen a support structure that provides this yet.

Also, the login screen seems to use #eee text on a #fff background. I guess it was somehow changed when I re-themed the desktop lol

Lastly, do I have to post a separate question for each issue I have, or can I just list them in a single post when I get them? I only ask as it seems that each post seems like it should relate to a single application. Some forums are like war camps lol

Same here ... it started after last update

My sistem:
Operating System: KDE neon 5.17
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.2
Kernel Version: 5.0.0-37-generic
OS Type: 64-bit
Processors: 12 × Intel® Core™ i7-8086K CPU @ 4.00GHz
Memory: 31,3 GiB of RAM

I can confirm this issue, too.

I came here searching for the same problem. I have a little bit more information, maybe others can test and confirm.

- The issue happens on either the login screen or the lock screen

- if I intentionally type an incorrect password and hit enter I see the message "unlocking failed". This tells me that the enter key is actually submitting the password for authentication, so I don't think the issue is that the enter key does not submit the password, it's just that after the correct password is submitted the screen does not unlock

- the enter key does work sometimes, I haven't noticed an exact pattern but length of time the screen is locked does seem to be a factor. the enter key seems to work most times if I try to unlock it right after it locks. As a test if I Ctrl+Alt+L lock my screen then immediately type my password the enter key almost always works, i'm talking under 15 seconds. If I leave my desk and come back 5-10 min later it almost never works.

- I have duplicated this issue on 3 different computers

- I didn't see anyone explicitly say this so I will add that clicking the arrow next to the password field is how I log in when the enter key doesn't work. The arrow works 100% of the time. I do this without retyping my password. Enter...nothing...then arrow and I'm in.

OS: KDE neon User Edition 5.17 x86_64
Host: Precision Tower 7910
Kernel: 4.15.0-72-generic
Uptime: 4 days, 5 hours, 32 mins
Packages: 2804
Shell: bash 4.4.20
Resolution: 1920x1200, 1920x1200, 1920x1200, 1920x1200
DE: KDE
WM: KWin
Theme: Breeze Dark [KDE], Breeze [GTK2/3]
Icons: Breeze-dark [KDE], Breeze [GTK2/3]
Terminal: konsole
CPU: Intel Xeon E5-2687W v4 (24) @ 3.500GHz
GPU: NVIDIA GeForce GTX 980
Memory: 10387MiB / 128855MiB

I wanted to write the same findings this weekend.

thank you for your time @wxnarwhal

I can confirm all these findings from @wxnarwhal.

These are machines I'm using KDE on
Operating System: KDE neon 5.17
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.2
Kernel Version: 5.0.0-37-generic
OS Type: 64-bit
Processors: 12 × Intel® Core™ i7-8086K CPU @ 4.00GHz
Memory: 31,3 GiB of RAM


Regards

Armando

Me too, issues with sddm login and Enter key with different PC's:
I noticed several days ago a similar problem: the enter key is not working in the sddm-greeter login, although it is working the enter from the numeric keypad. No difference if the password is ok or not.

I've changed the keyboard to check if it is related to hardware, but no, the problem remains. Nevertheless, the enter key is working normally after login, for example in terminals. And I found this problem in 2 PC's.

I've checked the keycodes:
keycode 36 (keysym 0xff0d, Return) for normal enter and keycode 104 (keysym 0xff8d, KP_Enter) for numeric keypad return

$ dpkg -l sddm
ii sddm 0.17.0-2+18.04+bionic amd64
but I've just now checked it hasn't been upgraded for at least November December

Instead I've found the package kde-config-sddm has been updated on Dec 4rd
dpkg-l_191203.gz:ii kde-config-sddm 4:5.17.3-0xneon+18.04+bionic+build41 amd64 KCM module for SDDM
dpkg-l_191205.gz:ii kde-config-sddm 4:5.17.4-0xneon+18.04+bionic+build42

Edit: Enter key not working only if it has been clicked on the input text area.

I have the same problem, sddm intermittently does not respond to carriage return on login or lock screen. Carriage return works correctly in all other programs.

System Info:
KDE Neon 5.17.4
KDE Frameworks Version: 5.64.0
QT Version: 5.13.2
Kernel Version:4.15.0-72-generic
OS Type: 64-bit

Also to note. As long as I don't click in the password field and type the password followed by a return it works correctly and responds to the carriage return. However if I click in the password field and then type return it, it fails to respond to the return. So what I was initially seeing as intermittent behavior may have been because sometimes I click in the password field before typing the password and sometimes I don't.

+1 Having this exact issue since a while. Here is a GitHub issue to track regarding this problem. https://github.com/sddm/sddm/issues/1215

One year on and I'm seeing this issue on the latest KDE Neon. Due to the nature of this bug and whether you experience it depends on your 'technique' in entering your password.

So assuming your screen has auto locked/blanked and you want to wake up the screen and log in you can do this in three subtly different ways. One of those three ways will show this bug the other two ways won't show the bug.

The three techniques for logging in.

1. You move the mouse, the login screen appears, you position the mouse cursor in the password box and click left. You type the password and hit return..... Then nothing happens. This technique shows the bug.

2. You move the mouse, the login screen appears, you DO NOT click in the password box but instead immediately start typing the password and hit return. You're now logged in! This method does not show the bug.

3. You move the mouse, the login screen appears, you either click left in the password box OR NOT, it doesn't matter which, you enter your password and DO NOT hit return. You click left on the login button. Your're now logged in! This technique does not show the bug.

So I would be interested in anybody that does not have this problem, to try using precisely the steps described in technique 1 above and let's us know whether you can reproduce this bug.

update: 22/12/2019. I can also confirm that as per the comment by @rmndz above, the numeric keypad enter key works, it's the main enter key that has the issue.

therealsteelskin wrote:One year on and I'm seeing this issue on the latest KDE Neon. Due to the nature of this bug and whether you experience it depends on your 'technique' in entering your password.

One year on? For me it's a surprise, I don't have this impression (using KDE Neon). For me, it is a bug that appeared recently, because now I've realized that I used to click on the password area and I've found this problem in two PC's at the same time several weeks ago. But I might be wrong, it is just an impression...

Edited:
Note1: I've just tried to log in with several laptops and I have found that one of them had the Return key codified as KP_Enter (numeric keypad enter), then the bug it didn't affect
Note2: Booted a laptop with "neon-user-20191205-1116.iso", blocked the display, and it had this bug (and the Return key well codified)

rmndz wrote:

therealsteelskin wrote:One year on and I'm seeing this issue on the latest KDE Neon.

I'm referring to the following bug (sorry forgot to link to it https://github.com/sddm/sddm/issues/1107. This was a bug in sddm reported a year ago. I agree with you that it has surfaced in KDE Neon at the beginning of December 2019, it may have been in upstream for a year. It's just taken that long to work it's way through debian SID, testing, stable, then Ubuntu and finally KDE Neon.

I can confirm this issue exists in KDE Neon 5.17 & SDDM. It would seem that the problem presents itself if you click the mouse in the password box. If, for example, you simply move the mouse to wake the computer or to have SDDM display the password box, but you don't click into it and you just start typing then the problem doesn't manifest. If you do click into the password box, then you are unable to use the ENTER key to action the log in. I don't know if this is limited to KDE Neon as this behaviour doesn't happen with my other Kubuntu 19.10 desktop.

scotthews wrote:I can confirm this issue exists in KDE Neon 5.17 & SDDM. It would seem that the problem presents itself if you click the mouse in the password box. If, for example, you simply move the mouse to wake the computer or to have SDDM display the password box, but you don't click into it and you just start typing then the problem doesn't manifest. If you do click into the password box, then you are unable to use the ENTER key to action the log in. I don't know if this is limited to KDE Neon as this behaviour doesn't happen with my other Kubuntu 19.10 desktop.

Great to see others with this issue, misery loves company .

Like to add to the above, if you click in the box the enter doesn't work, but clicking back out of the box allows the enter button to work again, at least in my case.

therealsteelskin wrote:
I'm referring to the following bug (sorry forgot to link to it https://github.com/sddm/sddm/issues/1107. This was a bug in sddm reported a year ago. I agree with you that it has surfaced in KDE Neon at the beginning of December 2019, it may have been in upstream for a year. It's just taken that long to work it's way through debian SID, testing, stable, then Ubuntu and finally KDE Neon.

Thankfully, this route is inaccurate

Here is a more relevant, and current bug report with many dupes, and hopefully some attention.
https://bugs.kde.org/show_bug.cgi?id=415130

It seems it has been solved and it was related to qtvirtualkeyboard as it says @ https://bugs.kde.org/show_bug.cgi?id=415130

My packets:
sddm 0.18.1-0+18.04+bionic+build16 @ http://archive.neon.kde.org/user
qtvirtualkeyboard-plugin:amd64 5.14.1+dfsg-0xneon+18.04+bionic+build37

Operating System: KDE neon 5.18
KDE Plasma Version: 5.18.1
KDE Frameworks Version: 5.67.0
Qt Version: 5.14.1