Lockscreen: blank/black screen after suspend

heart1010 · 2015-10-16 19:24:00

Hi,

after I suspend my laptop (close it and opened it again) I normally got the lockscreen where I have to put my password. But now I get a totally blank/black screen, no unlock message/window, nothing cry
What happened?!

Thanks

hhh · 2015-10-16 20:39:40

Are you using the RC1 ISO and this suddenly happened, or what do you mean?

tknomanzr · 2015-10-17 00:36:29

I know ATI has a backlight issue in Jessie. It has to do with the way systemd sets the backlight up. It would be good to see the output of:

lspci | grep VGA

as well. If it is an ATI thing, I know how to fix it.

heart1010 · 2015-10-18 20:06:42

tknomanzr wrote:

I know ATI has a backlight issue in Jessie. It has to do with the way systemd sets the backlight up. It would be good to see the output of:
lspci | grep VGA 
as well. If it is an ATI thing, I know how to fix it.

No ATI....

$ lspci | grep VGA 
00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)

hhh wrote:

Are you using the RC1 ISO and this suddenly happened, or what do you mean?

I had the last crunchbang and upgraded to jessie->bunsen with the posted upgrade script from one member in the cb forum.
Yes, everything worked since weeks/month and then this happened.

From this black/blank screen I can go to tty console 1 for example with ctrl+alt+1 and go back to x session with ctrl+alt+7. When I do this I have for a few seconds this message on the screen https://goo.gl/photos/LXAr5zDD8VDGdh5GA (but I have no cursor, no mouse, I can't do anything)

Last edited by heart1010 (2015-10-18 20:08:00)

heart1010 · 2015-10-18 20:11:38

This thread looks very similar to my problem!? https://forums.bunsenlabs.org/viewtopic.php?id=338

Someone there suggested to post the output from systemd-inhibit, so here is my output for that command:

$ systemd-inhibit 
     Who: NetworkManager (UID 0/root, PID 606/NetworkManager)
    What: sleep
     Why: NetworkManager muss Netzwerke abschalten
    Mode: delay

     Who: xfce4-power-manager (UID 1000/heart, PID 1274/xfce4-power-man)
    What: handle-power-key:handle-suspend-key:handle-hibernate-key:handle-lid-switch
     Why: xfce4-power-manager handles these events
    Mode: block

damo · 2015-10-18 20:16:54

heart1010 wrote:

...
hhh wrote:
Are you using the RC1 ISO and this suddenly happened, or what do you mean?
I had the last crunchbang and upgraded to jessie->bunsen with the posted upgrade script from one member in the cb forum.
Yes, everything worked since weeks/month and then this happened.
...

Was it this script?

heart1010 · 2015-10-18 20:37:34

Yes, that was it...

damo · 2015-10-18 20:46:18

heart1010 wrote:

Yes, that was it...

Post #1 wrote:

Mod Edit:
This script is now obsolete as it does not include the BunsenLabs repositories.
To install BunsenLabs, use the live ISO image:
http://crunchbang.org/forums/viewtopic.php?id=40602
[ now continued on Bunsenlabs forums here ]
--HoaS
Mod Edit 2
This script is not approved by the BL team, and is unsupported.
It is known to have caused problems for some users.
--damo

**********************

heart1010 wrote:

Yes, everything worked since weeks/month and then this happened

Well it couldn't have happened if nothing changed, so what did you do before you noticed the problem? - Upgrade? Install something? Change a configuration somewhere?

Last edited by damo (2015-10-18 20:49:05)

damo · 2015-10-18 20:53:48

heart1010 wrote:

This thread looks very similar to my problem!? https://forums.bunsenlabs.org/viewtopic.php?id=338
Someone there suggested to post the output from systemd-inhibit, so here is my output for that command:
$ systemd-inhibit 
     Who: NetworkManager (UID 0/root, PID 606/NetworkManager)
    What: sleep
     Why: NetworkManager muss Netzwerke abschalten
    Mode: delay

     Who: xfce4-power-manager (UID 1000/heart, PID 1274/xfce4-power-man)
    What: handle-power-key:handle-suspend-key:handle-hibernate-key:handle-lid-switch
     Why: xfce4-power-manager handles these events
    Mode: block

