linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Douglas Christman <douglaschristman@gmail.com>
Cc: linux-input@vger.kernel.org,
	"Hans de Goede" <hdegoede@redhat.com>,
	"Pali Rohár" <pali.rohar@gmail.com>
Subject: Re: ALPS DualPoint double click bug
Date: Sun, 19 Jul 2015 23:54:46 -0700	[thread overview]
Message-ID: <20150720065446.GA13879@dtor-ws> (raw)
In-Reply-To: <CANuv8QyimosOLwtvLpSLjjEk2SemgxTrZDJxWnzQG-M3q20CHg@mail.gmail.com>

On Sun, Jul 19, 2015 at 09:29:26AM -0400, Douglas Christman wrote:
> Hello all,
> 
> Kernel v4.1 introduces a bug for my laptop's (Toshiba Tecra A10)
> touchpad.  Clicking twice only registers as a single click (and three
> clicks are needed to double-click).
> 
> The touchpad shows up as 'AlpsPS/2 ALPS DualPoint' in dmesg.
> Bisecting drivers/input/mouse suggests that commit 92bac83d introduced
> the bug.
> 
> Please let me know if I can provide any other information that would be useful.
> 
> Filed as bug #101701 on bugzilla.

Let's add a few people...

-- 
Dmitry

  reply	other threads:[~2015-07-20  6:54 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-19 13:29 ALPS DualPoint double click bug Douglas Christman
2015-07-20  6:54 ` Dmitry Torokhov [this message]
2015-07-20  7:25   ` Pali Rohár
2015-07-21  3:00     ` Douglas Christman
2015-07-21  7:12       ` Pali Rohár
2015-07-21 23:51         ` Douglas Christman
2015-07-22  7:21           ` Pali Rohár
2015-07-22 15:08             ` Benjamin Tissoires
2015-07-22 17:26               ` Stephen Chandler Paul
2015-07-23  9:31               ` Hans de Goede
2015-07-25 14:07                 ` Douglas Christman
2015-07-27 16:40                   ` Hans de Goede
2015-07-27 23:38                     ` Douglas Christman
2015-07-29 20:45                       ` [PATCH 0/1] Alps button reporting bugfix cpaul
2015-07-29 20:45                         ` [PATCH 1/1] Input - alps: Fix button reporting on the V2 Alps protocol cpaul
2015-07-29 21:01                           ` Dmitry Torokhov
2015-07-30  7:52                           ` Pali Rohár
2015-07-30 13:51                           ` Hans de Goede
2015-07-30 14:11                             ` Pali Rohár
2015-07-30 14:18                               ` Hans de Goede
2015-07-30 14:28                                 ` Pali Rohár
2015-07-30 14:32                                   ` Pali Rohár
2015-07-30 14:38                                     ` Hans de Goede
2015-07-30 14:45                                       ` Pali Rohár
2015-07-30 14:17                       ` ALPS DualPoint double click bug Hans de Goede
2015-07-30 14:46                         ` Pali Rohár
2015-07-30 15:00                           ` Hans de Goede
2015-07-30 15:49                             ` Pali Rohár
2015-07-31  8:12                               ` Hans de Goede
2015-07-31 21:12                             ` Douglas Christman
2015-07-31 21:17                               ` Pali Rohár
2015-08-01  6:48                                 ` Hans de Goede
2015-07-21 17:12       ` Dmitry Torokhov

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=20150720065446.GA13879@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=douglaschristman@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-input@vger.kernel.org \
    --cc=pali.rohar@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).