Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 72826 - keyboard "rate" preferences have wrong label
keyboard "rate" preferences have wrong label
Status: CLOSED DUPLICATE of bug 75628
Product: Red Hat Linux
Classification: Retired
Component: control-center (Show other bugs)
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Jonathan Blandford
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2002-08-28 03:38 EDT by Jan Iven
Modified: 2013-04-02 00:17 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:49:30 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jan Iven 2002-08-28 03:38:36 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.0 (X11; Linux i686; U;) Gecko/20020509

Description of problem:
The GNOME keyboard rate setting tool (gnome-keyboard-porperties?) has the label
"faster" on slider "delay" at the wrong (right) end. Moving the slider in that
direction actually increases delay.

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

How reproducible:

Steps to Reproduce:
1.click "Red hat", "preferences"?, keyboard?
2.adjust slider towards right
3.note that keyboard delay increases

Additional info:

(filing this bug from memory, so actual labels could be slighty off)
Comment 1 Havoc Pennington 2002-09-25 14:53:11 EDT
Upstream as http://bugzilla.gnome.org/show_bug.cgi?id=94196
Comment 2 Jody Goldberg 2002-09-25 15:37:01 EDT
This was fixed in
Comment 3 Havoc Pennington 2002-12-19 18:12:39 EST

*** This bug has been marked as a duplicate of 75628 ***
Comment 4 Red Hat Bugzilla 2006-02-21 13:49:30 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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