A bit more info. It appears that the sequence of events may be the
following:
I lock the screen from the keyboard. That key is bound to i3lock --dpms
--inactivity-timeout 10 --color=220022 .
A bit later, xautolock decides to lock the screen as well. That command,
by chance, is not quite the
Good idea, thanks, I'll bind my lock key to that. I think I learned of
xautolock after learning that I could lock the screen by binding i3lock to
a key.
Jeff Abrahamson
+33 6 24 40 01 57
+44 7920 594 255-- only if I'm in the UK
http://jeff.purple.com/
http://blog.purple.com/jeff/
On 1 May
On 1 May 2015 at 17:40, Jeff Abrahamson j...@purple.com wrote:
I lock the screen from the keyboard. That key is bound to i3lock --dpms
--inactivity-timeout 10 --color=220022 .
If you use xautolock, better trigger a lock through it then, I use the
Pause button to lock it like this:
