Andreas Doll wrote:
> On 2016-01-15 at 23:21, Markus Teich wrote:
> > I don't like the man-page approach. Documentation always looses
> > synchronization to the codebase, so my proposal would be to output a similar
> > error message in slock. The link from "slock: could not grab pointer" to
> > `un
On 2016-01-15 at 23:21, Markus Teich wrote:
> I don't like the man-page approach. Documentation always looses
> synchronization
> to the codebase, so my proposal would be to output a similar error message in
> slock. The link from "slock: could not grab pointer" to `unclutter -grab`
> should
> be
Andreas Doll wrote:
> By the way, xscreensaver successfully locks the screen, and prints
>
> couldn't grab pointer! (AlreadyGrabbed)
>
> and displays the verification window only upon keyboard activity. Without
> unlcutter this window appears also on mouse input.
Heyho Andreas,
This is probably
On 2016-01-15 at 19:40, Markus Teich wrote:
> I assume this is the same issue for slock. From XGrabKeyboard(3):
> > If the keyboard is actively grabbed by some other client, XGrabKeyboard
> > fails
> > and returns AlreadyGrabbed.
> For screenlockers grabbing the keyboard is a must so no other cl
Andreas Doll wrote:
> I've just tested with i3lock 2.6 (on Debian stable), which also returns after
> a short moment to the desktop without verification, complaining
>
> $ i3lock
> i3lock: Cannot grab pointer/keyboard
Heyho Andreas,
I assume this is the same issue for slock. From XGrabKeyboard(3
On 2016-01-11 at 09:21, Markus Teich wrote:
> I was not aware of that issue. The man page of unclutter says for the `-grab`
> option "This often doesn't interoperate too well with some window managers" so
> it might actually be not slocks fault. Since this does not seem to be a
> critical
> issue,
Andreas Doll wrote:
> I've tested with slock 1.1 and 1.2. Upon researching this issue I found that
> it was already noticed by others. Arch wiki [1] blames unclutter for this and
> notes that is also breaks i3lock, which isn't confirmed in [2].
>
> I'm not sure if you are fine with the current beh
Hello
I've noticed that slock won't lock the screen if unclutter grabbed to mouse
pointer. To be precise, the screen blacks for a short moment, and then returns
to the desktop without password verification.
This happens when
$ unclutter -grab
was called more than 5 seconds before, or immediatel
