Bug 127718

Summary: Synaptics touchpad (?) gggggggggggenerates repeat characters
Product: [Fedora] Fedora Reporter: Horst H. von Brand <vonbrand>
Component: kernelAssignee: Dave Jones <davej>
Status: CLOSED NEXTRELEASE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 2CC: barryn, dtor_core, pfrields, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-04-16 04:06:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Horst H. von Brand 2004-07-12 20:55:40 UTC
Description of problem:
Toshiba M-30 notebook. Just getting the hand near the touchpad seems
to have the effect ilustrated. Sometimes.

Version-Release number of selected component (if applicable):

How reproducible:
Around once for each typed line in xemacs, for instance

Steps to Reproduce:
1. Type something, get near touchpad
Actual results:
rrrrrepeateddddd charrrs

Expected results:
No repeats.

Additional info:

Comment 1 Barry K. Nathan 2004-07-14 05:27:49 UTC
Have you tested previous Fedora Core or Red Hat releases, or MS
Windows, to make sure the problem does not happen with any of those?
Hardware failure can cause this type of thing. (I'm not saying it
can't be software, just that it would be helpful to know whether or
not it happens with some other version of the Linux kernel or with
some other non-Linux operating systme.)

Comment 2 Dmitry Torokhov 2005-03-22 21:11:27 UTC
It looks like Satellite's KBCs can not handle data from Synaptics at full rate, 
setting rate to 40 resolves keyboard issues.

This patch should take care of setting lower rate automatically:


Comment 3 Dave Jones 2005-04-16 04:06:23 UTC
Fedora Core 2 has now reached end of life, and no further updates will be
provided by Red Hat.  The Fedora legacy project will be producing further kernel
updates for security problems only.

If this bug has not been fixed in the latest Fedora Core 2 update kernel, please
try to reproduce it under Fedora Core 3, and reopen if necessary, changing the
product version accordingly.

Thank you.