On Wed, Jun 30, 2010 at 13:53:42 +0100, Ben Whyall wrote:
Attached are the files you asked for. The period when it happened
is towards the bottom of the xinputtest.txt file. It's difficult to
be more precise as it jumped round 6 or 7 times before allowing me
ot move to correct workspace and stop the trace.
Weird, the only thing that may be suspicious is devices 10 and 11
(Microsoft 2.4GHz Transceivers) switching around from keyboard to mouse
and vice versa halfway in the trace:
And now 10 is a slave keyboard and 11 is a slave pointer..
EVENT type 1 (DeviceChanged)
device: 2 (11)
reason: SlaveSwitch
Reporting 7 classes:
Class originated from: 11
Buttons supported: 13
Button labels: Button Left Button Middle Button Right Button Wheel Up Button Wheel Down Button Horiz Wheel Left Button Horiz Wheel Right Button Side Button Extra Button Unknown Button Unknown Button Unknown Button Unknown
Button state:
Class originated from: 11
Keycodes supported: 248
Class originated from: 11
Detail for Valuator 0:
Label: Abs X
Range: -1.000000 - -1.000000
Resolution: 1 units/m
Mode: relative
Class originated from: 11
Detail for Valuator 1:
Label: Abs Y
Range: -1.000000 - -1.000000
Resolution: 1 units/m
Mode: relative
Class originated from: 11
Detail for Valuator 2:
Label: Abs Gas
Range: -1.000000 - -1.000000
Resolution: 1 units/m
Mode: relative
Class originated from: 11
Detail for Valuator 3:
Label: Abs Brake
Range: -1.000000 - -1.000000
Resolution: 1 units/m
Mode: relative
Class originated from: 11
Detail for Valuator 4:
Label: Abs Misc
Range: -1.000000 - -1.000000
Resolution: 1 units/m
Mode: relative
If that's not it then the problem may not be recorded in the trace. Not
sure how to debug then.
Cheers,
Julien