Red Hat Bugzilla – Bug 124207
cannot set keyboard repeat rate
Last modified: 2007-11-30 17:10:43 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510
Description of problem:
After I updated my libgnome, the keyboard doesn't autorepeat any
more. When I try to set keyboard autorepeat rates in Preferences ->
Keyboard, I got:
An error occurred while loading or saving configuration information
for gnome-settings-daemon. Some of your configuration settings may
not work properly.
When I clicked Details, I got:
Type mismatch: Expected `int' got `float' for key
Also, when I enabled Repeat Keys, every time I typed a character it is
I am also having problems with icons not showing up on Nautilus. I
don't know if this is related.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Just upgrade libgnome.
I am also getting similar symptoms -- I have no key repeat, but when I
enable it I get two keys per keystroke. I was getting the same error
message after I did an upgrade, but have not received that error since
I did a clean install. I'm using Fedora Core 2.
I don't recall seeing this problem when I first installed Core 2. I
did install some of the KDE libraries, and that's when I first saw the
issue (along with my background being messed up). I uninstalled those
KDE libraries, but all my problems still persist.
I have more problems: I cannot set the background, and when I tried
setting the theme in Preferences it tells me that it cannot find any
default themes. Downgrading back to libgnome-2.6.0-2 solves all the
Is anyone going to look at this? It's been open for a month and a half.
I have the same problem. Very annoying. I would be very happy to
give more details if needed for a fix.
Fedora Core 2
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.
This bug is being closed because it has been in the NEEDINFO state for a long
time now. Feel free to reopen the bug report if the problem still happens for
you and you can provide any information that was requested.