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 <mysat...@gmail.com>: > Look in ~/.xsession-errors, or wherever you redirect the window > manager's stderr (readlink /proc/<i3_pid>/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. > > cheers! > mar77i >
