linux-kernel - Re: ALPS touchpad no longer recognizing 'taps' as mouseclick in 3.3-rc3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120213022221.GF25382@kroah.com>
Date:	Sun, 12 Feb 2012 18:22:21 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc:	linux-input@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: ALPS touchpad no longer recognizing 'taps' as mouseclick in
 3.3-rc3

On Sun, Feb 12, 2012 at 12:12:36PM -0800, Dmitry Torokhov wrote:
> Hi Greg,
> 
> On Sun, Feb 12, 2012 at 08:47:28AM -0800, Greg KH wrote:
> > Hi,
> > 
> > This problem has been since 3.3-rc1, but I only now am getting around to
> > reporting it, sorry about that.
> > 
> > In 3.3-rc3, my alps touchpad isn't recognizing a tap on the touchpad as
> > a mouse click.  Is there a new Kconfig option that I need to enable?
> > 
> > My /proc/bus/input/devices entry for this thing is:
> > I: Bus=0011 Vendor=0002 Product=0008 Version=7326
> > N: Name="AlpsPS/2 ALPS DualPoint TouchPad"
> > P: Phys=isa0060/serio1/input0
> > S: Sysfs=/devices/platform/i8042/serio1/input/input6
> > U: Uniq=
> > H: Handlers=mouse1 event6 
> > B: PROP=8
> > B: EV=b
> > B: KEY=e420 70000 0 0 0 0
> > B: ABS=260800001000003
> > 
> > Is there anything else you need me to report to help track this down?
> > 
> 
> Please make sure you have xorg-x11-drv-synaptics installed and then
> check if tap to click is enabled in your DE. I think Gnome for some
> reason has it off my default.

Is this a new thing for the 3.3 kernel?  I ask as 3.2 and older kernels
work just fine this way.  I can do a 'git bisect' to track it down to a
specific patch if that will help out.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/