I can see the same bug on DELL E6500 laptop.
same dmesg.

kernel-2.6.31.5-127.fc12.x86_64
xorg-x11-server-Xorg-1.7.1-7.fc12.x86_64

/var/log/Xorg.0.log:
(II) config/hal: Adding input device AlpsPS/2 ALPS DualPoint TouchPad
(II) LoadModule: "synaptics"
(II) Loading /usr/lib64/xorg/modules/input/synaptics_drv.so
(II) Module synaptics: vendor="X.Org Foundation"
	compiled for 1.6.99.900, module version = 1.1.99
	Module class: X.Org XInput Driver
	ABI class: X.Org XInput driver, version 7.0
(II) Synaptics touchpad driver version 1.1.99.1
(**) Option "Device" "/dev/input/event6"
(II) AlpsPS/2 ALPS DualPoint TouchPad: x-axis range 0 - 1023
(II) AlpsPS/2 ALPS DualPoint TouchPad: y-axis range 0 - 767
(II) AlpsPS/2 ALPS DualPoint TouchPad: pressure range 0 - 127
(II) AlpsPS/2 ALPS DualPoint TouchPad: finger width range 0 - 0
(II) AlpsPS/2 ALPS DualPoint TouchPad: buttons: left right middle
(--) AlpsPS/2 ALPS DualPoint TouchPad: touchpad found
(**) AlpsPS/2 ALPS DualPoint TouchPad: always reports core events
(II) XINPUT: Adding extended input device "AlpsPS/2 ALPS DualPoint TouchPad" (type: TOUCHPAD)
(**) AlpsPS/2 ALPS DualPoint TouchPad: (accel) keeping acceleration scheme 1
(**) AlpsPS/2 ALPS DualPoint TouchPad: (accel) acceleration profile 0
(--) AlpsPS/2 ALPS DualPoint TouchPad: touchpad found
(II) config/hal: Adding input device DualPoint Stick
(**) DualPoint Stick: always reports core events
(**) DualPoint Stick: Device: "/dev/input/event5"
(II) DualPoint Stick: Found 3 mouse buttons
(II) DualPoint Stick: Found relative axes
(II) DualPoint Stick: Found x and y relative axes
(II) DualPoint Stick: Configuring as mouse
(**) DualPoint Stick: YAxisMapping: buttons 4 and 5
(**) DualPoint Stick: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "DualPoint Stick" (type: MOUSE)
(**) DualPoint Stick: (accel) keeping acceleration scheme 1
(**) DualPoint Stick: (accel) acceleration profile 0
(II) DualPoint Stick: initialized for relative axes.
(II) config/hal: Adding input device Macintosh mouse button emulation
(**) Macintosh mouse button emulation: always reports core events
(**) Macintosh mouse button emulation: Device: "/dev/input/event3"
(II) Macintosh mouse button emulation: Found 3 mouse buttons
(II) Macintosh mouse button emulation: Found relative axes
(II) Macintosh mouse button emulation: Found x and y relative axes
(II) Macintosh mouse button emulation: Configuring as mouse
(**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
(**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Macintosh mouse button emulation" (type: MOUSE)
(**) Macintosh mouse button emulation: (accel) keeping acceleration scheme 1
(**) Macintosh mouse button emulation: (accel) acceleration profile 0
(II) Macintosh mouse button emulation: initialized for relative axes.

forgot to add that a similar bug seems te be referenced here:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/296610

This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Hi,
It seems the Ubuntu guys made more progress on this bug.
and that a patch is included in the vanilla kernel 2.6.33-rc1.
(see. http://linux.derkeiler.com/Mailing-Lists/Kernel/2009-12/msg07439.html)

I got a bit lost tracking it, but I think this is the patch:
http://patchwork.kernel.org/patch/60124/

Could you backport it to the next fedora kernel ?
thanks.

PS:
I'm not sure but {{ bugzilla.link(492719) }} seems to be a duplicate...

*** Bug 492719 has been marked as a duplicate of this bug. ***

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

So, I tested again, as I have the computer concerned with this bug for a few days.
And it seems to me that this bug is solved on an updated Fedora 12.


Thanks.

I have A Dell Latitude D600, which has the AlpsPS/2 ALPS DualPoint TouchPad. I've run Fedora 12 and Fedora 13 Beta and have essentially the same experience as the original poster. So I do not think this bug is fixed.

My verbose description of the manifestation of the problem in two very annoying instances that are about 80% reproducible.

1. I use the touchpad to move the mouse arrow to a button or drop down menu. I then release my finger from the touchpad and click the left touchpad button (the one right below the touchpad). The UI does not indicate the button as been pushed, the drop down menu does not appear.

  a.) If I touch the touchpad even slightly to cause mouse arrow movement, now the previous click is registered and the UI responds 100% of the time as expected. Until I do this, the UI will wait indefinitely.

  b.) If I click again, the click is almost always registered, but not as reliably as touching the touchpad, or slightly moving my finger if it is already in contact with the touchpad.

2. I use the touchpad to position the mouse arrow above or below the scroll shuttle, and click one. The scroll shuttle will not move up or down by one page only. It will continue to scroll until the touchpad is touched.

Conclusion: I think the click is being interpreted as a click and hold in the vast majority of cases even though the button has been released. The button "release" comes when the button is pressed again, or more commonly in daily usage when the mouse arrow is moved using the touchpad (even grazing the touchpad will cause this.)

Created attachment 417933 [details]
CentOS DeviceManager screenshot 1

Created attachment 417934 [details]
CentOS DeviceManager screenshot 2

Created attachment 417935 [details]
Fedora 13 DeviceManager screenshot 1

Created attachment 417937 [details]
Fedora 13 DeviceManager screenshot 2

Ok so I cannot reproduce the problem at all on CentOS 5.5. The problem happens constantly on Fedora 13. This is on the same hardware (Dell Latitude D600) with default installations.


OK so four attachments: CentOS 5.5 vs Fedora 13 Device Manager.

C1= CentOS 5.5, clicked on "AlpsPS/2 ALPS DualPoint TouchPad" in the left hand navigation of the Device Manager.
C2= CentOS 5.5, clicked on the parent "Platform Device (i8042)" in the left hand navigation.

F1 and F2, same on Fedora 13 respectively.

As you can see there are discrepancies between the two:

Fedora 13:
info.capabilities  string[]   input, input.touchpad

CentOS 5.5:
info capabilities  strlist    [u'input', u'input.tablet', u'input.mouse']


Anyway I don't know if any of these differences explain why the button/trackpad are erratic on Fedora but not on CentOS.

This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.