linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ajaxas <ajaxas@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Greg KH <gregkh@linuxfoundation.org>
Cc: linux-input@vger.kernel.org
Subject: Re: ALPS touchpad no longer recognizing 'taps' as mouseclick in 3.3-rc3
Date: Mon, 13 Feb 2012 16:28:28 +0700	[thread overview]
Message-ID: <CAKanTDcURNVGZQsNo-=GZ9FQAMzy8o8JPESUj9oGGqPxYLOiig@mail.gmail.com> (raw)
In-Reply-To: <20120213063928.GB10056@core.coreip.homeip.net>

Hi!

I see the problem is solved, but I will reply anyway.

On Mon, Feb 13, 2012 at 1:39 PM, Dmitry Torokhov
<dmitry.torokhov@gmail.com> wrote:
> On Mon, Feb 13, 2012 at 01:19:31PM +0700, ajaxas wrote:
>> Hello
>>
>> On Mon, Feb 13, 2012 at 12:12 PM, Dmitry Torokhov
>> <dmitry.torokhov@gmail.com> wrote:
>> > On Sun, Feb 12, 2012 at 06:22:21PM -0800, Greg KH wrote:
>> >> 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.
>> >
>> > No, there is no need. I am pretty sure pre-3.3 your touchpad worked in
>> > PS/2 compatibility mode; in 3.3 we merged support for native multitouch
>> > protocol so your touchpad works in absolute mode, can support various
>> > gestures (vertical/hrizontal scroll, user-selected sensitivity, etc.)
>> > and is recognozed as a proper touchpad by the entire stack. For some
>> > reason though Gnome has disabled tap to click for touchpads by default.
>> > I do not remember what is the default for KDE.
>> >
>> > Hope this helps.
>> >
>> > --
>> > Dmitry
>> > --
>> > To unsubscribe from this list: send the line "unsubscribe linux-input" in
>> > the body of a message to majordomo@vger.kernel.org
>> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>> Since I'm using the same ALPS touchpad as Greg, I might be of some help here.
>>
>> I don't know how to check whether my touchpad is in absoulte mode or
>> not, but KDE system settings ->  input devices doesn't list any
>> additional touchpads at all, only a mouse. Which affects both mouse
>> and touchpad.
>
> What mouse does it identify? Also, do you have kcm_touchpad module
> installed?
>
> [dtor@dtor-d630 ~]$ rpm -qa "kcm*touchpad*"
> kcm_touchpad-0.3.1-6.fc15.x86_64
> [dtor@dtor-d630 ~]$ locate kcm_touchpad.so
> /usr/lib64/kde4/kcm_touchpad.so

Just mouse, nothing specific.
Can't remeber installing such package, but I don't think my touchpad
must be configured by DE. I strongly believe this should be done via
/etc/X11/xorg.conf.d/ and therefore left DE-independent. My one and
only pain is that I can't configure per-window or per-application
keymap settings via Xorg.

>>
>> Could this be not a DE, but a xorg/driver problem afetr all?
>
> It could but it most likely is as most distributions install and set up
> synaptics X driver by default. I am not sure what DE Greg is using
> though.
>
> --
> Dmitry

Hah, I see. I use archlinux which, as a matter of fact, doesn't
configure synaptics driver or indeed Xorg by default.

Anyway, thank you for your time!

--
Best regards,
Vladimir
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2012-02-13  9:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-12 16:47 ALPS touchpad no longer recognizing 'taps' as mouseclick in 3.3-rc3 Greg KH
     [not found] ` <CAKanTDf908L7XoyuVWGh5oy6L8V0nuPUpReyKTR7FBdQDHjovw@mail.gmail.com>
2012-02-12 17:01   ` ajaxas
2012-02-12 20:12 ` Dmitry Torokhov
2012-02-13  2:22   ` Greg KH
2012-02-13  5:12     ` Dmitry Torokhov
2012-02-13  6:19       ` ajaxas
2012-02-13  6:39         ` Dmitry Torokhov
2012-02-13  6:48           ` Greg KH
2012-02-13  9:28           ` ajaxas [this message]
2012-02-13  6:38       ` Greg KH

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='CAKanTDcURNVGZQsNo-=GZ9FQAMzy8o8JPESUj9oGGqPxYLOiig@mail.gmail.com' \
    --to=ajaxas@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-input@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 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).