Closed johnraff closed 8 years ago
Suspend != lock screen. For example, if you are using xscreensaver and set it to lock the screen after N minutes, suspend, and wake up before the N-minute interval has passed, the screen is unlocked. Of course if the locker is called twice for whatever reason, that could be a problem.
That poster reported that the screen was locked automatically by light-locker when going into suspend.
Of course that's a separate function - in fact xfce4-power-manager has an option "Lock screen when system is going for sleep", so is presumably talking directly to light-locker in that case.
So additionally activating bl-lock from suspend in bl-exit is something to remove, right?
If that's the case, I'd say yes.
I'd say yes if that's the case.
On 11 January 2016 14:02:25 GMT+09:00, John Crawley notifications@github.com wrote:
That poster reported that the screen was locked automatically by light-locker when going into suspend.
Of course that's a separate function - in fact xfce4-power-manager has an option "Lock screen when system is going for sleep", so is presumably talking directly to light-locker in that case.
So additionally activating bl-lock from suspend in bl-exit is something to remove, right?
Reply to this email directly or view it on GitHub: https://github.com/BunsenLabs/bunsen-utilities/issues/27#issuecomment-170433231
bl-exit
See this forum post: https://forums.bunsenlabs.org/viewtopic.php?pid=14909#p14909
Is the call to bl-lock that comes with the suspend action on line 109 superfluous? Could it be the cause of some of the blackscreen issues people have been getting?