On January 19, 2018 9:42:26 AM GMT+01:00, Bennett Piater <bennett@piater.name> wrote:
On 01/18/2018 09:37 PM, Alad Wenter via aur-general wrote:
See the bug report I linked in the first reply.
https://bitbucket.org/raymonad/xss-lock/issues/17/does-not-report-activity-t...
Right, that is actually something else than what I did. I used `xset s` to trigger on inactivity, and xss-lock correctly locks the screen when that happens.
So it seems like it can still be used as a replacement for xautolock.
Fwitw (and sorry for hijacking), I recently tried xprintidle (with a forked upstream, different from the one in the AUR) and it seems to work. This might still be used in a script to lock screens automatically under X, but it's clunky. I'd much prefer a more complete solution, as xautolock is aging (not so well) and at least in my case produces undesirable defuncts from time to time. xss-lock seemed too broken at that time, so I never used it. Are there any other alternatives not mentioned in the wiki? Best, David -- https://sleepmap.de