Description of problem:
For some Toshiba laptop moduls, e.g. Satellige Pro 6000 and 6100, the keyboard
input routines often returns the character twice when a key was pressed only once.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Log in.
2. Type "This is a test of the keyboard" in shell or editor
Thiss is a ttest of thhe keybboarrd
Or something of that nature ;-/
This is a test of the keyboard
Will not happen in text console, or when Xkb extension is disabled. XkbDisable
is a nearly acceptable workaround, but:
1. Additional hacks are necessary to set up the keyboard map properly.
2. Change is lost if Xconfigurator is rerun.
also happens with RedHat 8.0 on Satellite pro 2400
This is not an XFree86 bug if I recall correctly, but some hardware
weirdness. You are best off searching google or asking for help on XFree86
mailing lists, to try and narrow the problem down. If you can obtain more
information on the problem, and could report back here with it, it'd be much
appreciated. That way, if my assumption of hardware problem is incorrect,
we'll have more to go on also.
There are lots of web sites that point out the problem, but information about
what is causing it is harder to find. The following may be helpful, though:
The refrences to "bounce" settings also make me wonder if I might adjust these
via "XkbOption" in XF86Config, but I can't find any documentation on that parameter.
I'm also going to post a request for more details on the Toshiba Linux forum.
"Peter T. Breuer" <firstname.lastname@example.org> says
The keyboard really does generate spurious key release events. I've
also been told that keydown can be generated as well, but have never
Apparently the way at least one layer of the X driver works, release
events are interpreted as keystrokes. One either
a) turns off that layer (the XKbDisable thing)
b) eliminates the spurious release events when they hit the raw
keyboard mode driver in the kernel (kernel patch)
c) applies a further filter of some kind to the X keyboard
driver, using setbounce and.or other utilities.
Toralf, Geoff: Does this problem occur on any newer Red Hat OS
releases also? If so, can you test it with Fedora Core 2 perhaps
and provide feedback? If it's still a problem, hopefully we
can find a solution that doesn't require adding hacks to the
Setting bug to "NEEDINFO" state.
Since this bugzilla report was filed, there have been several major
updates to the X Window System, which may resolve this issue. Users
who have experienced this problem are encouraged to upgrade to the
latest version of Fedora Core, which can be obtained from:
If this issue turns out to still be reproduceable in the latest
version of Fedora Core, please file a bug report in the X.Org
bugzilla located at http://bugs.freedesktop.org in the "xorg"
Once you've filed your bug report to X.Org, if you paste the new
bug URL here, Red Hat will continue to track the issue in the
centralized X.Org bug tracker, and will review any bug fixes that
become available for consideration in future updates.
Setting status to "CURRENTRELEASE" (Fedora Core 3 currently)