Oh and I found more information about this in the arch wiki:
https://wiki.archlinux.org/title/Session_lock#xss-lock
That seems to say that this command is supposed to trigger a lock:
loginctl lock-session
and it does *not* work here. Does it work for you?
It seems the `xset s` mechanism i am using is the "DPMS" hook. They do
have a note there:
> Note: When using xss-lock with DPMS, you will have to blank the screen
> yourself. It will not be triggered when looking at videos.
It is not exactly to me what that means ("blank the screen
yourself"??). But it does hint that something else (a video player i
guess?) will prevent screen locking, which begs the question of what
qualifies as a video player. Maybe if i have a video player playing
somewhere that I didn't know about? I did have a tab opened on some
youtube thing earlier, but i tried closing that tab (and indeed, all of
firefox in fact) and that didn't do it.
It would sure be nice if one could tell wth is preventing this thing
from sending locking signals. :)
I also found out on that wiki that you can use systemd to send those
signals:
https://wiki.archlinux.org/title/Session_lock#Inactivity
... but considering that loginctl lock-session doesn't work in the first
place, i wonder how this could work at all anyways... maybe worth a try?
--
Freedom is being able to make decisions that affect mainly you. Power
is being able to make decisions that affect others more than you. If
we confuse power with freedom, we will fail to uphold real freedom.
- Richard Stallman
