Lockscreen: blank/black screen after suspend

tknomanzr · 2015-11-04 00:30:25

Another possibly related issue I have been having on the test install I setup while testing sound, is when I suspend, the network gets suspended also. However, when I resume from suspend, the network does not come back up. A check through systemctl shows the suspend state as still active, like it is not correctly updating somehow. I don't think it is supposed to be active one it resumes from suspend. Also, shutting down and restarting services does not work. The only thing that helps me is a forced reboot.

Note, the lock functionality works as expected but the resume from suspend functionality does not. This is a new issue introduced with RC1. Resume and Suspend states are not an issue I have ever experienced with that particular hardware. If you need/want more info I will try to dig it up for you. I have not really dug that deep into it since my main focus at the time was on sound issues.

Last edited by tknomanzr (2015-11-04 00:31:09)

hhh · 2015-11-04 01:06:54

nm-applet reconnects for after suspend w/out issue.

heart1010 · 2015-11-19 19:40:27

Anything new to this one... I still have the mentioned problem after lock out/suspend that I only have a black screen.

What I do now is

Ctrl+Alt+F1
login
killall light-locker
logout
Ctrl+Alt+F7

...then I have my desktop back where I left it.

But this is really annoying. So can I check some config or sth. else in order to get this working finally?!

light-locker config?! Or what can cause this?

Thanks

ohnonot · 2015-11-20 07:19:22

try disabling light-locker, maybe it'll help or shed more light on the issue.

heart1010 · 2015-11-26 19:17:08

ohnonot wrote:

try disabling light-locker, maybe it'll help or shed more light on the issue.

I disabled light-locker, thanks for that tip. Now I can use my laptop again without that black screen (when there should be a "lock screen".

So light-locker is the cause of that.

Can we go deeper into bunsen light-locker config files and check if my files are correct?!

helix169 · 2016-01-10 22:58:38

Hi,

I've encounterd the same problem after lock out/suspend that I only have a black screen, like heart1010.
I've found using the bl-exit script at command line generates this strange behaviour also.

Since this python script calls dbus for suspending , I tried following command in a terminal:

dbus-send --print-reply --system  \
--dest=org.freedesktop.login1 \
/org/freedesktop/login1 \
org.freedesktop.login1.Manager.Suspend boolean:true

... and voilà: My computer does suspending and resuming was no problem: My screen was locked...by light-locker of course. After typing my username/password the desktop restored normal... with no hanger in network-applet, sorry for my bad english. I tried this very often without one error, so I wondered why the bl-exit script does not.

Maybe I've found a solution, it works for me so far:
In line 108 of the bl-exit script I commented out the call of bl-lock

def suspend():
#call("bl-lock")
send_dbus("Suspend")

Guess what? Suspending via menu or via bl-exit is running again just as it should.

johnraff · 2016-01-11 04:43:22

^this is interesting. So light-locker is called automatically when suspending, and it looks as if the call from bl-exit to bl-lock (which also calls 'light-locker-command -l') might be causing problems.

Thank you for the hint!

johnraff · 2016-01-17 07:49:47

This fix has now been applied in version 8.6.2-1 of bunsen-utilities, which should be available on the repositories before long.

Thanks again @helix169 for finding it.

AL13N · 2016-01-17 13:54:11

@helix169: Thank You.

heart1010 · 2016-01-18 20:42:35

I've updated the package

$ sudo apt-cache policy bunsen-utilities
bunsen-utilities:
  Installiert:           8.6.2-1
  Installationskandidat: 8.6.2-1
  Versionstabelle:
 *** 8.6.2-1 0
        500 http://pkg.bunsenlabs.org/debian/ bunsen-hydrogen/main i386 Packages
        100 /var/lib/dpkg/status
     0.3-13~git 0
        500 file:/var/local/debs/ ./ Packages

and restarted my laptop.

But again a black screen when I do "bl-lock" or close the laptop and open it again.

What I'm doing wrong!?

xaos52 · 2016-01-19 09:15:49

try

sudo apt-get update && sudo apt-get upgrade

Edit:
IGNORE THE ABOVE
You have the latest version of bunsen-utilities.
Your problem probably differs from the one solved by it.

xaos52 · 2016-01-19 10:20:49

@heart1010

Apparently there is a long list of problems concerning light-locker. See this list and there still isn't a solution for all cases.
Can you go over the list (perhaps from bottom to top, because it is looooong) and see if
1.the situation described applies to you
2. try any proposed solutions and report back to us

Thanks

heart1010 · 2016-01-19 10:31:08

Ok, will try a few "solutions" and report back here....

Enable "lock on suspend" in Light Locker settings

Where can I find "light locker settings" in bunsenlabs?

Last edited by heart1010 (2016-01-19 10:31:51)

xaos52 · 2016-01-19 10:45:27

I don't think it is there?
Let me install Xubuntu and I will find out and report back.

hhh · 2016-01-19 13:51:16

heart1010 wrote:

Where can I find "light locker settings" in bunsenlabs?

It's not in Debian. You can backport it from Ubuntu, but light-locker only has a few options so it's easy to just edit the light-locker.desktop autostart file. See man light-locker.

heart1010 · 2016-01-19 18:46:04

Ok, light at the end of the tunnel

https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1259339/comments/30 wrote:

One simple work-around I found is to do the following:
1. Disable the check box to lock the screen before suspending in xfce-power-manager settings.
2. Enable "lock on suspend" in Light Locker settings
Now the screen is properly locked when resuming from suspend *and* screen power is restored after logging in.
Tested this on two Xubuntu 14.04 systems, seems to work.

Tested this and bl-lock command is working!!!!

I disabled the checkbox mentioned in 1) above and started light-locker in terminal with

