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 631989 - keyboard: handle per-hostname num-lock state saving
keyboard: handle per-hostname num-lock state saving
Product: gnome-settings-daemon
Classification: Core
Component: keyboard
Other Linux
: Normal normal
: ---
Assigned To: gnome-settings-daemon-maint
: 646738 648190 651593 660228 (view as bug list)
Depends on:
Reported: 2010-10-12 16:42 UTC by Bastien Nocera
Modified: 2012-10-29 08:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Bastien Nocera 2010-10-12 16:42:46 UTC
Currently disabled waiting on GSettingsList.

See code in plugins/keyboard/gsd-keyboard-manager.c
Comment 1 William Jon McCann 2010-10-12 18:30:44 UTC
May want to consider that it currently is sorta broken when you have multiple keyboards...  the setting isn't really per hostname but per device I guess.
Comment 2 Bastien Nocera 2010-10-12 18:52:57 UTC
Well, it should be per-device, though it obviously works per hostname, and applies the same setting to all the keyboards attached to a display server. Which is pretty broken...

Is it worth even trying?
Comment 3 André Klapper 2011-03-03 20:52:08 UTC
[Removing GNOME3.0 target as decided in release-team meeting on March 03, 2011. "nice-to-have" categorisation for GNOME3.0]
Comment 4 Bastien Nocera 2011-04-04 19:01:18 UTC
*** Bug 646738 has been marked as a duplicate of this bug. ***
Comment 5 Bastien Nocera 2011-04-25 14:54:56 UTC
*** Bug 648190 has been marked as a duplicate of this bug. ***
Comment 6 Bastien Nocera 2011-05-31 23:08:56 UTC
*** Bug 651593 has been marked as a duplicate of this bug. ***
Comment 7 Bastien Nocera 2011-07-01 16:22:06 UTC
Peter, do we have per-device Num-Lock, or is that per display?

If it's per-display, I'll just turn that into a boolean and be done with it.
Comment 8 Peter Hutterer 2011-07-04 00:03:47 UTC
Strictly speaking per device, though it takes some effort to get it to work per-device (i.e. XI2 support). By default, hitting numlock on one keyboard will traverse through all devices and toggle it for all.
Comment 9 Bastien Nocera 2011-09-09 00:01:34 UTC
commit 808640667656668693cedd685f6a830bddc0117d
Author: Bastien Nocera <>
Date:   Fri Sep 9 00:59:01 2011 +0100

    keyboard: Remember and apply NumLock status
    By default, without a care in the world for hostnames.
Comment 10 Bastien Nocera 2012-10-29 08:47:33 UTC
*** Bug 660228 has been marked as a duplicate of this bug. ***