X grabs the input device exclusively, results in no output

[GoogleCodeExporter]

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

What is the expected output? What do you see instead?


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


Please provide any additional information below.
If applicable, also attach contents of /proc/bus/input/devices.
proc/bus/input/devices   is an empty file

Original issue reported on code.google.com by netsukec...@gmail.com on 2 Feb 2010 at 10:38

Attachments:

• output
• devices

[GoogleCodeExporter]

Issue 5 has been merged into this issue.

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

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Great, now could you please try running logkeys with --device option, e.g.
$ logkeys --start --device=/dev/input/eventX
especially for X = 4, 5 or 6 (i.e. /dev/input/event5), and report if it works 
that way.

logkeys only tries the first kbd device it finds, and in your case that is
/dev/input/event4, which responds to serial keyboard and may not work if you are
using an USB keyboard.

If neither of those work (/dev/input/eventX for X=4,5,6), then please try 
running
$ sudo od -tx1 /dev/input/eventX
(for X=0 to 9), and see if any variation of the above command produces any 
output on
key press. If not, also try it in console outside of X (i.e. Ctrl+Alt+F1).

Thank you for your time!

Original comment by kernc...@gmail.com on 2 Feb 2010 at 8:52

• Changed title: no output to log file
• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Hi tried logkeys --start --device=/dev/input/event 4 through 6 no joy

tried Ctrl+Alt+F1 no joy but f2 f3  f4 f5 f6 yes ok

This command sudo od -tx1 /dev/input/event0 through 9 
i had to ctrl c as it just sat there

this software workes in any tty session but not in a gui i hope helps

Original comment by netsukec...@gmail.com on 3 Feb 2010 at 10:12

• Added labels: ****
• Removed labels: ****

Attachments:

• logkeys.log

[GoogleCodeExporter]

Your attached logkeys.log file shows
{{{
Logging started ...

2010-02-03 08:40:06+0000 > ls#<BckSp>root
2010-02-03 08:41:51+0000 > xxxxxxx
2010-02-03 08:41:55+0000 > <LCtrl>c
2010-02-03 08:42:09+0000 > ls
2010-02-03 08:42:23+0000 > cd .
2010-02-03 08:42:26+0000 > cd ..
2010-02-03 08:42:29+0000 > ls
2010-02-03 08:42:31+0000 > cd home
2010-02-03 08:42:34+0000 > cd .
2010-02-03 08:42:38+0000 > cd ..
2010-02-03 08:42:41+0000 > startx
2010-02-03 08:42:46+0000 > 
<LCtrl><LAlt><F4><Esc><LCtrl><LAlt><Esc><LCtrl><LMeta> 
2010-02-03 08:43:15+0000 > 
2010-02-03 08:43:16+0000 > root
2010-02-03 08:43:21+0000 > xxxxxx
2010-02-03 08:43:25+0000 > <LCtrl><LAlt>0reboot
2010-02-03 08:43:50+0000 > 

Logging stopped at 2010-02-03 08:43:53+0000
}}}

So you are saying this successful logging session was made in a tty?
With which device?

In this case it seems that your X is grabbing your keyboard exclusively
(i.e. http://separaterealities.com/blag/?p=6) to which I have yet to find a 
workaround.

Ideas are very welcome. :)

Thank you for this bug report.

Original comment by kernc...@gmail.com on 3 Feb 2010 at 2:20

• Changed state: Accepted
• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Hey, netsukecarving,

Can I ask you for your /etc/X11/xorg.conf file, please.

Original comment by kernc...@gmail.com on 1 Apr 2010 at 1:14

• Changed title: X grabs the input device exclusively, results in no output
• Added labels: ****
• Removed labels: ****