-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Numlock option? #16
Comments
Have you tried mapping a certain key sequence to numlock in your keyd config? |
Just tried it, and it does work, but NumLock state doesn't persist after a reboot since it's not actually saved in firmware, meaning it needs to be toggled every boot. I also tried the installing the latest keyd version from source which has some numlock-related fixes in the changelog, but KDE's "Turn Numlock off on boot" setting still doesn't work regardless. Some more digging reveals that a number of people are having trouble with the "Numlock=off" setting for KDE/SDDM though, so that might be a Wayland issue moreso than a Chromebook-specific problem. If that's the case it's probably better fixed at that level than here. |
There must be something with keyd and numlock. TBH the best option is probably to set numlock on every boot with the special mapping in keyd. If you have a suggestion for what I should set it to let me know. |
Hi WTT,
Not sure if this is something better handled outside of keyd so bear with me, but is it possible to add an option to remap the numpad keys to regular keys? I had to do this manually in keyd on my Chromebooks because (as far as I could find) there's no way to toggle NumLock in BIOS on these machines, toggling the setting in KDE doesn't do anything, and the keyd virtual device prevents the CLI numlock toggle commands I could find from working. This is the relevant part of my keyd config, all the other numpad keys work fine without remapping:
I know there aren't that many Chromebooks out there with a number pad, but it'd be a handy feature for the few that exist.
Thanks in advance!
The text was updated successfully, but these errors were encountered: