On Thu, 2022-08-25 at 13:27 -0400, Antoine Beaupre wrote: > I have xss-lock setup to start xsecurelock automatically after the > delay prescribed by my `xset` configuration.
FWIW I've never seen it used with xsecurelock (I use i3lock) but I do `xset b off` in my session (but not the `s 60 3` thing you do) and autolocking does work for me as expected -- although in practice mostly lock via a key binding as I walk away, but if I forget it does lock itself. > I wonder if I'm missing a key service in my session, or how to debug > the screensaver in Xorg I'm afraid I don't know about any of this sort stuff, I just package the tool as a user. As you say `xset s activate` works I'm inclined to suggest the issue is elsewhere in the stack. But here are some random thoughts nonetheless: You pass --verbose but I assume the journald output for xss- lock.service has nothing of use? You could switch xsecurelock out for a wrapper which logs and then forwards to the real thing, at least then you would know if it was being called at all. Have you compared the process lists on the working and non-working systems, that might give a hint about a missing process/service in your session. Perhaps also look for anything which is inhibiting screenlock, e.g. a "Presentation Mode" setting? I think this is logind related functionality so perhaps there is a way to query the underlying setting via that? In the past I've seen these options having different setting for mains power vs battery, which could explain a laptop vs desktop difference. Ian.
