search

ramccor / logkeys

Automatically exported from code.google.com/p/logkeys
Other
0 stars 0 forks source link

Empty logfile #69

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Hardware: Acer TravelMate 6592 laptop with usb keyboard
2. Software: Ubuntu 11.04 x86_64: sudo apt-get logkeys
3. Action: touch test.log; sudo logkeys --start --output test.log

What is the expected output?
The pressed keys of the laptop keyboard (or from the usb keyboard).

What do you see instead?
Empty logfile

What version of the product are you using (`logkeys --help`)?
logkeys version: 0.1.0

On what operating system?
Ubuntu 11.04 x86_64

Additional information

cat /proc/bus/input/devices:

I: Bus=0019 Vendor=0000 Product=0003 Version=0000
N: Name="Sleep Button"
P: Phys=PNP0C0E/button/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input0
U: Uniq=
H: Handlers=kbd event0 
B: PROP=0
B: EV=3
B: KEY=4000 0 0

I: Bus=0019 Vendor=0000 Product=0005 Version=0000
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input1
U: Uniq=
H: Handlers=event1 
B: PROP=0
B: EV=21
B: SW=1

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2
U: Uniq=
H: Handlers=kbd event2 
B: PROP=0
B: EV=3
B: KEY=10000000000000 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/input3
U: Uniq=
H: Handlers=kbd event3 
B: PROP=0
B: EV=3
B: KEY=10000000000000 0

I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input4
U: Uniq=
H: Handlers=sysrq kbd event4 
B: PROP=0
B: EV=120013
B: KEY=10000 c020000000000 0 0 700f02000003 3803078f830f401 febfffdfffefffff 
fffffffffffffffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=0461 Product=4d15 Version=0111
N: Name="USB Optical Mouse"
P: Phys=usb-0000:00:1d.1-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:1d.1/usb6/6-1/6-1:1.0/input/input5
U: Uniq=
H: Handlers=mouse0 event5 
B: PROP=0
B: EV=17
B: KEY=70000 0 0 0 0
B: REL=103
B: MSC=10

I: Bus=0003 Vendor=413c Product=2003 Version=0110
N: Name="Dell Dell USB Keyboard"
P: Phys=usb-0000:00:1d.0-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.0/input/input6
U: Uniq=
H: Handlers=sysrq kbd event6 
B: PROP=0
B: EV=120013
B: KEY=1000000000007 ff9f207ac14057ff febeffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7

I: Bus=0019 Vendor=0000 Product=0006 Version=0000
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: 
Sysfs=/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/LNXVIDEO:00/input/inpu
t7
U: Uniq=
H: Handlers=kbd event7 
B: PROP=0
B: EV=3
B: KEY=3e000b00000000 0 0 0

I: Bus=0003 Vendor=5986 Product=0102 Version=0005
N: Name="Acer Crystal Eye webcam "
P: Phys=usb-0000:00:1a.7-1/button
S: Sysfs=/devices/pci0000:00/0000:00:1a.7/usb1/1-1/1-1:1.0/input/input8
U: Uniq=
H: Handlers=kbd event8 
B: PROP=0
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card0/input9
U: Uniq=
H: Handlers=event9 
B: PROP=0
B: EV=21
B: SW=4

I: Bus=0011 Vendor=0002 Product=0007 Version=92b1
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio4/input0
S: Sysfs=/devices/platform/i8042/serio4/input/input10
U: Uniq=
H: Handlers=mouse1 event10 
B: PROP=1
B: EV=b
B: KEY=6420 3000f 0 0 0 0
B: ABS=11000003

I: Bus=0011 Vendor=0002 Product=0001 Version=0000
N: Name="PS/2 Generic Mouse"
P: Phys=synaptics-pt/serio0/input0
S: Sysfs=/devices/platform/i8042/serio4/serio5/input/input11
U: Uniq=
H: Handlers=mouse2 event11 
B: PROP=0
B: EV=7
B: KEY=70000 0 0 0 0
B: REL=3

Original issue reported on code.google.com by gaspary...@gmail.com on 17 Aug 2011 at 4:34

GoogleCodeExporter commented 9 years ago 
Until the software is patched, please follow these instructions to get it 
working:
http://code.google.com/p/logkeys/wiki/Documentation#Empty_log_file_or_%27Couldn%
27t_determine_keyboard_device&
i.e. you will have to run logkeys with --device=event6 switch (or whatever 
event interface your device is on).

Original comment by kernc...@gmail.com on 17 Aug 2011 at 6:01

