When you have to unlock an encrypted volume during bootup, it's generally, and arguably, more convenient to have Num Lock on by default to type your password. This is even more convenient when using hardware tokens, being smart cards or usb keys, as they generally use numeric PINs to unlock the slot holding the key.
This module adds setleds and a shell script to turn Num Lock on.
The module priority (90), the hook (initqueue/settled), and its priority (90) are purely my attempt at putting it where I think it can go. I chose the later hook in time for the unlocking of the encrypted volume, based on trial and error testing. I reckon the devs here can recommend changes in this regard.
Checklist
[x] I have tested it locally
[ ] I have reviewed and updated any documentation if relevant
May I ask what are the next steps on a PR of this kind? Is it going to be merged on a future release? Is there anything I can do to help the process? I'd love to see it on the next version of Fedora.
When you have to unlock an encrypted volume during bootup, it's generally, and arguably, more convenient to have Num Lock on by default to type your password. This is even more convenient when using hardware tokens, being smart cards or usb keys, as they generally use numeric PINs to unlock the slot holding the key.
The idea of how to do it comes from here: https://wiki.archlinux.org/title/Activating_numlock_on_bootup
Changes
This module adds setleds and a shell script to turn Num Lock on.
The module priority (90), the hook (initqueue/settled), and its priority (90) are purely my attempt at putting it where I think it can go. I chose the later hook in time for the unlocking of the encrypted volume, based on trial and error testing. I reckon the devs here can recommend changes in this regard.
Checklist