search

ramccor / logkeys

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

./logkeys: Error opening input event device 'EEEEEEEEEEEEEEEEEEEE����': No such file or directory #76

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1../logkeys -s -d /dev/input/event0
2.
3.

What is the expected output?

What do you see instead?
./logkeys: Error opening input event device 'EEEEEEEEEEEEEEEEEEEE����': 
No such file or directory

What version of the product are you using (`logkeys --help`)?
logkeys version: 0.1.1a
On what operating system?
OpenSuse 12.2

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.

Both in the attach

Original issue reported on code.google.com by gustavof...@gmail.com on 2 Dec 2011 at 3:03

Attachments:

GoogleCodeExporter commented 9 years ago 
weird. whats the output if you run `locale`?

Original comment by kernc...@gmail.com on 2 Dec 2011 at 1:20

GoogleCodeExporter commented 9 years ago 
output 'locale' in attach.
thanks.

Original comment by gustavof...@gmail.com on 4 Dec 2011 at 2:17

Attachments:

GoogleCodeExporter commented 9 years ago 
can you please try first running
$ LC_ALL="en_US.UTF-8" LANG="en_US.UTF-8" bash
and then, if you type `locale`, there shouldn't be any "POSIX" any more (all 
replaced by english UTF-8 locale).
then run logkeys as previously in that new bash session. what do you get?

how about if you run it
$ logkeys --start --device=event0
(only event0 without '/dev/input/')?

I have no idea why it doesn't work or where it gets the 'EEEE...' from.

Original comment by kernc...@gmail.com on 4 Dec 2011 at 7:24

GoogleCodeExporter commented 9 years ago 
Unfortunately the result is the same.
Apply changes "locale" and tried to run it with --device=event0, but the error 
is the same.
I would appreciate any alternative configuration.
Thanks for your time.

Original comment by gustavof...@gmail.com on 4 Dec 2011 at 10:50

GoogleCodeExporter commented 9 years ago 
I don't know what else to try?
I see you're running from directory (./logkeys), but 'make install'-ing 
shouldn't make any difference in this case.
The program is trying to open EEEEEEEEEEEEEEEEEEEE���� instead of 
/dev/input/event0, when of course it fails. I don't understand why EEE... :[ 
Sorry.

Please report if you come up with something. Ask on OpenSUSE forums or 
something.

Original comment by kernc...@gmail.com on 4 Dec 2011 at 11:31

GoogleCodeExporter commented 9 years ago 
um, if you run with --device=some_random_string, is output the same?

Original comment by kernc...@gmail.com on 4 Dec 2011 at 11:33

GoogleCodeExporter commented 9 years ago 
Yes, the output is the same. Only change the amount of characters 'E' and 
special characters remaining.
EEEEEEEEEEEEEEEEEEEEEEEEEEEEg
EEEEEEEEEEEEEEEEEEEE���~�
EEEEEEEEEEEEEEEEEEEE����

Original comment by gustavof...@gmail.com on 5 Dec 2011 at 2:56

GoogleCodeExporter commented 9 years ago 
As I imagined, I'm sorry, I don't know what is causing this.
Please try to find help and solution on your distribution's community forums.

Original comment by kernc...@gmail.com on 5 Dec 2011 at 10:27