Control: tag -1 +patch Ian Campbell <i...@debian.org> wrote: [...] > So I believe the correct fix would be to skip the notifier if > the cycle time is zero since "The locker is started after the > first screen saver cycle". In that case a cycle time of 0 would > imply to me that the locker should be started immediately, > skipping the notifier. That would also seem to be implied by > the lack of a XCB_SCREENSAVER_STATE_CYCLE event in this case.
Yes, you're right, this is the correct behavior. I forked one of the copies of xss-lock in github and implemented this solution. It's in the latest two commits of this repo: https://github.com/tpikonen/xss-lock (The 3 commits before that could also be interesting, at least they improved my usage of xss-lock) Best, Teemu
