You are not logged in.
I have the following setup for xsecurelock:
xset s 3600 3600 -dpms
[...]
export XSECURELOCK_SAVER="saver_mpv"
export XSECURELOCK_LIST_VIDEOS_COMMAND="find ~/Videos/movies -type f"
export XSECURELOCK_BLANK_TIMEOUT=-1
xss-lock -n /usr/lib/xsecurelock/dimmer -l -- xsecurelockThe goal is to have a screensaver that never turns off, and for the screensaver (and lock) to activate after 1 hour of inactivity. The problem here is that automatic dimming after one hour doesn't work -- I have to run:
xset s activatemanually through sxhkd -- and the screen blanks after a period of running through the screensaver. I have read through the xset manual but can't seem to understand how to fix these issues. I assume the xset command I am currently using is wrong, but am unaware of a better option. I know that all the power management settings on my monitor are off.
Last edited by H2R (2021-11-13 04:42:02)
Offline
xset q?
Online
Screen Saver:
prefer blanking: yes allow exposures: yes
timeout: 3600 cycle: 3600
[...]
DPMS (Energy Star):
Standby: 600 Suspend: 600 Off: 600
DPMS is DisabledOffline
Looks ok, possibly something fends off the screensaver - did you try to drastically lower the timeout (5 or 10 seconds or so) and w/o anything supicious (video player, browsers, …) running?
About DPMS kicking in: possibly triggered by xsecurelock?
Did you try https://archlinux.org/packages/community/x86_64/slock/ instead?
Online
I incorrectly assumed that xsecurelock wouldn't invoke DPMS when it was disabled, so i removed the
export XSECURELOCK_BLANK_DPMS_STATE="on" option when I disabled DPMS. I'll add it again. As for the automatic dimming, I'm not sure why a longer inactive time hasn't worked but a variety of short intervals I tested (5, 60, etc.) do work.
Offline
1h is a long time, some spurious input could happen (optical mouse juddering) or some client fakes input to prevent the screensaver from kicking in (see my previous post).
You could keep "sudo libinput debug-events" or "sudo evtest" running to see whether some device acts up.
Did that variable tame the DPMS situation?
Online
The DPMS situation seems to be fixed, thank you. As for the automatic dimming, I couldn't find lingering devices after a period of inactivity (using debug-events and evtest). There could be a client that mimics input like you mentioned.
Offline