Mode: block

From: http://www.freedesktop.org/software/sys … hibit.html

...
If "block" is used (the default), the lock prohibits any of the requested operations without time limit, and only privileged users may override it.

...but don't ask me where to go from there (I don't know if it is relevant or not 8o) HoaS will know

heart1010 · 2015-10-18 21:10:23

damo wrote:

heart1010 wrote:
Yes, everything worked since weeks/month and then this happened
Well it couldn't have happened if nothing changed, so what did you do before you noticed the problem? - Upgrade? Install something? Change a configuration somewhere?

Well, I only done the apt upgrades every few weeks...

Eventually something in this upgrade changed something?!

$ cat /var/log/apt/history.log

Start-Date: 2015-10-06  20:29:05
Commandline: apt upgrade
Install: laptop-detect:i386 (0.13.7, automatic)
Upgrade: bunsen-pipemenus:i386 (8.6-1, 8.6.3-1), bunsen-images:i386 (8.1-1, 8.2-1), libsasl2-2:i386 (2.1.26.dfsg1-13, 2.1.26.dfsg1-13+deb8u1), bunsen-welcome:i386 (8.2-1, 8.3-1), libsasl2-modules-db:i386 (2.1.26.dfsg1-13, 2.1.26.dfsg1-13+deb8u1), bunsen-common:i386 (8.1-1, 8.4-1), bunsen-meta-ssh:i386 (8.2-1, 8.3-1), libsasl2-modules:i386 (2.1.26.dfsg1-13, 2.1.26.dfsg1-13+deb8u1), bunsen-meta-vcs:i386 (8.2-1, 8.3-1), bunsen-themes:i386 (8.2-1, 8.3-1), google-chrome-stable:i386 (45.0.2454.99-1, 45.0.2454.101-1)
End-Date: 2015-10-06  20:30:03

ohnonot · 2015-10-19 05:50:19

damo wrote:

Was it this script?

s/h/e/it strikes back from the grave...
:sighs-in-exasperation:
[just a joke, never mind that]

the content of /etc/systemd/logind.conf might be of interest.
i suspect all entries are commented out there (=set to default values), but you could try setting some of those:

HandleSuspendKey=ignore
HandleHibernateKey=ignore
HandleLidSwitch=ignore

