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 628954 - Remember Num Lock state at shutdown and restore it at boot
Remember Num Lock state at shutdown and restore it at boot
Status: RESOLVED OBSOLETE
Product: gdm
Classification: Core
Component: general
2.31.x
Other Linux
: Normal enhancement
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2010-09-07 12:44 UTC by Nick Stringer
Modified: 2018-05-24 10:27 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Nick Stringer 2010-09-07 12:44:35 UTC
***Forwarded bug from Ubuntu Launchpad***

This is a pretty trivial bug, but it may be a candidate for future a 100 papercuts cycle. I did try searching to see if it had been reported before, but couldn't find any - apologies if I've missed it!

At present, NumLock isn't enabled when you go to log in to Ubuntu, so you have to manually enable it before entering numerical passwords on the number pad. While this isn't a critical issue, it is one that I feel should be fixed. I don't know anyone who uses the number pad for its arrows, and other OSs do enable NumLock by default.

Additionally to achieve this behaviour at present requires installing the numlockx package, and manually editing /etc/gdm/Init/Default - which is clearly not appropriate for new users.
Comment 1 Josh Triplett 2012-03-29 21:32:14 UTC
Not exactly trivial: while enabling numlock is mostly harmless on a desktop keyboard, on a laptop it frequently makes the keyboard unusable, since the numlock overlays many of the standard keys.

Recent changes to the Linux kernel will partly address this problem, by ensuring that the kernel respects the desired numlock state set in the BIOS.  (This assumes your BIOS has such a setting.)

Ideally, I'd suggest that some system component should save the numlock state at shutdown and restore it on boot; that way, once you toggle it on once, that state will persist until you turn it back off, even if you reboot the system in the meantime.
Comment 2 Josh Triplett 2012-03-29 21:33:26 UTC
> Ideally, I'd suggest that some system component should save the numlock state
at shutdown and restore it on boot; that way, once you toggle it on once, that
state will persist until you turn it back off, even if you reboot the system in
the meantime.

To clarify, I don't think GDM should do that; I think it makes more sense for some lower-level system component to do that.  Perhaps the same bits that handle keymaps for the console.
Comment 3 Strangiato 2017-04-06 17:45:47 UTC
Why is this not fixed more than 5 years later?
I cant enable numlock on boot on my Arch and this workaround is not working anymore.
https://wiki.archlinux.org/index.php/Activating_Numlock_on_Bootup#GDM
Comment 4 GNOME Infrastructure Team 2018-05-24 10:27:37 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gdm/issues/33.