DPMS / ScreenSaver timers are not independent (can't dpms/lock independently)
I'm trying to poweroff my screen via dpms instead of using a screensaver, then lock it after a longer timeout. Since session locking is inexorably tied to the screensaver timeout, this is proving to be fruitless so far.
This seems to be impossible, since dpms automatically triggers the screensaver timeout as well, despite https://www.x.org/releases/X11R7.7/doc/xextproto/dpms.html contemplating such a user-case scenario.
Trying to work this around, I was hoping I could use the cycle time in combination with xss-lock:
xss-lock -n 'xset dpms force off' locker
xset s 60 600
xss-lock will trigger xset after 60s, then the locker at 600. This normally works if DPMS is not involved, however DPMS will inhibit the cycle timer, which is somewhat understandable.
I was hoping the different power states (powersave/suspend) would make a difference, however they're all handled the same.
Would it make sense to handle the cycle timer also in higher power-level states (anything except off)?