Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 154381 - Hardware autorepeat breaks autorepeat
Summary: Hardware autorepeat breaks autorepeat
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: xorg-x11
Version: 4.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: X/OpenGL Maintenance List
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2005-04-11 08:40 UTC by Petter Urkedal
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-04-11 10:41:01 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Petter Urkedal 2005-04-11 08:40:32 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.7.6) Gecko/20050322 Firefox/1.0.2 Red Hat/1.0.2-1.4.1

Description of problem:
The server shipped with RHEL-4 seems to contain an annoying bug

that breaks autorepeat.

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

How reproducible:

Steps to Reproduce:
1. Fire up the X server.
2. xset r rate 300 50
3. Hold down an autorepeating key

Actual Results:  Characters comes out fast, then slows down.

Expected Results:  Characters comes out fast, and continue so ad infinity.

Additional info:

Comment 1 Mike A. Harris 2005-04-11 10:41:01 UTC
The fix for this, which is attached to the bug report you've
provided a URL for above, is committed to the X.Org CVS stable
6.8.x branch, and is already integrated into the 6.8.2 release
which is in RHEL4 U1 update.

Once RHEL4 U1 is available, if after upgrading to the new release
you still encounter a problem, you may contact Red Hat Global Support
Services for the problem, and they will open an engineering ticket.

Setting status to "ERRATA".

Note You need to log in before you can comment on or make changes to this bug.