Logkeys doesn't work - Githubissues

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1.Change keyboard with USB keyboard

What is the expected output? Last working log file
What do you see instead? Nothing, just starting and date

What version of the product are you using (`logkeys --help`)? 0.1.0
On what operating system? Ubuntu 10.04

Please provide any additional information below.
If applicable, also attach contents of /proc/bus/input/devices, the output
of command `dumpkeys -n > dumpkeys.output`, and any
other relevant files.

Original issue reported on code.google.com by rioluk...@gmail.com on 24 May 2011 at 6:02

Merged into: #38

Attachments:

dumpkeys.output

GoogleCodeExporter commented 9 years ago

hello,

do you switch in the USB keyboard while logkeys is already running?
if that's the case, then the issue is known, I think.

can you please provide /proc/bus/input/devices before and after you attach the 
USB keyboard.

Original comment by kernc...@gmail.com on 24 May 2011 at 9:24

GoogleCodeExporter commented 9 years ago

[deleted comment]

GoogleCodeExporter commented 9 years ago

The keyboard was changed by my employee. I think yes, the usb keyboard was 
changed while computer on with the logkeys running.

I don't backup the /proc/bus/input/devices before keyboard changed, but now 
looks like this:

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
U: Uniq=
H: Handlers=kbd event0
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
U: Uniq=
H: Handlers=kbd event1
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0017 Vendor=0001 Product=0001 Version=0100
N: Name="Macintosh mouse button emulation"
P: Phys=
S: Sysfs=/devices/virtual/input/input2
U: Uniq=
H: Handlers=mouse0 event2
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3

I: Bus=0003 Vendor=0e8f Product=0022 Version=0110
N: Name="GASIA USB KB V11"
P: Phys=usb-0000:00:1d.1-2/input0
S: Sysfs=/devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0/input/input3
U: Uniq=
H: Handlers=kbd event3
B: EV=120013
B: KEY=10000 7 ff800000 7ff febeffdf f3cfffff ffffffff fffffffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=0e8f Product=0022 Version=0110
N: Name="GASIA USB KB V11"
P: Phys=usb-0000:00:1d.1-2/input1
S: Sysfs=/devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.1/input/input4
U: Uniq=
H: Handlers=kbd event4
B: EV=1f
B: KEY=837fff 2c3027 bf004444 0 0 1 c04 a27c000 267bfa d941dfed 9e0000 0 0 0
B: REL=40
B: ABS=1 0
B: MSC=10

I: Bus=0011 Vendor=0002 Product=0005 Version=0000
N: Name="ImPS/2 Generic Wheel Mouse"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input5
U: Uniq=
H: Handlers=mouse1 event5
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=103

There're some devices with kbd at the handlers, I tried event4, didn't work, 
when I tried event3 it worked. But i must use -d parameter. otherwise logkeys 
displays error. /dev/input/event-1 doesn't exist

Btw, what about the size of log file? Will it makes computer or logkeys slow?

Original comment by rioluk...@gmail.com on 25 May 2011 at 6:48

GoogleCodeExporter commented 9 years ago

yes, if you (re)attach another keyboard, it doesn't work, since for now, 
logkeys only listens on the interface inferred when the program is run.
sorry.

log file size increases for up to 25 bytes with each keystroke (normally just 1 
or 2 or 8 bytes per keystroke), but the file is appended to, so it shouldn't 
really have an effect on logkeys, or smooth running of the system (provided 
there is sufficient disk space).

Original comment by kernc...@gmail.com on 25 May 2011 at 9:30

Changed state: Duplicate

GoogleCodeExporter commented 9 years ago

I got logkeys working for me with a serial keyboard and couldn't get it working 
on my wireless USB keyboard. I read this post and tried unplugging and starting 
logkeys with the wireless USB keyboard but it still doesn't record keystrokes 
on the wireless USB board. Any information on this would be rad! Thanks!

Original comment by griffith...@gmail.com on 6 Jun 2011 at 1:05

GoogleCodeExporter commented 9 years ago

Yes, not all keyboard models are recognized, unfortunately.
To help correct this ASAP, please attach your /proc/bus/input/devices in this 
issue:
http://code.google.com/p/logkeys/issues/detail?id=42

Meanwhile, follow these instructions to get it working manually:
http://code.google.com/p/logkeys/wiki/Documentation#Empty_log_file_or_%27Couldn%
27t_determine_keyboard_device&

Original comment by kernc...@gmail.com on 6 Jun 2011 at 11:33

ramccor / logkeys

Logkeys doesn't work #59