Arch Linux

TheCoon

Member

Registered: 2016-05-10

Posts: 42

GDM unlocked when waking from suspend

Recently (past month) I have been facing a strange and scary issue with GNOME/GDM. (GNOME 3.26.2, Wayland)
Sometimes when my laptop wakes from suspend/sleep my user session and desktop is unlocked. Not visible for a moment, like here.
How can I solve this issue? At first I thought it might be due to a script I have in

/usr/lib/systemd/system-sleep/

which is responsible for running

systemctl restart NetworkManager.service

but the issue seems to persist even after disabling it (also, I see no reason why a script should affect GDM's basic security features).

robg

Member

Registered: 2015-03-05

Posts: 225

Re: GDM unlocked when waking from suspend

Next time this happens, please post (before doing anything else) the output of `journalctl -xe` and `dmesg`. To "rule out" GDM as an issue, if you use a different graphical login, does the issue also occur? And speaking of occurrence, how frequently does this happen? Can you identify any special circumstances in the case of an unlocked desktop after sleep?

TheCoon

Member

Registered: 2016-05-10

Posts: 42

Re: GDM unlocked when waking from suspend

Next time this happens, please post (before doing anything else) the output of `journalctl -xe` and `dmesg`.

Will do.

To "rule out" GDM as an issue, if you use a different graphical login, does the issue also occur? And speaking of occurrence, how frequently does this happen? Can you identify any special circumstances in the case of an unlocked desktop after sleep?

No special circumstances as far as I can tell, I'm keeping my eyes open for anything that might be the cause of it.
Since it's not really consistent, I still haven't tried a different graphical login because I'm trying to work out what causes it in the first place. I will, however, try to be more alert as to whether this occurs if I lock the screen before closing the lid or not. Maybe it's specific to closing the lid without manually locking first.

Similar issues have been reported here and here.