Bug#855465: marked as done (taps intermittently missed on AlpsPS/2 ALPS GlidePoint touchpad)

["Debian Bug Tracking System" <owner@bugs.debian.org>]

Your message dated Mon, 16 Jul 2018 15:56:30 +0200
with message-id <20180716135630.GA28246@polynomio>
and subject line Re: Bug#855465: taps intermittently missed on AlpsPS/2 ALPS GlidePoint touchpad
has caused the Debian Bug report #855465,
regarding taps intermittently missed on AlpsPS/2 ALPS GlidePoint touchpad
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
855465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855465
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

--- Begin Message ---

• To: submit@bugs.debian.org
• Subject: taps intermittently missed on AlpsPS/2 ALPS GlidePoint touchpad
• From: Jyotirmoy Bhattacharya <jyotirmoy@jyotirmoy.net>
• Date: Sat, 18 Feb 2017 23:44:45 +0530
• Message-id: <CALc-kK5R5RLdx30C=06vkBpsWYToYF6dNmF0YxmNfk3XcV03PQ@mail.gmail.com>

Package: libinput10

Version: 1.6.0-1

On my AlpsPS/2 ALPS GlidePoint touchpad with tap-to-click enabled, taps sometimes register as clicks and sometimes don't.

On running

sudo libinput-debug-events --enable-tap --device /dev/input/event2

sometimes taps produce events like

event2   POINTER_BUTTON   +21.93s    BTN_LEFT (272) pressed, seat count: 1
event2   POINTER_BUTTON   +22.20s    BTN_LEFT (272) released, seat count: 0

but sometimes they produce nothing at all and there is no clear pattern of when a tap succeeds.

On the other hand with libinput built from the current git (6b561d45) things work as expected and

sudo ./event-debug --enable-tap --device /dev/input/event2

consistently generates events for taps.

Jyotirmoy Bhattacharya

--- End Message ---

--- Begin Message ---

• To: Jyotirmoy Bhattacharya <jyotirmoy@jyotirmoy.net>, 855465-close@bugs.debian.org
• Subject: Re: Bug#855465: taps intermittently missed on AlpsPS/2 ALPS GlidePoint touchpad
• From: Hector Oron <zumbi@debian.org>
• Date: Mon, 16 Jul 2018 15:56:30 +0200
• Message-id: <20180716135630.GA28246@polynomio>
• In-reply-to: <CALc-kK5R5RLdx30C=06vkBpsWYToYF6dNmF0YxmNfk3XcV03PQ@mail.gmail.com>
• References: <CALc-kK5R5RLdx30C=06vkBpsWYToYF6dNmF0YxmNfk3XcV03PQ@mail.gmail.com>

On Sat, Feb 18, 2017 at 11:44:45PM +0530, Jyotirmoy Bhattacharya wrote:
> Package: libinput10
> Version: 1.6.0-1
> 
> On my AlpsPS/2 ALPS GlidePoint touchpad with tap-to-click enabled, taps
> sometimes register as clicks and sometimes don't.
> 
> On running
> 
> sudo libinput-debug-events --enable-tap --device /dev/input/event2
> 
> sometimes taps produce events like
> 
> event2   POINTER_BUTTON   +21.93s    BTN_LEFT (272) pressed, seat count: 1
> event2   POINTER_BUTTON   +22.20s    BTN_LEFT (272) released, seat count: 0
> 
> but sometimes they produce nothing at all and there is no clear pattern of
> when a tap succeeds.
> 
> On the other hand with libinput built from the current git (6b561d45)
> things work as expected and
> 
> sudo ./event-debug --enable-tap --device /dev/input/event2
> 
> consistently generates events for taps.
> 
> Jyotirmoy Bhattacharya

I am closing this bug, since there is no input to Andreas question and looks like it might be fixed in later version.
Could you please reopen if the issue persists?

Attachment: signature.asc
Description: PGP signature

--- End Message ---