search

superr4y / logkeys

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

log file empty after one hour #5

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.I do not know installed ok
2.
3.

What is the expected output? What do you see instead?
to have a log file with something in it

What version of the product are you using? On what operating system?

logkeys-0.1.0      bt4  laptop install
Please provide any additional information below.

locale 

LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

Original issue reported on code.google.com by netsukec...@gmail.com on 1 Feb 2010 at 6:47

Attachments:

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
It appears that BackTrack's kernel either doesn't use event interface, or much 
more
likely, logkeys didn't infer the correct input event device.

Can you please attach contents of file /proc/bus/input/devices, and the output 
of

dumpkeys -n|grep
'^\([[:space:]]shift[[:space:]]\)*\([[:space:]]altgr[[:space:]]\)*keycode'

run as root.

Original comment by kernc...@gmail.com on 1 Feb 2010 at 7:03

GoogleCodeExporter commented 9 years ago

Original comment by kernc...@gmail.com on 2 Feb 2010 at 6:04