https://bugs.kde.org/show_bug.cgi?id=456210
--- Comment #43 from ratijas <m...@ratijas.tk> --- Can reproduce. After normal password prompt a useless lonely "Unlock" buttons shows up, like the one for password-less users. Clicking it sometimes terminates the lock screen app and thus returns to the desktop, but sometimes does nothing. Build-in laptop screen + external HDMI 4K@30FPS monitor. Both with testing and real screen locking. No fingerprints, no fprint, only password. Workaround is to run loginctl unlock-session from TTY2 (Ctrl+Alt+F2 or +F8 depending on your distro). Operating System: Arch Linux KDE: git master Qt Version: 5.15.5 Kernel Version: 5.18.16-arch1-1 (64-bit) Graphics Platform: X11 I'm not getting EDID logs in journalctl, but I do get this line on start of kscreenlocker_greet: > kscreenlocker_greet[8858]: pam_systemd_home(kde:auth): systemd-homed is > not available: > Unit dbus-org.freedesktop.home1.service not found. I'm also getting these cosmetic error messages after every failed attempt, even though I can't find any instance where it is defined as "read-only": > > file:///usr/local/kde/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml:75: > TypeError: Cannot assign to read-only property "showPassword" Consistent observation: when entering a correct password one screen first, the following dummy "Unlock" button terminates the screen locker and returns me to the desktop. But if I enter the password on another screen first — it won't unlock, it'll do nothing. It doesn't matter when do you do next: only first correct password attempt seems to matter. "One" and "another" screens are randomly chosen laptop's built-in and external HDMI: in other words it would either work on a first try because you guessed the screen correctly, or it won't work no matter how many times you click. So far I'm more lucky with the "one" being the built-in laptop's one. Basically, the same logs as posted above. The only difference when it's about to enter the unlockable state (i.e. I guessed the screen wrong) is an extra `kscreenlocker_greet: Start auth` line after `kscreenlocker_greet: Auth done RC 0`. -- You are receiving this mail because: You are watching all bug changes.