$ light-locker --lock-on-suspend &

Now "bl-lock" is working!

So do I only have to edit the autostart file from light-locker (/etc/xdg/autostart/light-locker.desktop) so that the Exec line looks like:

Exec=light-locker --lock-on-suspend

?

KrunchTime · 2016-01-20 00:46:32

johnraff wrote:

^this is interesting. So light-locker is called automatically when suspending, and it looks as if the call from bl-exit to bl-lock (which also calls 'light-locker-command -l') might be causing problems.
Thank you for the hint!

johnraff wrote:

This fix has now been applied in version 8.6.2-1 of bunsen-utilities, which should be available on the repositories before long.
Thanks again @helix169 for finding it.

Except that now the fix appears to have created an issue with my setups. I use xscreensaver (I have to modify bl-lock after every bunsen-utilities update) and coming out of suspend used to prompt me for a password from xscreensaver, but recently (this week) that no longer works. Coming out of suspend just brings me to my desktop. I would very much prefer to be required to enter a password to access my systems after coming out of suspend so that someone walking by can't just get on my computer.

Care to describe the changes made so that I can undo them on my end and know what to do for future updates?

Edit: One other item to note: I do not have xfce4-power-manager installed on my desktop.

Last edited by KrunchTime (2016-01-20 05:41:01)

johnraff · 2016-01-20 06:14:27

Clearly the old code, inherited from CrunchBang, was necessary when using xscreensaver, while causing problems with light-locker. Anyway, for people who use xscreensaver it's a one-liner. In /usr/bin/bl-exit, find line 108 'def suspend():' and add this line below it:
call("bl-lock")
so the whole block should look like this:

def suspend():
    call("bl-lock")
    send_dbus("Suspend")

KrunchTime wrote:

I use xscreensaver (I have to modify bl-lock after every bunsen-utilities update) ...

This is unfortunate, because there will no doubt be more upgrades to bunsen-utilities before long, and now you'll have to edit bl-exit too. You could make local copies of bl-exit and bl-lock in ~/bin and as long as $HOME/bin comes first in your $PATH then they will take priority over the versions in /usr/bin. I haven't tried this but it should work, and save you that repeated re-editing.

johnraff · 2016-01-20 06:18:43

heart1010 wrote:

So do I only have to edit the autostart file from light-locker (/etc/xdg/autostart/light-locker.desktop) so that the Exec line looks like:
Exec=light-locker --lock-on-suspend
?

That should work, but it will be overwritten if light-locker is upgraded or reinstalled. You could copy /etc/xdg/autostart/light-locker.desktop to ~/.config/autostart and edit your local copy. That will not be changed by the system.

KrunchTime · 2016-01-20 07:49:18

johnraff wrote:

Clearly the old code, inherited from CrunchBang, was necessary when using xscreensaver, while causing problems with light-locker. Anyway, for people who use xscreensaver it's a one-liner. In /usr/bin/bl-exit, find line 108 'def suspend():' and add this line below it:
call("bl-lock")
so the whole block should look like this:
def suspend():
    call("bl-lock")
    send_dbus("Suspend")
KrunchTime wrote:
I use xscreensaver (I have to modify bl-lock after every bunsen-utilities update) ...
This is unfortunate, because there will no doubt be more upgrades to bunsen-utilities before long, and now you'll have to edit bl-exit too. You could make local copies of bl-exit and bl-lock in ~/bin and as long as $HOME/bin comes first in your $PATH then they will take priority over the versions in /usr/bin. I haven't tried this but it should work, and save you that repeated re-editing.

Big thank you!

Last edited by KrunchTime (2016-01-20 07:49:32)

#21 2015-11-04 00:30:25

Re: Lockscreen: blank/black screen after suspend

#22 2015-11-04 01:06:54

Re: Lockscreen: blank/black screen after suspend

#23 2015-11-19 19:40:27

Re: Lockscreen: blank/black screen after suspend

#24 2015-11-20 07:19:22

Re: Lockscreen: blank/black screen after suspend

#25 2015-11-26 19:17:08

Re: Lockscreen: blank/black screen after suspend

#26 2016-01-10 22:58:38

Re: Lockscreen: blank/black screen after suspend

#27 2016-01-11 04:43:22

Re: Lockscreen: blank/black screen after suspend

#28 2016-01-17 07:49:47

Re: Lockscreen: blank/black screen after suspend

#29 2016-01-17 13:54:11

Re: Lockscreen: blank/black screen after suspend

#30 2016-01-18 20:42:35

Re: Lockscreen: blank/black screen after suspend

#31 2016-01-19 09:15:49

Re: Lockscreen: blank/black screen after suspend

#32 2016-01-19 10:20:49

Re: Lockscreen: blank/black screen after suspend

#33 2016-01-19 10:31:08

Re: Lockscreen: blank/black screen after suspend

#34 2016-01-19 10:45:27

Re: Lockscreen: blank/black screen after suspend

#35 2016-01-19 13:51:16

Re: Lockscreen: blank/black screen after suspend

#36 2016-01-19 18:46:04

Re: Lockscreen: blank/black screen after suspend

#37 2016-01-20 00:46:32

Re: Lockscreen: blank/black screen after suspend

#38 2016-01-20 06:14:27

Re: Lockscreen: blank/black screen after suspend

#39 2016-01-20 06:18:43

Re: Lockscreen: blank/black screen after suspend

#40 2016-01-20 07:49:18

Re: Lockscreen: blank/black screen after suspend

Board footer