Bug 376001

Summary:	Fedora 8 on IBM T42: synaptics driver not functioning correctly
Product:	[Fedora] Fedora	Reporter:	Will Newton <will.newton>
Component:	synaptics	Assignee:	Peter Hutterer <peter.hutterer>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	8	CC:	david, xgl-maint
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-08-24 03:33:30 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Will Newton 2007-11-11 14:31:04 UTC

Description of problem:

My problem sounds a little like 233717. On a clean F8 install my touchpad seemed
to be functioning incorrectly e.g. button getting stuck down for short periods,
scroll wheel events happening at unintended times.

To fix the problem I had to install the gsynaptics application and turn off
scrolling and tapping events to restore my basic touchpad functionality. Maybe
as a default these events should be turned off?

The clean installed version of Xorg also defaults to Emulate3Buttons mode which
disables my 3rd button.

In all it takes quite a bit of work to get my laptop into a usable state.

Comment 1 Peter Hutterer 2008-07-21 06:51:36 UTC

Can you give me an update on this? How is the status with F9?

Comment 2 David Nalley 2008-08-24 03:33:30 UTC

Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as INSUFFICIENT_DATA.