On Tue 16 Oct 2007, Tom Epperly wrote:
> >  
> Here is what a single click yields:
> 
> ButtonPress event, serial 27, synthetic NO, window 0x2600001,
>    root 0x7d, subw 0x0, time 76706834, (122,108), root:(258,990),
>    state 0x0, button 1, same_screen YES
> 
> ButtonPress event, serial 27, synthetic NO, window 0x2600001,
>    root 0x7d, subw 0x0, time 76706834, (122,108), root:(258,990),
>    state 0x100, button 1, same_screen YES
> 
> ButtonRelease event, serial 27, synthetic NO, window 0x2600001,
>    root 0x7d, subw 0x0, time 76706954, (122,108), root:(258,990),
>    state 0x100, button 1, same_screen YES
> 
> ButtonRelease event, serial 27, synthetic NO, window 0x2600001,
>    root 0x7d, subw 0x0, time 76706954, (122,108), root:(258,990),
>    state 0x0, button 1, same_screen YES

I get the exact same thing since updating everything, resulting in these
versions (these are the relevant packages, I hope):

xserver-xorg                    1:7.3+2
xserver-xorg-core               2:1.4-3
xserver-xorg-input-all          1:7.3+2
xserver-xorg-input-evdev        1:1.2.0~git20070819-3
xserver-xorg-input-mouse        1:1.2.2-6

I note that Tom deleted "one of these input sections", and deleted the
one referencing /dev/psaux. When I do that, I also don't see any change.
However, if I delete the /dev/input/mice section and leave the psaux
one, then behaviour is as it should be!  And I happen to have an USB
mouse, which appears to work as an psaux device as far as X is
concerned...

Another curious thing is that xev shows that the mouse buttons are
repeated, but NOT the scroll wheel events, which are basically also
mouse buttons...

I would understand this change of behaviour if it happened after a
kernel upgrade, causing the psaux "emulated"(?) mouse to be mixed with
the USB mouse. However, I had not rebooted after the upgrade of X et.al, 
and experienced the problem then. (I have since rebooted with another
kernel to see if that would help, but it didn't.)


Paul Slootman



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to