Mouse movement events sent after mouse clicks even if the mouse does not move -> fixed after 3.2.4

[Sam Morris]

Related to the mouse movement issues I mentioned in #4086 the first comment: when I click a mouse button, the guest receives a button press/release event, followed immediately by a motion event, even though the mouse is not being moved.

The difference is that, now I'm using 2.2.4, the motion even occurs *after* the button events. This still results in annoying side-effects such as text being selected when clicking on a gnome-terminal window (since it thinks I just dragged the mouse pointer, I assume).

This can be observed in xev:

ButtonPress event, serial 33, synthetic NO, window 0x2000001,
    root 0x108, subw 0x0, time 4546735, (51,6), root:(421,441),
    state 0x10, button 1, same_screen YES

MotionNotify event, serial 33, synthetic NO, window 0x2000001,
    root 0x108, subw 0x0, time 4546735, (51,6), root:(421,441),
    state 0x110, is_hint 0, same_screen YES

ButtonRelease event, serial 33, synthetic NO, window 0x2000001,
    root 0x108, subw 0x0, time 4547431, (51,6), root:(421,441),
    state 0x110, button 1, same_screen YES

MotionNotify event, serial 33, synthetic NO, window 0x2000001,
    root 0x108, subw 0x0, time 4547431, (51,6), root:(421,441),
    state 0x10, is_hint 0, same_screen YES

Running evtest on the input device corresponding to the mouse device only shows button events; the motion events are not present. If I remove the vboxmouse device from the X server then the spurious motion events go away, so I guess the problem lies there.

[Michael Thayer]

Reproduced and fixed in SVN. The new code successfully passes on your testcase.

[Sam Morris]

Yup, this is fixed in 3.0.0, I guess it can be closed?

Thanks btw :)

[Frank Mehnert]

Thanks for the feedback!

[Sam Morris]

I am still seeing this with VirtualBox 3.2.0.

[Frank Mehnert]

Confirmed.

[Michael Thayer]

It should be squashed again now. Sorry about that.