cant determine keyboard

[GoogleCodeExporter]

What steps will reproduce the problem?
1.run lkl 
2.
3.

What is the expected output?
What do you see instead?
logkeys: Couldn't determine keyboard device. :/
logkeys: Please post contents of your /proc/bus/input/devices file as a new bug 
report. Thanks!

Q: Also tell me will this keylogger will work X windows or just it will log 
keys from console

Original issue reported on code.google.com by omersatt...@gmail.com on 5 Nov 2011 at 11:40

• Merged into: #42

Attachments:

• businputdevices.txt

[GoogleCodeExporter]

did you read the documentation?
http://code.google.com/p/logkeys/wiki/Documentation#Empty_log_file_or_%27Couldn%
27t_determine_keyboard_device&
run it with '--device event3' or '--device event4' switch.
it should work under X too.

Original comment by kernc...@gmail.com on 5 Nov 2011 at 2:40

• Changed state: Duplicate

[GoogleCodeExporter]

I checked these commands.Actually its a USB keyboard
1: llk --device(#also with -d option) /dev/input/event3 (#with all 
events,0,1,2,3,4,5)
2: llk -d /dev/input/by-id/usb-SIGMACH1P_USB_Keykoard-event-kbd
3: llk -d /dev/input/by-id/usb-SIGMACH1P_USB_Keykoard-event-if01
4: llk --device /dev/input/by-path/pci-0000\:00\:1d.1-usb-0\:1\:1.0-event-kbd

Result: Issue is the same....

Original comment by omersatt...@gmail.com on 5 Nov 2011 at 5:53

[GoogleCodeExporter]

it's logkeys, i.e.
logkeys --start --output mylog.log --device event3

llk is only the helper that invokes /usr[/local]/etc/logkeys-start.sh script.

please try again.

Original comment by kernc...@gmail.com on 5 Nov 2011 at 6:49

[GoogleCodeExporter]

I think its working now.Because log file says logging has started.I really 
appreciate your help.Thanks Dear.I`ll post if something goes wrong.Again thanks 

Original comment by omersatt...@gmail.com on 5 Nov 2011 at 7:01