On my machine I'm not getting any mouse or keyboard feedback.

[GoogleCodeExporter]

This is folded in from Issue 52.

Hi,

Thanks for looking into this. I do not get the original error after installing 
key-mon 1.4.4 with "sudo python setup.py install", and key-mon now starts up 
fine.

*But* neither mouse button nor key presses actually result in any action on 
key-mon's behalf :)

I can conform the following packages are installed on my machine:

librsvg2-common
python-gtk2
python-xlib

I am not sure about the "X.Org record module" or how to check whether it is 
present. Could that be why key-mon doesn't do anything for me?

best,
flo.H

Original issue reported on code.google.com by scottaki...@gmail.com on 24 Nov 2010 at 6:57

[GoogleCodeExporter]

@hollerweger01@qub.ac.uk if you have the time there are some things you could 
check for me.

On my machine(s) when I run this grep I get the following:

$ egrep ' LoadModule.*(evdev|record)' /var/log/Xorg.0.log
(II) LoadModule: "record"
(II) LoadModule: "evdev"

Perhaps you don't have the record module?  I've seen on a forum that the 
`record` module was removed for a while because it had some bugs (but is now 
back) Perhaps you are on this version?

Do you have the evdev module listed?  An older version of key-mon used evdev, 
but it didn't work with the wacom tablets, so it was rewritten using `record`.

If that's your problem and this is still an issue for you, it might be possible 
to restore evdev and make it an optional (backup) way of getting the mouse, and 
keyboard information.

---
Another thing you could try is to run xlib.py which is installed with the 
program, when I run the following I get this output when hitting keys:

$ python /usr/share/pyshared/keymon/xlib.py
Press ESCape to quit
Xlib.protocol.request.QueryExtension
Xlib.protocol.request.QueryExtension
type:EV_KEY scancode:28 code:KEY_RETURN value:0
type:EV_KEY scancode:16 code:KEY_Q value:1
qtype:EV_KEY scancode:16 code:KEY_Q value:0
type:EV_KEY scancode:46 code:KEY_C value:1
ctype:EV_KEY scancode:46 code:KEY_C value:0
type:EV_KEY scancode:1 code:KEY_ESCAPE value:1

Original comment by scottaki...@gmail.com on 24 Nov 2010 at 6:58

[GoogleCodeExporter]

Hi,

The egrep command you suggested gives me exactly the same output as you get, so 
I guess the record module is in place. I cannot comment on the possibility of 
it being a buggy version, and due to dependency issues it is not possible for 
me to upgrade at this stage.

What I noted, however, is that my key-mon install routine (sudo python setup.py 
install) does not seem to have created a directory /usr/share/pyshared/keymon/

Instead, I can find xlib.py in the following places:

/usr/local/src/key-mon-1.5.1$ locate xlib.py
/usr/lib/python2.5/site-packages/keymon/xlib.py
/usr/local/src/key-mon-1.5.1/build/lib/keymon/xlib.py
/usr/local/src/key-mon-1.5.1/src/keymon/xlib.py

(where /usr/local/src/key-mon-1.5.1/ is the dir where I extracted the key-mon 
tarball in)

When i run

python /usr/local/src/key-mon-1.5.1/build/lib/keymon/xlib.py

that does not seem to react to any keystrokes. Maybe that's where the root of 
this issue lies?

best,
flo.H

Original comment by fhollerweger01@qub.ac.uk on 25 Nov 2010 at 7:43

[GoogleCodeExporter]

Yes the fact that xlib.py is not reacting to any keystokes or mouse clicks is 
the problem.  What about if you run as root?:

sudo python /usr/local/src/key-mon-1.5.1/build/lib/keymon/xlib.py

Original comment by scottaki...@gmail.com on 26 Nov 2010 at 11:54

[GoogleCodeExporter]

No, no luck as root either, sorry...

Original comment by fhollerweger01@qub.ac.uk on 26 Nov 2010 at 12:12

[GoogleCodeExporter]

I have a slightly modified xlib.py which seems to conform more to what another 
program (autokey) is doing. Perhaps this might solve your problem?

$ python xlib.py

Original comment by scottaki...@gmail.com on 26 Nov 2010 at 2:55

Attachments:

• xlib.py

[GoogleCodeExporter]

Thanks for this, but unfortunately that new xlib.py does not seem to do the 
trick either (neither as regular user nor as root).

Just to make sure I am getting this right: I do a
  python /path/to/the/xlib.py
and then fire out random keystrokes in a separate window with my favourite text 
editor. That should do the trick, right?

best,
flo.H

Original comment by fhollerweger01@qub.ac.uk on 26 Nov 2010 at 3:33

[GoogleCodeExporter]

Right, keystrokes in the same window (or mouse clicks) or in another window 
should output some information.  You get no output at all? 

Do you at least get?:
Press ESCape to quit
Xlib.protocol.request.QueryExtension
Xlib.protocol.request.QueryExtension

An using the xlib.py that I attached in the bug page (in case you didn't notice 
it).

