xmonad and xkb features

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Just use xmonad for a few minutes

What is the expected output? What do you see instead?
I use a xkb feature that allows one to press Ctrl-Shift-NumLock and then
control the mouse with the keyboard. After a while, that feature just stops
working. I can restart it, although it will be disabled again after some
time. I don't have that problem with the other window manager I use
(metacity, I think).

What version of the product are you using? On what operating system?
I'm using version 0.7 in Ubuntu 8.04. The problem already existed in xmonad
0.6. I do have the same problem if I config xmonad not to use any contrib
extensions. I'm attaching my xorg.conf.

Original issue reported on code.google.com by mauricio...@gmail.com on 2 Sep 2008 at 1:25

Attachments:

• xorg.conf

[GoogleCodeExporter]

Are you absolutely certain that this doesn't happen in metacity?  I've read 
that the
keyboard mouse control feature in X.org does not work very well, and makes me 
wonder
if this is really an xmonad bug.

Original comment by SpencerJ...@gmail.com on 11 Sep 2008 at 8:44

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Yes. I used a computer without a mouse for almost two months. At that time I 
tried a
lot to use xmonad, but always had to go back to metacity (or maybe compiz. I'm 
not
sure since I never activated desktop effects, but maybe compiz was already 
active).
There, I never had that problem. I can say that for those months I used both 
xmonad
and gnome default window manager half of the time each.

However, I also would guess that this is not an xmonad bug, but some small x.org
problem that xmonad do not address, while other window managers do.

Original comment by mauricio...@gmail.com on 11 Sep 2008 at 12:43

[GoogleCodeExporter]

I think this is the problem that gave X keyboard mouse control its bad name:

http://www.math.missouri.edu/~stephen/software/bugfix-for-mousekeys

It's solved for a long time now. After a lot of testing, I have found no other 
window
manager with this same problem. I think we should consider this a xmonad 
problem.

Also: if I set keyboard mouse control using, for instance, xkbset in xmonad.hs, 
just
before calling 'xmonad', the keyboard control is already turned off when the 
blank
screen appears.

Original comment by mauricio...@gmail.com on 23 Oct 2008 at 10:28

[GoogleCodeExporter]

I'm now using xmonad 0.8 in Ubuntu 8.10. The problem is still there, in two 
different
computers with different hardware.

Maybe the priority of this should be raised. Not because of the problem itself, 
since
very few people use a computer without a mouse, but because keyboard is 
probably the
major issue in xmonad, and solving this bug may help solving others.

Original comment by mauricio...@gmail.com on 10 Nov 2008 at 4:26

[GoogleCodeExporter]

This problem seems no to be a bug of xmonad, but the feature of XKB.
In default, the MouseKeys of XKB expires in 120 second (try "xkbset q exp").
You can change this expire time by executing "xkbset exp [TIME_IN_SECONDS]"
Also, you can set MouseKeys not to expire by executing "xkbset exp m".

But however, xkbset seems not to work in Ubuntu 8.04.
So I updated to Ubuntu 8.10, then now xkbset works.

Original comment by hpn...@gmail.com on 13 Nov 2008 at 11:44

[GoogleCodeExporter]

Interesting! As I said, I only have this problem with xmonad, never with other 
window
managers. However, it seems I never left the mouse for 120 seconds outside 
xmonad.
After 'xkbset exp =m' everything works as expected.

Thanks! Problem solved.

Original comment by mauricio...@gmail.com on 14 Nov 2008 at 2:21

[GoogleCodeExporter]

Original comment by SpencerJ...@gmail.com on 4 Mar 2009 at 7:51

• Changed state: Invalid