warbo-utilities: 9b9bb3bc3bb3bc1250a40b8c00e00a19b22db3f3

     1: From: Chris Warburton
     2: Date: Thu, 31 May 2018 12:37:03 +0100
     3: State: resolved
     4: Subject: Use space2ctrl for keys
     5: Message-Id: <efdab4013c354a72-0-artemis@nixos>
     6: resolution: fixed
     7: 
     8: Pull out xcape and xmodmap in favour of space2ctrl. We used to use it
     9: many moons ago, I can't remember why we switched to xcape. In any case,
    10: our xcape setup is definitely complicated and flaky, so might as well
    11: try something simpler.
    12: 
    13: One important question is whether we can spot the reason for keys
    14: becoming unresponsive. My current thoughts are:
    15: 
    16:  - Suspend/resume might be messing with things
    17:  - Plugging/unplugging USB keyboards might be the cause
    18:  - Plugging/unplugging external monitors might be the cause
    19:  - Upgrading the kernel without rebooting might be the reason we need to
    20:    rmmod/modprobe to fix the keyboard (which breaks the mouse)
    21: 
    22: It would be useful if we could either hook on to these
    23: suspend/resume/plug/unplug events to run the keys command, or if we
    24: could reliably spot when those events have happened and poll for
    25: them. Either way, we shouldn't be running keys over and over.

Generated by git2html.