desktop unlocked after resume

[igordovgaluk]

desktop unlocked for a few seconds after resume then locks.
cinnamon 2.4.8, version Linux Mint 17.1 (with all level 3 and above updates), kernel 3.13.0-37-generic

[igordovgaluk]

similar issue http://forums.linuxmint.com/viewtopic.php?f=49&t=197000

[dalcde]

Do you happen to have popup menus open before locking?

[linux-modder]

@dalcde, @op, look at the Main Settings menu Is 'Lock before Sleep' enabled if not enable it and retry. with enabled this is no longer an issue on Fedora Cinnamon also in xscreensaver there is setting to blank out on / return form lock could also try those.

[rapgro]

Reproducible for me. After a resume from standby, the screen gets locked but after some long delay. so the evil user is able to enter some commands still. IMHO that's a security issue.
RedHat security response team requests that the screen gets locked immediately on an standby|suspend event.
https://bugzilla.redhat.com/show_bug.cgi?id=614608
https://bugzilla.redhat.com/show_bug.cgi?id=632978
https://bugzilla.redhat.com/show_bug.cgi?id=1225229#c11

[shnplr]

happens for me on 2.6.13 LM 17.2
i can usually start my web browser (i.e. click a panel shortcut) before the screen locks. I have never been able to do more than one thing before it locks. When I unlock the browser has indeed been started.

[ion201]

Issue still in Cinnamon 2.8.6

Related issues:
#3060
#4601

As far as I can tell, the screen is not actually locking on suspend, but instead locking after waking up. I'm not experiencing this on my desktop, but am on my dual-core pentium laptop when manually suspending or closing the lid. The time it is unlocked for is ~1-2 seconds at most. Perhaps the issue is present but not noticeable on faster hardware?

[igordovgaluk]

Perhaps ... my i5 is a slow hardware

[cindyq]

Also seeing this on kernel 4.2, Cinnamon - 2.6.13 -- on resume, the desktop contents flash for a couple of seconds then the lock screen shows up

[gerow]

I also saw an interesting behavior similar to what @cabellicar123 describes in #2466 (comment) where a user's setting for automatic screen lock and sutomatic suspend were the same value.

This causes the screensaver to lock before the suspend occurs. When the user un-suspends and unlocks the screen the lock triggered by the suspend then happens later and the user must re-unlock the screen.

Attached are logs from cinnamon-screensaver (version 2.6.4) exhibiting this behavior. I'm not sure why gs_manager_set_lock_active gets called twice before suspend, but may be a red herring since I see it get called twice when I just call the D-Bus method to lock the screen anyway. The gs_manager_set_lock_active call later after the suspend is the interesting one that appears to be the actual issue.
cinnamon-screensaver.txt

[Vahan86]

@igordovgaluk, does this issue still occur in Cinnamon 3.2?

[igordovgaluk]

@Vahan86
yes, for few seconds after resume the desktop is accessible.
then it is locked.
Cinnamon 3.2.7 (Mint 18.1)

[steve--d]

I think this is a race condition, seeing as systemd likes to do everything in parallel. I found giving a bit of time for other processes to run when sleep is triggered helped, haven't seen this problem in two days after:

# cat /usr/lib/systemd/system-sleep/activate-screensaver.sh 
#!/bin/bash

if [ $1 == "pre" ]
then
	sleep 2
fi

Fedora 25, Dell XPS 13 9350

[igordovgaluk]

i would ask to review Lock and Suspend. Very often it takes few seconds to lock/suspend.
looks like Cinnamon issue. MATE on same system works perfectly fine (suspends in a second).