Martin Kühne wrote:
> This reminds me, we're talking about i3 here.
Heyho,
if you're using unclutter, this thread[0] could also help you out. Either way it
seems that something else on your system already has an active keyboard/mouse
grab preventing slock from starting.
--Markus
0: http://list
This reminds me, we're talking about i3 here. Take a look at some of
the bugs that end up in their bugtracker, for example [0].
Could [1] be related to what you're seeing?
cheers!
mar77i
[0] https://github.com/i3/i3/issues/2539
[1] https://github.com/aktau/hhpc/issues/2
Thank you, Martin!
I see these messages on affected version:
slock: unable to grab mouse pointer for screen 0
slock: unable to grab keyboard for screen 0
2016-12-05 11:07 GMT+03:00 Martin Kühne :
> Look in ~/.xsession-errors, or wherever you redirect the window
> manager's stderr (readlink /proc/
Look in ~/.xsession-errors, or wherever you redirect the window
manager's stderr (readlink /proc//fd/2). Slock should leave a
message why it cannot run.
Generally speaking, if something works in the terminal, but doesn't
work through key binding, it's usually a matter of environment
variables.
che