(probably not all together, one by one followed by reboots, i'd recommend)

ps:
i don't know what screenlocker bl uses, but some are deliberately designed to not display anything until you enter your password. tried that?

Head_on_a_Stick · 2015-10-19 06:48:58

ohnonot wrote:

the content of /etc/systemd/logind.conf might be of interest.
i suspect all entries are commented out there (=set to default values), but you could try setting some of those:
HandleSuspendKey=ignore
HandleHibernateKey=ignore
HandleLidSwitch=ignore
(probably not all together, one by one followed by reboots, i'd recommend)

The output of `systemd-inhibit` (post #5) shows that xfce4-power-manager is controlling these so altering that file will have no effect.

@OP: You can use xfce4-power-manager-settings to stop your laptop suspending on lid closure.

As ohnonot says, check that your backlight isn't set to zero or something silly like that.

From a black screen, does <Ctrl>+<Alt>+F2 switch you to a TTY?

You should consider re-installing, the unsupported upgrade technique may have b0rked your system in other ways.

What is the output of:

lsb_release -a
cat /etc/debian_version
cat /etc/apt/sources.list /etc/apt/sources.list.d/*

heart1010 · 2015-10-19 18:43:32

Head_on_a_Stick wrote:

@OP: You can use xfce4-power-manager-settings to stop your laptop suspending on lid closure.
As ohnonot says, check that your backlight isn't set to zero or something silly like that.

Ok checked... I get this warning on terminal when starting xfce4-power-manager-settings

$ xfce4-power-manager-settings

(xfce4-power-manager-settings:1810): xfce4-power-manager-settings-WARNING **: Schema "apps.light-locker" not found. Not configuring Light Locker.

Head_on_a_Stick wrote:

From a black screen, does <Ctrl>+<Alt>+F2 switch you to a TTY?

Yes, as said above... I can switch to the TTY terminals without any problem.

Head_on_a_Stick wrote:

What is the output of:

lsb_release -a
cat /etc/debian_version
cat /etc/apt/sources.list /etc/apt/sources.list.d/*

$ lsb_release -a
No LSB modules are available.
Distributor ID:	BunsenLabs
Description:	BunsenLabs GNU/Linux 8.2 (Hydrogen)
Release:	8.2
Codename:	Hydrogen
heart@laptop:~$ cat /etc/debian_version
8.2
heart@laptop:~$ cat /etc/apt/sources.list /etc/apt/sources.list.d/*
## CRUNCHBANG
## Compatible with Debian Wheezy, but use at your own risk.
#deb http://packages.crunchbang.org/waldorf waldorf main
##deb-src http://packages.crunchbang.org/waldorf waldorf main

## DEBIAN
deb http://http.debian.net/debian jessie  main contrib non-free
##deb-src http://http.debian.net/debian jessie main contrib non-free

## DEBIAN SECURITY
deb http://security.debian.org/ jessie/updates  main contrib non-free
##deb-src http://security.debian.org/ wheezy/updates main contrib non-free

## WINE MONO
## deb http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu precise main
#deb http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu trusty main

# added by bl-welcome
# Multimedia repository
deb http://www.deb-multimedia.org jessie main non-free

# TLP http://thinkwiki.de/TLP_-_Linux_Stromsparen#Debian
deb http://repo.linrunner.de/debian jessie main# http://crunchbang.org/forums/viewtopic.php?id=39993
deb http://pkg.bunsenlabs.org/debian bunsen-hydrogen main### THIS FILE IS AUTOMATICALLY CONFIGURED ###
# You may comment out this entry, but any other modifications may be lost.
deb http://dl.google.com/linux/chrome/deb/ stable main
# local debs
deb file:///var/local/debs ./

damo · 2015-10-19 18:53:37

Did you set `xfce4-power-manager-settings` to handle display power management (in the "Display" tab)?

heart1010 · 2015-10-19 19:04:58

you mean that one?

damo · 2015-10-19 19:11:13

Yes

johnraff · 2015-10-22 03:05:28

heart1010 wrote:

I get this warning on terminal when starting xfce4-power-manager-settings

$ xfce4-power-manager-settings

(xfce4-power-manager-settings:1810): xfce4-power-manager-settings-WARNING **: Schema "apps.light-locker" not found. Not configuring Light Locker.

This looks suspicious. Have you got light-locker installed?

heart1010 · 2015-10-23 19:39:25

johnraff wrote:

heart1010 wrote:
I get this warning on terminal when starting xfce4-power-manager-settings
$ xfce4-power-manager-settings

(xfce4-power-manager-settings:1810): xfce4-power-manager-settings-WARNING **: Schema "apps.light-locker" not found. Not configuring Light Locker.
This looks suspicious. Have you got light-locker installed?

Yes, it's installed.

$ dpkg -l|grep locker
ii  light-locker                                                1.4.0-2+b1                           i386         simple screen locker for lightDM display manager

I've read in the other thread that it's "normal" to have only a black screen and we should type in the password in this area but also nothing happens here when I type my password or write my password and hit enter, nothing (only the black screen)

Pieton · 2015-11-03 22:08:25

[To the moderators, feel free to create a new thread if you think it is more appropriate. Thanks]

Hi,

I was about to open a new thread when I found this one and I think that heart1010 and I face the (almost?) same issue for a couple of days: it does not always happen but when I suspend my laptop and I unlock it, a message appears during a few seconds (the same as posted on Message #4) requesting my password.

If I do enter my password, then the laptop is suspending again (and after I unlock it again, everything is going smooth).
Otherwise, the screen is going dark. Actually, I can still (hardly) see the message box. I tried to put my password but I did not manage to restore the screen luminosity. The only solution I found was rebooting.

Last but not least, as I still have the mouse working (contrary to heart1010), I am able to display more information about the issue. It comes from org.freedesktop.login1.suspend which tries to suspend the computer while it is not allowed.

Here is the output of systemd-inhibit:

$ systemd-inhibit
     Who: NetworkManager (UID 0/root, PID 595/NetworkManager)
    What: sleep
     Why: NetworkManager needs to turn off networks
    Mode: delay

     Who: xfce4-power-manager (UID 1000/mpuigt, PID 929/xfce4-power-man)
    What: handle-power-key:handle-suspend-key:handle-hibernate-key:handle-lid-switch
     Why: xfce4-power-manager handles these events
    Mode: block

2 inhibitors listed.

as far as I understand, xfce4-power-manager is in charge of suspending the laptop, which explains why org.freedesktop.login1.suspend is not allowed to do so. However, I do not understand why the latter also tries to suspend the laptop.

Any idea how to fix it? Thanks in advance.

hhh · 2015-11-03 23:21:37

it does not always happen but when I suspend my laptop and I unlock it, a message appears during a few seconds (the same as posted on Message #4) requesting my password.
If I do enter my password, then the laptop is suspending again (and after I unlock it again, everything is going smooth).

I saw this today on a fresh install of RC1 32 bit with no backports installed. I can't remember if I suspended just by closing the laptop lid or if I used the bl-exit window, but when I woke the laptop up an hour and a half later and entered my password, it suspended again.

I woke it again and entered my password and I was brought to the desktop with the backlight dimmed all the way down.

Now I'm trying to reproduce and I can't, but I'm only leaving it suspended for a minute.

I also think there's different backlight behavior if I just close the lid (suspend is the default RC1 behavior in that case), if I use bl-exit>suspend and leave the lid open or if I use bl-exit>suspend and then close the lid. I'll have to do some more testing.

We'll probably need to split these last 2 posts to there own thread or merge them with another existing light-locker thread, since the OP used a non-maintained script, but I'm leaving them here for now.

#1 2015-10-16 19:24:00

Lockscreen: blank/black screen after suspend

#2 2015-10-16 20:39:40

Re: Lockscreen: blank/black screen after suspend

#3 2015-10-17 00:36:29

Re: Lockscreen: blank/black screen after suspend

#4 2015-10-18 20:06:42

Re: Lockscreen: blank/black screen after suspend

#5 2015-10-18 20:11:38

Re: Lockscreen: blank/black screen after suspend

#6 2015-10-18 20:16:54

Re: Lockscreen: blank/black screen after suspend

#7 2015-10-18 20:37:34

Re: Lockscreen: blank/black screen after suspend

#8 2015-10-18 20:46:18

Re: Lockscreen: blank/black screen after suspend

#9 2015-10-18 20:53:48

Re: Lockscreen: blank/black screen after suspend

#10 2015-10-18 21:10:23

Re: Lockscreen: blank/black screen after suspend

#11 2015-10-19 05:50:19

Re: Lockscreen: blank/black screen after suspend

#12 2015-10-19 06:48:58

Re: Lockscreen: blank/black screen after suspend

#13 2015-10-19 18:43:32

Re: Lockscreen: blank/black screen after suspend

#14 2015-10-19 18:53:37

Re: Lockscreen: blank/black screen after suspend

#15 2015-10-19 19:04:58

Re: Lockscreen: blank/black screen after suspend

#16 2015-10-19 19:11:13

Re: Lockscreen: blank/black screen after suspend

#17 2015-10-22 03:05:28

Re: Lockscreen: blank/black screen after suspend

#18 2015-10-23 19:39:25

Re: Lockscreen: blank/black screen after suspend

#19 2015-11-03 22:08:25

Re: Lockscreen: blank/black screen after suspend

#20 2015-11-03 23:21:37

Re: Lockscreen: blank/black screen after suspend

Board footer