Re: [dev] [ANNOUNCE] slock-1.3

From: Markus Teich <markus.teich_AT_stusta.mhn.de>
Date: Sat, 13 Feb 2016 11:17:24 +0100

hiro wrote:
> How does your integrated execution of s2ram change that? Your slock can still
> fail in just the same way.

Heyho hiro,

with the patch first the cover window is created and the keyboard and mouse are
grabbed. I consider this setup. If it fails, slock exits and does *not* execute
s2ram. If it succeeded, s2ram is executed and the loop handling user input is
entered. Of course there could be a crash inside that loop, but we cannot know
that in advance and we also cannot fork-exec s2ram at any later stage.

The most common case for slock failing was that the grabbing of input devices
failed when some other application still had a grab active. This failure is
fixed by the patch.

--Markus
Received on Sat Feb 13 2016 - 11:17:24 CET