I have enabled Restore num lock state on startup but it’s always disabled
I can’t figure out why it happens . Hope someone can answer
I have enabled Restore num lock state on startup but it’s always disabled
I can’t figure out why it happens . Hope someone can answer
First place I would look is in you BIOS - you might just be toggling it the wrong way! I still don’t really understand why it is still a ‘thing’. We’ve had dedicated cursor keys for MANY years now… (yeah, laptops, I know - and maybe 10-keyless gamers too)
Usually the DE has a way to permanently change numlock.
And there’s a small utility package numlockx that might help too.
I used the way DE has and it did nothing . The utility works partially I’d say . Because I cannot type any numbers with numlock off but can change workspace
Does this have anything to do with it , also is there any command line way to fix this (i.e. how to edit Xfconf ) cause I don’t think GUI can help
Anyway I am keeping the utility , thanks @manuel
xfconf-query is a CLI tool for Xfce settings. Try xfconf-query --help
for more info.
Got this far , now what ?
This is a boolean number , what value should I set and how to do that via command line .
You’re missing one more entry in your settings:
…and I found this in the XFCE4-Forum:
You have to replace VALUE with “true”
…and “leer” is German for “empty”
OK Fixed it
I reset everything in Xfconf editor in keyboards section and set numlock on with the command
xfconf-query -c keyboards -p /Default/Numlock -t bool -s true --create
and this entry appeared
Then selected restore numlock on startup in keyboard settings and the second entry appeared
So if you have any problem with Xfconf resetting all options is a good idea !
Thankyou @Tinymeat
I found this in the Arch-Wiki:
Install the numlockx package and then edit /etc/lightdm/lightdm.conf:
/etc/lightdm/lightdm.conf
[Seat:*]
greeter-setup-script=/usr/bin/numlockx on
But numlockx won’t help with typing numbers from numpad . I think the issue was with Xfconf so resetting it solved it .
I would’ve marked Tinymeat’s answer as solution but that could be achieved using the settings manager and the issue was something else .
Anyway thank you @freebird54 @manuel @Tinymeat and @Scruggs for helping