SUMMARY No possibility to login after screen lock on laptop when lid was opened without power supply (on battery). STEPS TO REPRODUCE 1. Boot Plasma, login there. 2. Setup lock screen when laptop lid is closed 3. Close a lid of a laptop 4. Wait till screen will be locked 5. Unplug power cable, laptop should work on battery 6. Wait and open a lid OBSERVED RESULT In this case there is no field for password, and it's impossible to login. EXPECTED RESULT I'd like to see a field for password and be able to login with no matter on power supply me or on battery. Operating System: openSUSE Tumbleweed 20250130 KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.1 Kernel Version: 6.13.0-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz Memory: 7,6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620
Hi - just to check: * Are you able to access a virtual terminal (ex. using Ctrl+Alt+F3) when this issue occurs? * Are any parts of the screen locker visible, such as the wallpaper or clock? * Does the mouse pointer still appear? * Does the issue only occur if the laptop is unplugged while the lid is closed? Thanks!
(In reply to John Kizer from comment #1) > * Are you able to access a virtual terminal (ex. using Ctrl+Alt+F3) when > this issue occurs? Yes. It works. > * Are any parts of the screen locker visible, such as the wallpaper or clock? I see only a wallpaper. But no one control. > * Does the mouse pointer still appear? Yes. > * Does the issue only occur if the laptop is unplugged while the lid is > closed? I'm unable to reproduce it without closing a lid.
Still here... Operating System: openSUSE Tumbleweed 20250211 KDE Plasma Version: 6.3.0 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.2 Kernel Version: 6.13.1-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz Memory: 7,6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620
A couple of other ideas to check into: Does the issue occur on Wayland as well as X11? If you trigger the issue and identify the time that it occurred, can you grab the system journal records from around that time and share them? For example, if the issue occurred at 4:30 PM today, you could use sudo journalctl --since="2025-02-13 16:29:00" --until="2025-02-13 16:31:00" to look at the surrounding couple of minutes and see if any major crashes, errors or warnings are being reported there.
Created attachment 178338 [details] systemctl log
> Does the issue occur on Wayland as well as X11? On Wayland the situation is worse even. It occurs and I unable access virtual terminal, I see text, blinking cursor, I can type, but it's not a terminal, nothing works. > If you trigger the issue and identify the time that it occurred, can you > grab the system journal records from around that time and share them? For > example, if the issue occurred at 4:30 PM today, you could use sudo > journalctl --since="2025-02-13 16:29:00" --until="2025-02-13 16:31:00" to > look at the surrounding couple of minutes and see if any major crashes, > errors or warnings are being reported there. I attached systemctl log. The keypoints: фев 14 07:37:04 localhost.localdomain systemd-logind[1040]: Lid closed. фев 14 07:37:27 localhost.localdomain login[3577]: pam_kwallet5(login:auth): pam_kwallet5: pam_sm_authenticate фев 14 07:37:45 localhost.localdomain sudo[3626]: igor : TTY=tty3 ; PWD=/home/igor ; USER=root ; COMMAND=/usr/sbin/reboot One more thing - unmasking sleep.target doesn't solve anything...
These line are red: фев 14 07:37:04 localhost.localdomain kscreenlocker_greet[3430]: PAM unable to dlopen(/usr/lib64/security/pam_fprintd.so): /usr/lib64/security/pam_fprintd.so: cannot open shared object file: No such file or directory фев 14 07:37:04 localhost.localdomain kscreenlocker_greet[3430]: PAM adding faulty module: /usr/lib64/security/pam_fprintd.so фев 14 07:37:04 localhost.localdomain kscreenlocker_greet[3430]: PAM unable to dlopen(/usr/lib64/security/pam_pkcs11.so): /usr/lib64/security/pam_pkcs11.so: cannot open shared object file: No such file or directory фев 14 07:37:04 localhost.localdomain kscreenlocker_greet[3430]: PAM adding faulty module: /usr/lib64/security/pam_pkcs11.so And: фев 14 07:37:19 localhost.localdomain systemd-logind[1040]: Failed to execute suspend operation: Unit sleep.target is masked.
Created attachment 178339 [details] systemctl log without unplugging power cable
I added systemctl log without unplugging power cable.
(In reply to Igor Mironchik from comment #7) > These line are red: > > фев 14 07:37:04 localhost.localdomain kscreenlocker_greet[3430]: PAM unable > to dlopen(/usr/lib64/security/pam_fprintd.so): > /usr/lib64/security/pam_fprintd.so: cannot open shared object file: No such > file or directory > фев 14 07:37:04 localhost.localdomain kscreenlocker_greet[3430]: PAM adding > faulty module: /usr/lib64/security/pam_fprintd.so > фев 14 07:37:04 localhost.localdomain kscreenlocker_greet[3430]: PAM unable > to dlopen(/usr/lib64/security/pam_pkcs11.so): > /usr/lib64/security/pam_pkcs11.so: cannot open shared object file: No such > file or directory > фев 14 07:37:04 localhost.localdomain kscreenlocker_greet[3430]: PAM adding > faulty module: /usr/lib64/security/pam_pkcs11.so These are almost certainly the problem. They're indicative of a packaging, updating, or configuration issue on the system. If it's still reproducible for you, I'd recommend asking your distro's packagers or developers for help with it. Thanks!