After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 646738 - Numlock cannot be remembered as "activated" on start.
Numlock cannot be remembered as "activated" on start.
Status: RESOLVED DUPLICATE of bug 631989
Product: gnome-settings-daemon
Classification: Core
Component: keyboard
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2011-04-04 18:48 UTC by Frederic Bezies
Modified: 2011-04-04 19:01 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Frederic Bezies 2011-04-04 18:48:16 UTC 
I'm using a french keyboard which needs numlock activated to use numeric pad.

I set in control center (or I think so, gnome-control-center is crashing when clicking on keyboard) numlock to be activated by default.

Here is the crash of gnome-control-center :

GLib-GIO-ERROR **: Settings schema 'org.gnome.settings-daemon.peripherals.keyboard' does not contain a key named 'rate'
aborting...

And gnome-control-center version : 2.91.93.
Comment 1 Bastien Nocera 2011-04-04 19:01:18 UTC 
(In reply to comment #0)
> I'm using a french keyboard which needs numlock activated to use numeric pad.
> 
> I set in control center (or I think so, gnome-control-center is crashing when
> clicking on keyboard) numlock to be activated by default.
> 
> Here is the crash of gnome-control-center :
> 
> GLib-GIO-ERROR **: Settings schema
> 'org.gnome.settings-daemon.peripherals.keyboard' does not contain a key named
> 'rate'
> aborting...
> 
> And gnome-control-center version : 2.91.93.

You should 1) update your installation (2.91.93 is old, newer version won't crash, but it was a broken installation in the first place) 2) num-lock status isn't remembered by default in GNOME 3.0.

*** This bug has been marked as a duplicate of bug 631989 ***