Most recent kernel where this bug did not occur: 2.4.26 Distribution: Slackware 10.0 Hardware Environment: Barton 2500+ and MS intellimouse optical USB 5 button mouse Software Environment: KDE 3.4.3 Problem Description: at dmesg it shows: psmouse.c: Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. and cursor starts to auto click everything on my desktop i had this problem when i decide to use 2.6.x instead of 2.4.x i first used 2.6.12.3 and same problem and now with 2.6.13.4 the same i tried all possible protocols in X including "ExplorerPS/2" but no effect i also tried with gpm or without gpm but the problem persists Steps to reproduce: press any key or combination of keys on keyboard the same time as you move very fast your mouse Ex. when i press CTRL`C or CTRL`V to copy paste something and i move my cursor the same time this happens
I have a very similar problem. Mouse become crazy and click everywhere in the screen. But it is not important if I'm using keyboard in the meantime or not, neighter it is important if I'm using mouse slowly or fast.. I'm using Ubuntu Edgy 6.10 but I have the same problem with Feisty Fawn beta (with the last kernel). In my kern.log there are a lot of this kind of rows: Mar 28 14:49:37 attorianzo-desktop kernel: [17179662.100000] psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. I'm using a logitech mouse
In my case, after i searched all the net and forums, i think the problem was from my keyboad driver(standard keyboard with the default slack drivers), the kbd driver. Somehow it conflicts with the mouse. the solution problably is to install the latest kbd driver, or look into xorg.conf and see what driver are you using. I never tried this though because at the time i found this solution slackware 11 was released and i have done a fresh install of the new slack and after upgraded to the latest kernel no problems appeared with my mouse .
Can everyone affected please test with the latest kernel as well. Thanks.
Please reopen this bug if it's still present with kernel 2.6.22.