(I'm sorry if this is filed against the wrong product/component. I wasn't sure what to choose for KDE's lock screen. I did see the kscreenlocker entry, but I wasn't able to choose 5.12.4 for that) ## Description The Return/Enter key will stop working on the lock screen for all subsequent attempts after a failed password entry attempt. ## Steps to reproduce 1. Lock your screen 2. Enter an invalid password and confirm it with Return 3. wait for the confirmation message that it's the wrong password 3. Proceed to type in the correct password and try to confirm it with Return Result: The Return key is ignored Expected result: Return is accepted and you're logged in.
Can't reproduce. While the message is shown the field is disabled which is by design but as soon as you can type again, it works as expected.
Works here too Please run /usr/lib64/libexec/kscreenlocker_greet confirm if it works there, attach any console output and a screenshot then reset this bug status to unconfirmed
Thanks for the quick response, guys. Sorry to hear that you couldn't reproduce the issue thus far. Here is my CLI output when invoking kscreenlocker_greet manually and going through the reproduction steps: $ /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Haswell Desktop OpenGL version string: 3.0 Mesa 18.0.0-rc5 OpenGL shading language version string: 1.30 Driver: Intel GPU class: Haswell OpenGL version: 3.0 GLSL version: 1.30 Mesa version: 18.0 Linux kernel version: 4.15 Requires strict binding: yes GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no Locked at 1522771089 UdevQt: unable to create udev monitor connection Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) QXcbClipboard::setMimeData: Cannot set X11 selection owner QXcbClipboard::setMimeData: Cannot set X11 selection owner Authentication failure (I'm not sure how to take a screenshot of the lockscreen, so I left that out for now). A few more observations about the lock screen behaviour: - Widget focus seems to remain on the password entry field, visually at least (as indicated by the blue highlight around the text entry field) - Using the return key on the virtual keyboard does work - Clicking on the password entry field after retyping the correct password does not appear to resolve the issue - Clicking on any other screen area doesn't seem to have an effect, either - Unlocking the screen by clicking on the unlock button still works, of course And some additional details on my system, FWIW: - Platform: Kubuntu 18.04 Beta 1, updated as of 2018-04-03. Clean install. - Only one user - No customizations to the lock screen, apart from changing the user icon to Konqi - Locale: $ locale LANG=de_DE.UTF-8 LANGUAGE= LC_CTYPE="de_DE.UTF-8" LC_NUMERIC="de_DE.UTF-8" LC_TIME="de_DE.UTF-8" LC_COLLATE="de_DE.UTF-8" LC_MONETARY="de_DE.UTF-8" LC_MESSAGES="de_DE.UTF-8" LC_PAPER="de_DE.UTF-8" LC_NAME="de_DE.UTF-8" LC_ADDRESS="de_DE.UTF-8" LC_TELEPHONE="de_DE.UTF-8" LC_MEASUREMENT="de_DE.UTF-8" LC_IDENTIFICATION="de_DE.UTF-8" LC_ALL= - Keyboard layout: (switching to a different layout doesn't seem to have any effect) $ setxkbmap -query rules: evdev model: pc105 layout: de - Input devices: Logitech USB keyboard and mouse Please let me know if there is any other information I can provide.
screenshot with: " /usr/lib64/libexec/kscreenlocker_greet --testing" Also how many screens do you have?
Created attachment 111803 [details] Screencast of the bug in action Only one screen connected for now. I went ahead and recorded a screencast. Thought that might illustrate the issue better.
Hmm, can't reproduce in the released version of Kubuntu bionic. Can you?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!