Follow

jwz has rewritten core parts of XScreenSaver, version 6 beta 1 now up for testing at jwz.org/blog/2021/02/xscreensa
The new version requires X with the XInput2 extension (X11R7).

That surface that can result in unlocking the screen after a crash has been greatly reduced by splitting up XScreenSaver into three separate programs.

@galaxis XScreenSaver is the one application which is handling the keyboard setup differently than any other. I.e., while my X11 ran without the "nodeadkey" variant, XScreenSaver happily used all keys hit. I'm sure Jamie has a reason for this.

Sign in to participate in the conversation
INFRa Mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!