*** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY When resuming from suspend, I type my password and press enter, then have to press enter again because an "unlock" button appears first, adding unnecessary friction to the user experience. It does not occur when just locking the screen, only after resuming from suspend. STEPS TO REPRODUCE 1. Suspend system and then resume it 2. Type password and press enter 3. Observe unnecessary "unlock" button OBSERVED RESULT Unnecessary "unlock" button adds extra friction for seemingly no reason EXPECTED RESULT Typing password and pressing enter logs you in, just like if you simply lock the screen without suspending. You wouldn't type your password and press enter if you didn't want to log back in, right? :) SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.4-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 3800X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 570 Series Manufacturer: Gigabyte Technology Co., Ltd. Product Name: X570 AORUS MASTER System Version: -CF ADDITIONAL INFORMATION
I have exactly the same issue.
I have the same issue except I can't get back into the machine -- After sleep, sometimes unlock screen only displays [Unlock?] button. Click on it or hit enter and it does nothing -- wait and [Unlock?] disappears just leaving background. Let it sit there and display blacks out. Hit [Shift] or [Return] and it displays [Unlock?] button again, but won't let you unlock your machine.\ Rinse, wash, repeat. Only way to avoid rebooting is go to TTY3 and do: $ loginctl unlock-sessions then return to TTY1 and continue working. S/W: Garuda Linux (Arch) KDE Plasma ver: 6.0.3 KDE Frameworks: 6.0.0 QT Version: 6.7.0 Kernel Version: 6.8.5-zen-1-zen (64-bit) Graphics Platform: Wayland H/W Processors: 8 x 11th Gen Intel Core i7-1165G7 @ 2.80GHz RAM Memory: 32 GB Graphics: Mesa Intel Xe Manufacturer: Framework
Happens to me too, logging in works, but sometimes it displays this unnecessary unlock button after typing the password and confirming. This only happens when resuming from suspend, it doesn't happen if locking the screen without suspending (with Meta+L for example). The system needs to stay suspended for more than 10 seconds, otherwise the unlock button is not shown after entering the correct password. Also it doesn't seems to be related to the say you confirm the password (with Enter key or with the button on the screen), just to how much time it passes. S/W: OS: Arch Linux KDE Plasma ver: 6.0.4 KDE Frameworks: 6.1.0 QT Version: 6.7.0 Kernel Version: 6.8.7-arch1-1 (64 bit) Graphics Platform: Wayland H/W Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor RAM Memory: 32 GB Graphics: AMD Radeon RX 6600 Manufacturer: ASUS
Hello I confirm also having this issue. Not blocking but annoying. Here is my system info: Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.7-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 5700 XT Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7C91 System Version: 2.0