Red Hat Bugzilla – Bug 115612
FC2 doesn't register clicks on laptop touchpad
Last modified: 2007-11-30 17:10:36 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040115
Description of problem:
After a clean install of FC2 test 1, tapping on the laptop's touchpad
does not register a mouse click. Using the actual mouse buttons works
fine for all six buttons; it's just tapping the touchpad that doesn't
This did work in FC1 release.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot into KDE, Gnome, or failsafe
2. Tap mousepad.
3. Click mouse button.
Actual Results: No response when tapping touch pad; click registered
when using mouse button.
Expected Results: click registered using either the touch pad or
The laptop is a VPR Matrix 175B4. The mouse is configured as a
generic ps/2 mouse with 3-button emulation (as it was in FC1); I've
also tried the Alps and Wheel Mouse configurations. This also occurs
whether or not gpm is running.
The mouse driver and other input drivers in XFree86 have not changed
between Fedora Core 1 and current. I suspect that any difference
in behaviour is caused by kernel changes from 2.4.x to 2.6.x, however
I do not have this hardware and can not test or try to reproduce
I'm carbon copying some kernel people who may be able to help
determine if this is a kernel problem or XFree86 problem.
I have FC1 with both kernel-2.4.22-1.2149.nptl and kernel-2.6.1-1.65
on a Compaq Presario 2100 laptop. 2.4 kernel handles touchpad with
support for tap (acts as click) and scroll section on right side (acts
as scroll wheel). The 2.6 kernel handles touchpad for mouse movement,
but no response to tap, and scroll area causes mouse vertical movement
instead of scrolling. This is definitely a kernel problem.
Synaptics Touchpad, model: 1
new absolute packet format
Touchpad has extended capability bits
-> multifinger detection
-> palm detection
input: SynPS/2 Synaptics TouchPad on isa0060/serio1
Disabling synaptics support fixed this for me.
Ok, this issue does seem to be a duplicate of bug #112473. Closing
*** This bug has been marked as a duplicate of 112473 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.