GoogleCodeExporter commented 9 years ago 
Issue 70 has been merged into this issue.

Original comment by kernc...@gmail.com on 17 Aug 2011 at 6:37

GoogleCodeExporter commented 9 years ago 
Tried:
 "touch test.log; sudo logkeys -d event5 --start --output test.log"

 "touch test.log; sudo logkeys -d /dev/input/event5 --start --output test.log"

(also tried other event numbers from 0 to 31, but "sudo cat /dev/input/event5" 
is the only one that seems to show something).

But still no luck.

Any ideas ?

Original comment by gaspary...@gmail.com on 23 Aug 2011 at 11:14

GoogleCodeExporter commented 9 years ago 
does `sudo cat /dev/input/event5` output when you move your mouse? as per 
/proc/bus/input/devices above, it seems event5 is connected with your USB mouse 
rather than keyboard.

I don't know. perhaps it's got something to do with issue 60?

Original comment by kernc...@gmail.com on 23 Aug 2011 at 11:29

GoogleCodeExporter commented 9 years ago 
`sudo cat /dev/input/event5` does not output anything when I move my mouse.
The configuration at this moment is a laptop with a usb keyboard and a usb 
mouse.

I have tested `sudo cat /dev/input/event4` and it outputs the keys from the 
laptop keyboard. Still no luck with "touch test.log; sudo logkeys -d 
/dev/input/event4 --start --output test.log"

From strace I get this (if you think it may be important I can post the hole 
output of strace):

access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
connect(6, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110) = -1 ENOENT 
(No such file or directory)

stat("/usr/local/sbin/logkeys", 0x7fff2e931f80) = -1 ENOENT (No such file or 
directory)
stat("/usr/local/bin/logkeys", 0x7fff2e931f80) = -1 ENOENT (No such file or 
directory)
stat("/usr/sbin/logkeys", 0x7fff2e931f80) = -1 ENOENT (No such file or 
directory)

connect(5, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110) = -1 ENOENT 
(No such file or directory)

ioctl(5, SNDCTL_TMR_TIMEBASE or TCGETS, 0x7fff39792b40) = -1 ENOTTY 
(Inappropriate ioctl for device)

Original comment by gaspary...@gmail.com on 23 Aug 2011 at 12:29

GoogleCodeExporter commented 9 years ago 
yes, please do attach the whole strace dump in a file. 
also, what does "uname -a" say about the kernel you are using?

Original comment by kernc...@gmail.com on 24 Aug 2011 at 10:34

GoogleCodeExporter commented 9 years ago 
usr@laptop:~$uname -a
Linux laptop 2.6.38-11-generic #48-Ubuntu SMP Fri Jul 29 19:02:55 UTC 2011 
x86_64 x86_64 x86_64 GNU/Linux

May be it is important, have test it with Unity and with KDE v4.6.5

Original comment by gaspary...@gmail.com on 25 Aug 2011 at 12:00

Attachments:

GoogleCodeExporter commented 9 years ago 
Same problem with LXDE.

Original comment by gaspary...@gmail.com on 25 Aug 2011 at 3:47

GoogleCodeExporter commented 9 years ago 
After a clean Ubuntu 10.4 re-install, everything is working ok now.

Original comment by gaspary...@gmail.com on 11 Oct 2011 at 12:21

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
This happens to me as well. I get a completely empty log file (0 bytes) even 
when I supply the device ID directly. I do `sudo logkeys -s -d event0`; it 
prints nothing and the exit code is 0.

I'm on arch linux, `Linux firefly-desky 3.1.4-1-ARCH #1 SMP PREEMPT Tue Nov 29 
08:55:45 CET 2011 x86_64 AMD Phenom(tm) II X6 1055T Processor AuthenticAMD 
GNU/Linux`.

I posted my /proc/bus/input/devices etc. here: 
https://code.google.com/p/logkeys/issues/detail?id=42#c15

Original comment by effi...@gmail.com on 12 Dec 2011 at 12:11

GoogleCodeExporter commented 9 years ago 
by fixing related issues (issue 60 and issue 42), I think this can be closed.
see those issued for an explanation.

Original comment by kernc...@gmail.com on 4 Jan 2012 at 7:26

GoogleCodeExporter commented 9 years ago 
Hello
I have same problem with Ubuntu 13.04
:(

Original comment by voevodin...@gmail.com on 10 Jul 2013 at 10:26

GoogleCodeExporter commented 9 years ago 
Hello, i have the same problem with Ubuntu 13.10

Original comment by leon1...@gmail.com on 10 Apr 2014 at 4:38