Re: Keyboard generating events

[Andreas S. <an...@sc...>]

* Kjetil Kjernsmo (kj...@kj...) [031106 21:16]:
> My girlfriend just experienced that her keyboard and mouse locked up 
> hard after a few hours' use. It could have been something like that I 
> experienced too, but I did not investigate at that time. Locked hard 
> means that the secondary mouse generates no events, and the LEDs on the 
> keyboard can't be toggled. 

this is something that i experience, too.

i assumed it was my usb hardware which was slighly broken, so i
looked for ways to work around it. your usb setup doesnt seem to
be too stable either, perhaps it is the same problem? however,
here it is mostly the two mice and my keyboard dis- and reappearing.

the problem with reappearing is that the xserver does not reclaim
its hw automatically once it was gone. It does that only on
special events, e.g. when you switch from the console to X.

the Xserver in debian-experimental is able to regrab its hardware
with help of the input.agent from
http://people.debian.org/~warp/evdev/ , since it can react to
events received from a pipe, which the input.agent writes to.

the drawback with the event interface configuration is that it
seems to have problems with mouse keypresses (the pressbutton
event is generated at the same time as the releasebutton event,
making dragging and marking things under X impossible). I still
want to debug this so this is fully usable. the author of the x
event interface can not explain this and never saw this
phenomenon.