No gnome-screensaver process (but screen still goes blank after a while).

[fetchinson]

Hi folks, I'm not using gnome or kde only the sawfish window manager stand alone. But I do launch gnome-settings-daemon for all the goodies it provides. Now my question is that I don't know what causes my laptop screen to go blank after a while. There is no gnome-screensaver process or anything like *screen* but nevertheless screensaving works very well.

Is this a dbus thing?

[brianblaze]

Sadly I am not too familiar with kde but even gnome does not have screen savers but I too have the same weirdness which I have never really bothered to worry about but my screen should turn off after an hour but it does after like 15 minutes... in my system settings -> screen it says it should tunr off after 1 hour... Probably something similar.... maybe not

[sidebrnz]

Gnome-screensaver should only be used with Gnome, but it will try to take over any time it's installed. Fetchinson, you should check to see if xscreensaver is installed and if so, how it's set. The best way to do this is to run this in a terminal, not as root:

xscreensaver-demo

If bash can't find it, you don't have xscreensaver installed. If it runs, it may be set to act only as a screen blanker. Also, it occurs to me that you might be using the wrong command to look for a screen saver.

ps aux | grep *screen*

returns only the grep command on my box, but

ps aux | grep screen

also shows that xscreensaver is running. HTH, HAND.

[fetchinson]

Originally Posted by sidebrnz

Gnome-screensaver should only be used with Gnome, but it will try to take over any time it's installed. Fetchinson, you should check to see if xscreensaver is installed and if so, how it's set.

No, xscreensaver is not installed so it is not running.

And whatever runs is actuallly only acting as screen blanker as you said, so after a while the screen goes simply blank. And then when it has to it wakes up as it should so it functions perfectly well. I just can't find what process it is

Also, it occurs to me that you might be using the wrong command to look for a screen saver.

ps aux | grep *screen*

returns only the grep command on my box, but

ps aux | grep screen

Sure, I do the former "ps aux | grep screen" so I'm definitely sure that nothing of the sort is running.

My only guess is a dbus thingy at this point but don't know how to track it down.

[secipolla]

That's the X default setting (blanks after 600s).

I think you can disable it for the session with

xset -dpms

or for 'ever' with a file turning off DPMS in /etc/X11/xorg.conf.d

Maybe something like:

Section "Monitor"
    Identifier     "Monitor0"
    Option         "DPMS" "off"
EndSection

P.S. note that even out of X the screen blanks when idle and that's a kernel setting AFAIK (but haven't searched how to disable that).

Other references: man xset and https://wiki.archlinux.org/index.php...ment_Signaling

[cazo]

Does your screen go blank, or does it actually 'sleep'? It's probably hard to tell on a laptop's internal display, but an external display's power LED usually changes from green to amber.

gsettings list-recursively org.gnome.settings-daemon.plugins.power

org.gnome.settings-daemon.plugins.power active true
org.gnome.settings-daemon.plugins.power button-hibernate 'hibernate'
org.gnome.settings-daemon.plugins.power button-power 'suspend'
org.gnome.settings-daemon.plugins.power button-sleep 'hibernate'
org.gnome.settings-daemon.plugins.power button-suspend 'suspend'
org.gnome.settings-daemon.plugins.power critical-battery-action 'hibernate'
org.gnome.settings-daemon.plugins.power idle-brightness 30
org.gnome.settings-daemon.plugins.power idle-dim-ac false
org.gnome.settings-daemon.plugins.power idle-dim-battery true
org.gnome.settings-daemon.plugins.power idle-dim-time 90
org.gnome.settings-daemon.plugins.power lid-close-ac-action 'blank'
org.gnome.settings-daemon.plugins.power lid-close-battery-action 'suspend'
org.gnome.settings-daemon.plugins.power notify-perhaps-recall true
org.gnome.settings-daemon.plugins.power percentage-action 2
org.gnome.settings-daemon.plugins.power percentage-critical 3
org.gnome.settings-daemon.plugins.power percentage-low 10
org.gnome.settings-daemon.plugins.power priority 1
org.gnome.settings-daemon.plugins.power sleep-display-ac 1800
org.gnome.settings-daemon.plugins.power sleep-display-battery 1800
org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0
org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'suspend'
org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 0
org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'suspend'
org.gnome.settings-daemon.plugins.power time-action 120
org.gnome.settings-daemon.plugins.power time-critical 300
org.gnome.settings-daemon.plugins.power time-low 1200
org.gnome.settings-daemon.plugins.power use-time-for-policy true

[fetchinson]

Thanks guys for the replies.

It turns out there is a new framework in the kernel called fanotify which can monitor files and directories for changes and even tells you what process it is doing it. And using fanotify I found out that upowerd is the culprit