Closed GoogleCodeExporter closed 9 years ago
Hello. :-)
Thanks for this bug report.
Can you please follow the procedure described here
http://code.google.com/p/logkeys/wiki/Documentation#Empty_log_file_or_%27Couldn%
27t_determine_keyboard_device&
and determine which device interfaces your keyboard.
It will likely be /dev/input/event3 or /dev/input/event4.
Whichever it is, please add a comment here.
Then, until the next version of logkeys, run it with -d switch, e.g.
$ logkeys --start --device /dev/input/event3
:-)
Original comment by kernc...@gmail.com
on 13 Jun 2010 at 2:52
Issue 35 has been merged into this issue.
Original comment by kernc...@gmail.com
on 15 Jul 2010 at 3:05
Hopefully fixed in r72.
Original comment by kernc...@gmail.com
on 19 Aug 2010 at 3:57
Original issue reported on code.google.com by
indika.l...@gmail.com
on 12 Jun 2010 at 11:04