Bug 446680 - Keyboard repeat rate not set
Summary: Keyboard repeat rate not set
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-settings-daemon
Version: 9
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 446545 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-05-15 16:48 UTC by Richard Körber
Modified: 2018-04-11 16:19 UTC (History)
5 users (show)

Fixed In Version: 2008-06-10
Clone Of:
Environment:
Last Closed: 2008-06-11 21:41:56 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Richard Körber 2008-05-15 16:48:23 UTC 
Description of problem:
When booting Fedora 9 and starting Gnome, the configured keyboard repeat delay
and repeat rate is not actually applied to the keyboard. I have to start
gnome-keyboard-properties and do some fake changes in order to get the settings
I want.

Version-Release number of selected component (if applicable):
xorg-x11-drv-keyboard-1.3.0-3.fc9.i386

How reproducible:
Always

Steps to Reproduce:
1. Change the keyboard repeat delay and rate to something you'd notice.
2. Reboot the system, log in to Gnome.
3. Try the keyboard.
  
Actual results:
The repeat rate and delay is set to some default values. (Which is annoyingly
slow for my taste... ;)

Expected results:
The repeat rate and delay is set as configured in the Gnome settings.
Comment 1 Rui Matos 2008-05-15 21:56:49 UTC 
I believe this bug should be assigned to gnome-settings daemon. I confirm that
it exists.
Comment 2 Matěj Cepl 2008-05-16 21:19:33 UTC 
Your wish is my order! (and moreover I think you are right)
Comment 3 Matthias Clasen 2008-05-23 03:51:31 UTC 
*** Bug 446545 has been marked as a duplicate of this bug. ***
Comment 4 Richard Körber 2008-05-27 20:09:25 UTC 
I also noticed that the Num Lock status is not restored until I start
gnome-keyboard-properties and change a parameter.

This bug is quite annoying. How can I help to resolve it quickly?
Comment 5 Richard Körber 2008-06-10 21:37:56 UTC 
The bug has been fixed with today's yum update. Thanks!
Comment 6 Matěj Cepl 2008-06-11 21:41:56 UTC 
Thanks for letting us know.
Note You need to log in before you can comment on or make changes to this bug.