No "card" to type in password after suspend [$50]

[yeboahnanaosei]

Prerequisites

• [x] I have searched open and closed issues for duplicates.

Describe the bug

Sometimes after waking the pc from suspend, all I get is the gray background. The "card" which shows my desktop wallpaper, my avatar and the password input box do not show up. All I get is the gray background with the wifi, bluetooth, battery and power indicators at the top right. That is all I get. No "login as guest button, no time and date, no avatar, no password input box, no "card" in the middle. I have to reboot the system to be able to login.

To Reproduce

Steps to reproduce the behavior:

1. Suspend the PC
2. Wake the pc up
3. No box to enter password and login

Expected behavior

I expect to see the "card" with my avatar, and password input box in order to enter my password and login

Platform Information

Please check what applies:

• [x] I'm using the latest released stable version

---

There is a $50 open bounty on this issue. Add to the bounty at Bountysource.

[joedborg]

I'm seeing this too, especially when using an external display. Really stressful as I have to reboot to get anything back.

[joedborg]

To prove how stressful this is, I've added a bounty :) https://www.bountysource.com/issues/87407064-no-card-to-type-in-password-after-suspend

[joedborg]

After seeing this again it's worth saying that, for me, I don't get the clock either. It's just the grey background, nothing else is presented.

If there's a way I can grab logs post forced reboot, to help with this, please let me know.

[JonathanPrecise]

As a workaround, I remember to save all data before locking, and when this happens, I can Ctrl+Alt+F1, login, and run sudo systemctl restart lightdm, which logs me out in the process and brings me to the login page. What logs should I send (redacted) in order to further debug this?

EDIT: @yeboahnanaosei reports having issues with the dock after applying the workaround. This never happened to me, so YMMV.

[joedborg]

I know everyone's busy, but this is incredibly day breaking for me. For what ever reason, it seems to have increased in occurrences and, at a guess, I'd say it's happening 50% of times my screen locks (and display goes to sleep).

I don't know if this is the cause, or even a clue but

May 20 14:04:01 mia lightdm[2273]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
May 20 14:04:01 mia lightdm[2273]: PAM adding faulty module: pam_kwallet.so
May 20 14:04:01 mia lightdm[2273]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
May 20 14:04:01 mia lightdm[2273]: PAM adding faulty module: pam_kwallet5.so

...is splattered all over the LightDM.

[yeboahnanaosei]

@JonathanPrecise workaround works. However, there is this weird behaviour I've noticed when you eventually log back in. Every click on an icon on the dock launches a new instance of the application you clicked on.

Example: After managing to log back in using @JonathanPrecise approach , I click on the files icon on the dock to open files which opens successfully. Later when I again go to click on the files icon on the dock to minimize, instead of minimizing, a new instance or window of files gets opened.

[JonathanPrecise]

Other workarounds I have found (with their respective drawbacks):

• If you're stuck in this situation and can't afford to lose unsaved work, CTRL+ALT+F1, login, and kill the lock screen program light-locker (you can do this by running killall light-locker, or manually getting the locker process id with ps ax | grep light-locker and killing it with kill _<pid>_). Do note that doing so disables locking the screen again for the remainder of the session, and you possibly need to reboot in order for the login screen to show up properly again.

• If this becomes annoying, you can uninstall light-locker and install another locker like xscreensaver. However it must be added as an startup application in Settings (e.g. Custom command: xscreensaver -no-splash). Aditionally you must remap the keyboard shortcut SUPER+L to lock the screen with you just-installed program (e.g. xscreensaver-command -lock). If you modified the PAM files for LightDM (e.g. for adding U2F/Yubico), make sure to modify them for your new screen lock as necessary (e.g. /etc/pam.d/xscreensaver). Note that this workaround will uninstall the "Security & Privacy" switchboard in Settings (which can be reinstalled using my fork), will not allow you to lock the screen with the wingpanel power menu (hence why you set the keyboard shortcut), and will probably look ugly (or at least not fit in with the elementary OS style).

@yeboahnanaosei That's weird. I never had this happen to me with any of my workarounds, so I have no idea how to help you there.

[joedborg]

I've "gotten round this" by turning off all the suspend triggers and timers for the time being.

I see there's a newer version of light-locker. I'll try installing it and seeing if it helps.

[kmandarin-orange]

I'd like to confirm this still persists in elementary OS 6 for me, often after automatic suspends on my laptop. Is anyone else still experiencing this?