I can make another version of the file that outputs even more information so we 
can see where it fails.

Also, do you have to kill the program with Ctrl-C or with the kill command?

Original comment by sc...@forusers.com on 26 Nov 2010 at 3:50

[GoogleCodeExporter]

> You get no output at all?

No, none whatsoever.

> Do you at least get?:
> Press ESCape to quit
> Xlib.protocol.request.QueryExtension
> Xlib.protocol.request.QueryExtension

Yes.

> An using the xlib.py that I attached in the bug page (in case you didn't 
notice it).

Correct.

> Also, do you have to kill the program with Ctrl-C or with the kill command?

This is weird: Sometimes I cannot kill the program using Ctrl+C when I have 
typed something in the same shell after starting xlib. I cannot seem to say 
what exactly this depends on, though.

best,
flo.H

Original comment by fhollerweger01@qub.ac.uk on 26 Nov 2010 at 4:17

[GoogleCodeExporter]

I have another version of xlib.py to try, perhaps it has something to do with 
the threading (do you have a really fast machine?)

Original comment by sc...@forusers.com on 26 Nov 2010 at 4:37

Attachments:

• xlib.py

[GoogleCodeExporter]

Hi,

I really appreciate your efforts, but I am afraid that this thrid version of 
xlib does not do anything for me either.

My machine is a dual-core at 1.7 GHz each, so fairly standard.

best,
flo.H

Original comment by fhollerweger01@qub.ac.uk on 26 Nov 2010 at 4:41

[GoogleCodeExporter]

I should really be thanking you!  I'm sure there are other's that encountered 
your problem and just gave up without telling me.

So I have another version to try ;-)

Original comment by sc...@forusers.com on 26 Nov 2010 at 5:01

Attachments:

• xlib.py

[GoogleCodeExporter]

Sorry, new version is again no success (I am always testing them as normal user 
and root, by the way).

best,
flo.H

Original comment by fhollerweger01@qub.ac.uk on 26 Nov 2010 at 5:47

[GoogleCodeExporter]

Hi,

Just to announce that I got key-mon 1.5.1 (compiled from source) working on a 
different machine with a comparable Debian system.

The only difference I can tell from top of my head is that that machine has 
recently been upgraded, which would most likely also have included an X 
upgrade. So maybe this is an indication that the record module is indeed to 
blame?

best,
flo.H

Original comment by fhollerweger01@qub.ac.uk on 2 Dec 2010 at 1:58

[GoogleCodeExporter]

I have actually just upgraded the machine which key-mon never was working on, 
so now it runs X server version 1.7.7 (rather than 1.6.5, which it ran before), 
which is the same X version as on my other machine, on which key-mon works like 
a charm.

And I am afraid, after the upgrade key-mon is still not reacting to any keys on 
that first machine, so maybe the record module theory does not hold up to 
reality after all?

best,
flo.H

Original comment by fhollerweger01@qub.ac.uk on 4 Dec 2010 at 7:05

[GoogleCodeExporter]

I have exactly the same behaviour, but when I run ./xlib.py, I get only

Press ESCape to quit
djjd^CUser interrupted

"djjd" are the keys I've pressed. No messages about 
"Xlib.protocol.request.QueryExtension". 

I have /usr/share/pyshared/keymon directory filled with files.

In --debug mode there is no information about either mouse buttons or keys 
pressed

Everything else is exactly the same, I have "record" module and all libraries 
installed. I have Ubuntu 9.04. 

Original comment by shaman.sir on 10 Jan 2011 at 7:48

[GoogleCodeExporter]

I worked with previous versions of key-mon, they worked correctly, but now, 
when I've installed a new version, all them stopped to work.

Also I've tried to turn iBus on and off.

Original comment by shaman.sir on 10 Jan 2011 at 7:50

[GoogleCodeExporter]

I've got version 0.16 to work using

sudo python ./key-mon-0.16/key-mon/src/keymon/key_mon.py

No effect was changed on 1.5.1 though...

Original comment by shaman.sir on 10 Jan 2011 at 8:06

[GoogleCodeExporter]

@shaman.sir Any news on your side? (Hope you are one has starred) What was the 
Xorg server version you were using? and what's it now? (Current stable version 
is 1.10.x)

Original comment by livibet...@gmail.com on 17 Aug 2011 at 12:08

[GoogleCodeExporter]

I am closing this, because

 1. The original had been resolved by upgrading to newer X (1.7.7), though it doesn't seem to be a complete fix. Something was in factor but it wasn't identified and it's been too long since then.
 2. The second problem's owner shaman.sir hasn't responded to my inquire. (2 weeks)
 3. The problem doesn't look like exactly the same, second didn't have 'QueryExtension' message at all.

If there is still a problem, please create a new issue (please do ;-) with the 
current versions of Key-mon and libraries, so we can start fresh.

Original comment by livibet...@gmail.com on 3 Sep 2011 at 11:26

• Changed state: WontFix