| Summary: | Enter button clicks itself on lockscreen leaving me unable to type my password | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Ángel Navarro <jesusnavarrojr188> |
| Component: | Screen locking | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED DOWNSTREAM | ||
| Severity: | major | CC: | akselmo, daninshed, edmund, kde, kdedev, nate |
| Priority: | NOR | Keywords: | regression |
| Version First Reported In: | 6.4.80 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Plasma trying to auto-unlock itself with no password | ||
Is this on a system with no password? Have you set up PAM according to https://community.kde.org/Distributions/Packaging_Recommendations#PAM_configuration > Is this on a system with no password? No, I do have a password which the screen locker won't let me type in. SDDM works fine, only the screenlocker does that > Have you set up PAM according to > https://community.kde.org/Distributions/Packaging_Recommendations#PAM_configuration This almost completely locks me out of the computer with SDDM failing every time with the "Failed login" message like when I mistype the password. Glad I made a snapshot right before that which I restored from tty It's hard to be sure, but these symptoms point to some serious misconfigurations on your machine. I would recommend consulting Arch-specific resources for guidance on how to proceed. Please don't imply that this is a pebkac error when I did not touch the PAM files for anything else than to autounlock the wallet. I just downgraded from Plasma dev git packages back to "normal" (just in case you did not read it) release packages and the screen locker works just fine and is not broken anymore, so it's clearly an upstream issue and not something in my end. I'll hold on here for a while but I will keep the old snapshot in case you need some more logs :D Hmm, ok. Is it 100% reproducible for you still with a later version of git master? I don't see this in my built-from-source kscreenlocker on top of Fedora KDE 42, or on KDE Linux which builds all KDE stuff from source on top of an Arch-based base OS. I've just rebuilt the entire Plasma ecosystem git (everything, I even came from a fresh root with not even the testing repos, I built with the) from the ground and this is 100% reproducible. In my old git build it also had styling issues like the profile picture was squared with no borders but it seems not to be like that now. The first time I built everything with testing repos enabled, this time they are disable and the issue is completely reproducible from both, I have to unlock it from tty with loginctl. Weird that you can reproduce it 100% and for me it's 0%. I still suspect underlying differences in the host system or configuration could be at play here, but regardless, we'll need to figure out what's the reproducible trigger for it. I can't repro this either.. Just asking few clarifications, unsure if related or not: - What keyboard layout do you have? - Do you have a controller or similar device plugged in to the PC? - Does this stop when you unplug keyboard/mouse/controllers? - Does this happen when you wait for locking to happen, or when you lock by pressing shortcut? Or both? - dvorak-la but it doesn't really matter the keyboard as far as I can tell - I sometimes plug one but this happens way before I bought it though - It is a laptop so I can't unplug the keyboard and the trackpad... but I do have a touch screen - On both, the problem is waking up the screen in any way while being locked I can't further test because I'm on latest release right now and I don't really have spare time to recompile everything again (In reply to Ángel Navarro from comment #9) > but I do have a touch screen Does poking at the touch screen in lockscreen mode do anything either? (In reply to Akseli Lahtinen from comment #10) > (In reply to Ángel Navarro from comment #9) > > but I do have a touch screen > > Does poking at the touch screen in lockscreen mode do anything either? No, it doesn't work as well. I'm locked in until I'm forced to switch to TTY and manually loginctl unlock-session N. Weirdly, this doesn't happen on released versions but only on Git master compilations. Fixed. Turns out this is a downstream issue on `plasma-login-manager-git`. I can reproduce this on Archlinux. Without the `kde` file, `KScreenLocker` cannot authenticate and throws errors like this repeatedly: `kscreenlocker_greet[9241]: pam_warn(kde:auth): function=pam_sm_authenticate … service=[kde]` This might have been interpreted by the OP as "Enter being hit repeatedly", as the screen has a visible refresh, and shows something to the line of "Authentication failed". Questions: 1. Is PAM the only authentication way? Most OS's (Archlinux, Debian, FreeBSD) appear to provide a PAM service file called `kde`. Fedora, on the other hand, does not; which leads me to the next question: 2. Is there a way that `KScreenLocker` will work with, say, just `systemd-logind`, if configured correctly - and then PAM is involved via `logind`, rather than directly via a PAM service file called `kde`? Thank you for your time and sharing of knowledge, to further investigate this! Okay, I installed Fedora, and found out it does have a PAM service file `kde`! After digging around, I found it was installed via the package `plasma-workspace`. I guess that answers that; and perhaps, probably, my previous question 2 then also will turn out to be: No alternative ways to authenticate. The issue of OP was then, indeed, that downstream (in this case the maintainer of the package `kscreenlocker-git` in the Archlinux User Repository (AUR) failed to provide a PAM service file. This has been pointed out, and will be fixed soon, we hope. Thank you all! |
Created attachment 183222 [details] Plasma trying to auto-unlock itself with no password SUMMARY When I lock the screen and try to unlock it afterwards, the lockscreen acts as if I was pressing the Enter key repeatedly and after 3 tries it locks me out. I can't type my password to unlock it normally. STEPS TO REPRODUCE 1. Lock the screen. 2. Try to unlock it. OBSERVED RESULT Unlock event is automatically triggered EXPECTED RESULT To be able to type the password and unlock it properly SOFTWARE/OS VERSIONS SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.5 Dev (6.4.80 git master) KDE Frameworks Version: 25.07.80 Qt Version: 6.10.0 Beta ADDITIONAL INFORMATION I've just installed the whole Plasma Dev stack on my Arch system.