Red Hat Bugzilla – Bug 437609
synaptics touchpad tap not working
Last modified: 2018-04-11 07:05:40 EDT
Description of problem:
Tap on touchpad is not working at all - all other settings seem to work fine.
How reproducible: every time
Additional info: let me know what else you need, running fully updated rawhide
According to list emails this was recently changed to be default behavior (no
tap configured). You apparently need to add tap configuration to the xorg.conf.
There is a pretty good wiki of synaptics configuration stuff here:
See comments at https://bugzilla.redhat.com/show_bug.cgi?id=434669
My comment shouldn't have sounded like an authoritative response, its just a
suggestion as to why and something to look at.
adding to xorg.conf works fine:
Option "TapButton1" "1"
Option "TapButton2" "2"
would like to register my disapproval for the default setting though :)
another note is that gsynaptics settings for tap don't work until those settings
have been added
+1 to Dan's comment..I've grown to rely on tap working out of the box :)
*** Bug 437702 has been marked as a duplicate of this bug. ***
(In reply to comment #4)
> +1 to Dan's comment..
+1 from me as well
And seems thimm doesn't like it as well -- for his opinion see Bug 437702, which
looked like a dupe of this one (and thus I marked it as one).
Note: the bug has a lot of good informations. Quoting one
>For anyone hitting this bug report and in need of restoring the upstream
>behaviour, please add
> Option "RTCornerButton" "2"
> Option "RBCornerButton" "3"
> Option "TapButton1" "1"
> Option "TapButton2" "2"
> Option "TapButton3" "3"
Reassiging to ajax, as he according to Bug 437702 Comment 1 actually did the
change in the driver
I have the same problem and partly managed to solve it by by adding an
InputDevice section for the touchpad to xorg.conf as described.
Unfortunately the default touchpad setting is restored after a suspend/resume
cycle (on this IBM T41 Thinkpad). That means that I get the opposite behaviour
of what I have configured i.e. EdgeScroll works while taps doesn't.
Just adding my "+1" to restoring previous behaviour since tapping on touchpads
has come to be an expected one. I wouldn't have been as vehement in restoring
the default if there was a GUI option to changing it. As it is, gsynaptics
doesn't seem to offer that switch control.
Also +1 from me to turn tapping by default on.
Tap worked for my be default in Preview x86_64 Live. It does not scroll (two-finger, on a macbook this is
really needed) but it does allow single and double taps.
(In reply to comment #8)
> I have the same problem and partly managed to solve it by by adding an
> InputDevice section for the touchpad to xorg.conf as described.
> Unfortunately the default touchpad setting is restored after a suspend/resume
> cycle (on this IBM T41 Thinkpad). That means that I get the opposite behaviour
> of what I have configured i.e. EdgeScroll works while taps doesn't.
I see that too (Thinkpad T43, synaptics-0.14.6-7.fc9.i386): taps work on first
boot, but not after suspend/resume. Synclient still reports "TapButton1 = 1", etc.
*** Bug 442798 has been marked as a duplicate of this bug. ***
*** Bug 439672 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 439386 ***
As suggested, I've modified xorg.conf but still tapping doesn't work.
Can someone look at this xorg.conf and tell where I've gone wrong?
Option "Device" "/dev/input/mice"
Option "Protocol" "auto-dev"
Option "Emulate3Buttons" "yes"
Option "LeftEdge" "0"
Option "RightEdge" "850"
Option "TopEdge" "0"
Option "BottomEdge" "645"
Option "MinSpeed" "0.5"
Option "MaxSpeed" "1.5"
Option "AccelFactor" "0.06"
Option "FingerLow" "25"
Option "FingerHigh" "35"
Option "MaxTapTime" "150"
Option "MaxTapMove" "300"
Option "MaxDoubleTapTime" "125"
Option "FastTaps" "1"
Option "RTCornerButton" "2"
Option "RBCornerButton" "3"
Option "TapButton1" "1"
Option "TapButton2" "2"
Option "TapButton3" "3"
Option "LockedDrags" "1"
Option "VertScrollDelta" "20"
Option "HorizScrollDelta" "20"
Option "SHMConfig" "on"
And what happens after suspend/resume, it reverts to default again with no
I ve tryed it and after suspend/resume, tapping stops to work again
(In reply to #bug 437702 comment #1)
> OK, looks like this one was intentional:
> * Mon Mar 10 2008 Adam Jackson <email@example.com> 0.14.6-4
> - synaptics-0.14.6-tap-to-click.patch: Disable tap to click by default in
> the name of accessibility.
> I'm not sure this is really a good idea, since this is unexpected behaviour,
> both by upstream documentation as well as shipped documentation (e.g. the patch
> would have had to patch the man pages for example as well).
> Instead it could be something that the gdm login screen could be turning on/off
> along with all the other accessibility items. Also if you really want the
> default to change then do it in teh created xorg.conf, not hardwired in the
> sources where no one will be seraching for this change in behaviour. If F9 ships
> out that way you will get lots of duplicates to this bug report.
OK, so we have 5 reports out of a total of 56 reports of all synaptics bug
reports ever filed. Not the bug raining day, but still a very unpleasant
experience with F9 and tapping.
Fixing it is easy, here is the patch
--- synaptics.spec~ 2008-03-28 20:28:10.000000000 +0100
+++ synaptics.spec 2008-04-10 19:45:27.000000000 +0200
@@ -4,3 +4,3 @@
Summary: Synaptics Touchpad Driver
@@ -14,3 +14,2 @@
@@ -55,3 +54,2 @@
-%patch2 -p1 -b .tap
%patch3 -p1 -b .polldelay
@@ -89,2 +87,5 @@
+* Thu Apr 10 2008 Axel Thimm <Axel.Thimm@ATrpms.net> - 0.14.6-8
+- Reenable tap to click.
* Fri Mar 28 2008 Rex Dieter <firstname.lastname@example.org> 0.14.6-7
And for the ones too lazy to rebuild I've placed the fixed synaptics package in
ATrpms' testing area or you can get it directly from
Bought my sanity back.