All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	linux-input@atrey.karlin.mff.cuni.cz, zaitcev@redhat.com
Subject: Re: Fix sudden warps in mousedev
Date: Mon, 26 Mar 2007 14:42:06 -0700	[thread overview]
Message-ID: <20070326144206.93805eeb.zaitcev@redhat.com> (raw)
In-Reply-To: <d120d5000703261230h1724e453je2c14769fc099ad3@mail.gmail.com>

On Mon, 26 Mar 2007 15:30:42 -0400, "Dmitry Torokhov" <dmitry.torokhov@gmail.com> wrote:

> Regarding the synaptics driver and scroll problem. Yesterday I
> scrolled twice through entire Remarque's "Spark of Life" off lib.ru
> (once with 0.14.2 and once with latest git pull) and did not see any
> scrollbar getting "stuck". Could it be newer xorg problem instead of
> individual driver problem? I am using whatever xorg was installed in
> FC3 which is somewhat dated... Also, could it be that the scroll issue
> happens only in a certain application?

It's not a "scroll" issue. The issue is that the "up" event is getting
lost. It can be observed with any GUI elements, such as buttons.
However, since the event is delivered upon any motion, there's no
harm done with a button. Needless to say, this is not application
specific. It may be GNOME specific though.

FC-3 is far too old to be a good reference. I don't even know if it
has a usable synaptics module in its pre-modular X. You may be looking
at very different software stack.

I don't think that you need to concern yourself with this too much
at present. If X11 people (e.g. Kristian) present evidence that kernel
fails to deliver an event, then we'll look at it. However it might
help if evtest continued to work when X11 reads from /dev/input/eventN.
It was an unpleasant surprise that it doesn't.

-- Pete

  reply	other threads:[~2007-03-26 21:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-24  7:16 Fix sudden warps in mousedev Pete Zaitcev
2007-03-24  7:16 ` Pete Zaitcev
2007-03-25  5:34 ` Dmitry Torokhov
2007-03-25 18:19   ` Pete Zaitcev
2007-03-26  3:19     ` Dmitry Torokhov
2007-03-26 19:17       ` Pete Zaitcev
2007-03-26 19:30         ` Dmitry Torokhov
2007-03-26 21:42           ` Pete Zaitcev [this message]
2007-03-27  1:14             ` Dmitry Torokhov
2007-03-27 15:14               ` Chuck Ebbert
2007-03-27 15:46                 ` Dmitry Torokhov
2007-03-27 16:04                   ` Chuck Ebbert
2007-03-27 16:19                     ` Dmitry Torokhov
2007-03-28 20:51                       ` Matt Keenan
2007-04-11 21:51               ` Peter Osterlund

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070326144206.93805eeb.zaitcev@redhat.com \
    --to=zaitcev@redhat.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.