Okay, this is going to be a vague one... I have a password that I am able to enter very fast and since I am already using it for a long time, I (almost ;-) ) never fail to enter it correctly. Logging in at the console, logging in via SDDM or using sudo works basically every time. Unlocking the screen of my plasma desktop in a KVM/QXL/Spice VM fails almost all the time, however. At first I thought it's my fault for sure. But testing it over and over, it showed that I can enter this password correctly in console/sddm etc. as fast as I wish while I have to pay attention to enter it quite slowly (compared to the console - approx. 3 characters per second or less?) in the plasma screenlocker to have it accepted. I even changed the password to another similar complex one and tried it again after training it for some time. Same effect. I totally understand this is very vague... but perhaps you can simply try to reproduce it by setting a password (in my case 8 letters, upper and lower case, number and special character - I know there are better ones; this is historical and only used for my testing VMs ;-) ) and try to torture the screenlocker with it? Perhaps it's just an artifact of the input redirection over KVM/Spice? I couldn't test on a "real" machine yet, as I cannot switch to the 5-branch for now. If really nothing can be found, adding the "show password" button used in the native password dialogs could be probably helpful. Reproducible: Always Steps to Reproduce: 1. set complex password 2. learn to type it really fast 3. get rejected by screenlocker
> Perhaps it's just an artifact of the input redirection over KVM/Spice? That's very likely. It will also be difficult to debug. The only idea I have is to provide you a variant with showing the actual password, so that you can verify whether the entered text ends up correctly in the input field.
Sure. I'll install whatever you have ;-) (e-mail in German would be fine if you want to send sth)
Thanks for the report Olaf. I know it's been a while since this bug report was created but are you able to please test and confirm if this is still an issue? I've set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
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 mark the bug 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!
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!