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
