On Wed, Dec 22, 2010 at 06:50:25PM +0530, shirish शिरीष wrote: > In-line :- > > On Wed, Dec 22, 2010 at 16:25, Julien Viard de Galbert > <julien@vdg.blogsite.org> wrote: > > tags 607242 + moreinfo > > thanks > > > > On Wed, Dec 22, 2010 at 10:06:58AM +0100, Julien Viard de Galbert wrote: > >> [...] > >> I'm not an input expert, so I don't have much idea on that. > >> > >> For some reason (maybe the size it's more than 32k, which is huge for an > >> email) your report did not make it to the debian-x mailing list, so > >> maybe now that I'm replying an expert will see it ;) > > > Thank you. Didn't understand the bit about 32kb thing. Do you mean I > write a lot or did the font-size make the bug-report big. More clarity > here would be good . > It's mainly the size of the Xorg.0.log file, you could have removed a few of the repeated lines at the end. > > Got an expert advice ;) > > > > Apparently "dropping event due to full queue" indicates that the kernel > > never sends EV_SYN for this device. The driver queue the button and > > motion events until it gets the sync, so with no sync, the queue gets > > full... > > > > You should install evtest, and launch it once your mouse start to behave > > wrong. (to find the device you have to give in parameter you can look at > > your Xorg.0.log, it was /dev/input/event5 in the log you sent. > > so launch > > # evtest /dev/input/event5 > > move your mouse a little, and send us the output. > > Thank you, already installed evtest and now waiting for the mouse to > behave as it behaves :P , would try to send the data as and when it > becomes possible. Would you say below is a good idea > > $evtest /dev/input/event5 > mouse.txt > > Just wondering, because when that happens sometimes the desktop also > freezes or some other things happen. I could go to VT1 (CTRL+TAB+1)and > fire that up from there and let it do it work. Also after firing it > up, when I'm sure the data is captured how do I make it stop, do I do > a CTRL+C or some other keyboard combo so the data is safe and > pristine. A better set of instructions would go a long way in helping > me deliver the data that would be needed to pin-point what is wrong. I > wanna be in a position to be able to generate the data, if desktop > freezes or anything else, save that data, shutdown the system and > restart and still the data is there. Then will send you. Because of > the freakishness of the mouse, I'm not able to trust the GUI and the > system as much as I would like. > Yes, launching evtest form a VT should do it. but then you're going to have a huge file were all the firsts lines will be normal, basically what we are trying to find is if the EV_SYN event is still send. This event is displayed as "-------------- Report Sync ------------" so you should probably cut the file and remove the middle part where the sync events look normal. > > That would help understanding what's wrong. > > Yup. > > > Thanks for your time, > > > > Lastly > > -- > > Julien Viard de Galbert <julien@vdg.blogsite.org> > > http://silicone.homelinux.org/ <julien@silicone.homelinux.org> > > Lastly, NC is my signature means non-commercial, I don't know why > people think of non-commercial as non-free. I have seen many an > art-work and literature under the non-free license and nobody raises > an eyebrow. But as you said that's an entirely different matter so let > it rest. :) > Just because non-commercial is a restriction, so it's non-free with regards to debian criteria at least, and some other agrees with that ;) But of course you are perfectly free to use it for your signature :) -- Julien Viard de Galbert <julien@vdg.blogsite.org> http://silicone.homelinux.org/ <julien@silicone.homelinux.org> GPG Key ID: D00E52B6 Published on: hkp://keys.gnupg.net Key Fingerprint: E312 A31D BEC3 74CC C49E 6D69 8B30 6538 D00E 52B6
Attachment:
signature.asc
Description: Digital signature