AW: QAW: AW: Levovo trackpoint come delayed (reproducable with xev)

["Paul Maier" <svn-user at web dot de>]

> > -----Ursprüngliche Nachricht-----
> > On 29/01/2012 13:36, Paul Maier wrote:
> > > I did several tests and now I can send you a detailed report:
> >
> > Thanks for taking the time to do that.
> >
> > > Notes:
> > > - I found that file at C:\Program Files\Synaptics\SynTP\TP4table.dat and I have added the
> > >   lines from FAQ, but that didn't change anything.
> >
> > Hmm... the sixth item in the rule (which I'm guessing is a windows classname),
> > doesn't look like it's correct anymore.
> >
> > I'm not sure if that's related to your problems, but I've fixed the FAQ.
> >
> > >   The following description is done with the patched version of the file.
> > > - Your download reference "[1]" seems to be missing in your mail, therfore I used
> > >   XWin.20110803-git-a493c0465e56ce0b instead, that I still had from our last debugging.
> >
> > Yes, sorry about that. I meant to write:
> >
> > [1] ftp://cygwin.com/pub/cygwinx/XWin.20120129-git-45e67e363e19a481.exe.bz2
> >
> > Can you try again with the latest snapshot, there should be some additional
> > numbers after the WM_MOUSEWHEEL messages which should help with debugging ths
> > problem.
> >
> > > - I hold the button down and shift the trackpoint up and down.
> > >   xterm shows no scrolling movement at all.
> > > - Log in /var/log/xwin/XWin.0.log during this:
> > >   a) still comes at the moment when I shift the trackpoint up and down,
> > >   b) but it doesn't look regular any more:
> > >      There are MUCH more lines
> > >        winMouseButtonsSendEvent: iEventType: 4, iButton: 5, nEvents 2
> > >        winMouseButtonsSendEvent: iEventType: 5, iButton: 5, nEvents 2
> > >      and only a few lines
> > >        winWindowProc - WM_MOUSEWHEEL
> > >      in between.
> > >      Looks like this:
> > > [   473.447] winMouseButtonsSendEvent: iEventType: 5, iButton: 5, nEvents 2
> > > [   473.447] winMouseButtonsSendEvent: iEventType: 4, iButton: 5, nEvents 2
> >
> > This  looks a bit like the trackpoint is sending us a WM_MOUSEWHEEL for a much
> > larger mouse movement (which we need to break down into multiple button 5
> > press/releases)
> >
> > >      Maybe this is an interesting section, it contains an "EQ overflowing":
> > > [   350.612] [mi] EQ overflowing. The server is probably stuck in an infinite loop.
> >
> > This means that the events are being generated faster than the server can
> > process them.
> >
> > > - I release the button. At the moment when I release the button, the xterm jumps to a new
> position.
> > >   During this, there is absolutely no output to /var/log/xwin/XWin.0.log.
> >
> > So it sounds almost like the X server is being prevented from processing X
> > events until the mouse button is released.
> >
> > It might be interesting to try as separate test with some application which
> > constantly draws to it's window (like ico), if that continues drawing when the
> > trackpoint button is down.
> 
> 
> 
> Hi Jon,
> 
> here a log of my recent tests. The most interesting point is the last.
> 
> 1. I modified file C:\Program Files\Synaptics\SynTP\TP4table.dat according to new FAQ and reboot PC.
>    -> No change of behaviour.
> 
> 2. Download XWin.20120129-git-45e67e363e19a481.exe.bz2.
>   /bin/startxwin -- /bin/XWin.20120129-git-45e67e363e19a481.exe -logverbose 3 -clipboard -
> emulate3buttons 100 -nounixkill -nowinkill -xkboptions nbsp:level3
>    -> Doesn't start. Error message on the console is:
> 
> giving up.
> /bin/startxwin:  No such file or directory (errno 2):  unable to connect to X server
> /bin/startxwin:  No such process (errno 3):  Server error.
> 
>    -> No output at all to file /var/log/xwin/XWin.0.log.
> 
> 3. I took above startxwin command line and replace XWin.20120129-git-45e67e363e19a481.exe by
> XWin.20110803-git-a493c0465e56ce0b.exe
>    -> Immediately starts. All further tests with (old) XWin.20110803-git-a493c0465e56ce0b.exe.
> 
> 4. Today I couldn't get to the broken, jumpy behaviour by scrolling a Windows dialog.
>    So this is not the breaking condition as I previously meant.
>    But after some time, the scrolling behaviour breaks and xterm scrolls in jumpy way.
>    Sorry, I have no glue what's the condition that breaks it.
>    After reboot of PC it scrolls fine. Any work of 1 minute or so seems to break smooth scrolling.
> 
> 5. Then I started ico.
>    -> While ico runs, xterm scrolls fine and smooth. As soon as I stop ico, xterm scrolls jumpy.
>    -> Pressing the trackpoint button has no effect to ico. It keeps painting fine eather way.
> 
> Regards,
>   Paul
> 

more tests:

6. I started ico with -sleep 1
   ico -sleep 1
   I constantly hold the trackpoint button down and scroll the xterm.
   -> I observe jump scrolling movements every second, one jump each second.
      xterm jump scrolls exactly at the time when ico refreshes

7. close ico, start xpdf
   -> xpdf and xterm both have broken = jumpy scroll

8. start ico
   -> both xpdf and xterm both scroll fine and smooth

9. stop ico, start ico -sleep 1
   -> ico -sleep 1 starts, but doesn't paint anything. I do several tests.
   -> ico without sleep option starts fine.
   close xpdf
   -> ico -sleep 1 starts, but doesn't paint anything. I do several tests.
   -> ico without sleep option starts fine.
   -> ico -sleep 1 starts and repaints in 1 second rhythm. Fine.
   => an open xpdf seems to break "ico -sleep 1", and "ico -sleep 1" can be repaired
      by closing xpdf and then once running "ico" without options. Very weird.

Regards,
  Paul



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/