Notes:
Num pad not working. It was working when I first ran Manjaro then several months in it all of a sudden stopped working. Not sure which updates or changes were made that may have caused this.
Num pad works fine in the login screen when typing in the password but then stops working once logged in.
Num pad works with other keyboards I’ve tested.
I know this topic has been covered here already however none of the fixes have worked for me. Please review the following attempted solutions that have not worked for me.
Reintalled numlockx via terminal : sudo pacman -S numlockx
Edited the lightdm.conf file :
sudo nano /etc/lightdm/lightdm.conf >
modified following line to look like this ==>
greeter-setup-script=/usr/bin/numlockx on
I then went to start menu > settings > keyboard >and checked the box "Restore num lock on startup.
Rebooted machine.
I also tried several different keyboard layouts such as all the Logitech and standard layouts.
I then reinstalled xorg-server and the xorg-server-common from the software center. (this may not have been related. Was sort of guessing at this point)
See how this goes:
Numlock xfce turn on at boot - Settings / Keyboard / Restore num lock
OR
In the file ~/.config/xfce4/xfconf/xfce-perchannel-xml/keyboards.xml
make sure the following values are set to true: <property name="Numlock" type="bool" value="true"/>
and <property name="RestoreNumlock" type="bool" value="true"/>
As per my post I already enabled the Restore num lock check box.
For the second recommendation when I tried opening that file it launched my web browser and displayed the following:
XML Parsing Error: XML declaration not well-formed
Location: file:///run/user/1000/doc/7DJsWMkqHyzqo5eQIOXJfw/keyboards.xml
Line Number 1, Column 16:
Sure, it might do that, as your browser opens .xml files and xml-based files such as .htm and .html.
The suggestion required you to open the file in a text editor such as nano (example only) where you could have made any edits suggested, or visually confirmed your configuration; example:
Well rub my belly, tickle my toes and call me Shlapfandoo.
I found an unlikely workaround.
I installed a Logitech device manager from the software center called Solaar. From there I went under the “Disable Keys” section and disabled the Num Lock feature. Ironically it managed to re-enable the num lock feature. The best part is that I can’t disable the num lock now which I find funny and useful. It also survived reboot. I’m giving myself a pat on the back and calling it a night.
Robocop out.
Mod edit:Consecutive posts merged again.
UPDATE:
I booted my pc this morning and to my surprise my num pad is no longer working again. I’m therefore looking for solutions again.
UPDATE:
I went out and purchased a new keyboard becuase this issue isn’t worth my time trying to resolve when I know it’s a specific issue with Logitech that may or may not be able to be fixed.
I purchased a NuPhy Node 1000 low profile keyboard. All of the num pad buttons work except for the 5 key for some reason.
I unplugged my Logitech MX Keys keyboard along with the receiver and plugged it back in then disabled num pad keys inside Solaar app and now the num pad is working on my Logitech keyboard again.
I really don’t know what’s going on but I’m going to condider this ticket resolved as a workaround. Thank you all for your time. I appreciate it.
I agree. Seems to be a firmware issue. Logitech natively is only compatible with Windows and Apple. I may need to just purchase a new keyboard. After all the num pad on my other keyboards work just fine.
I already set these values to True using the text editor. But thank you for letting my know the GUI method. I do prefer GUI. =)
Mod edit:Consecutive posts merged and @mentions added.
If there are no intervening replies, please edit your previous post instead to add further information. Cheers!
Manufacturer defined keys may be an issue, but standard keys like numlock should be fine. As the firmware seems to have an option to disable it then that could be the cause, but then it would have to be set to do so.
Have you tested using a live USB?
Have you tried using evtest (not installed by default) to check what’s being received?
This issue is definitely not resolved. My num pad isn’t working again. Even worse my num pad on my new NuPhy keyboard isn’t working now. This seems to be happeneing at random when no changes were made. Well… Except for some updates. That’s the only thing I did. Not sure why the num pad would stop working every time an update comes out though.
RECAP:
Installed Solaar Logitech device manager for Linux from the software center.
Under Disable Keys section : Disabled the num pad. This had the opposite affect and enabled the num pad which got it working again. It survived the first reboot but did not survive the second reboot.
I launched Solaar again and this time enabled the num pad in the settings. This enabled the num pad and has survived a couple days now and multiple reboots. So I consider this resolved for that reason.
I have not tested in a live USB environment. Now that I know that is an avenue for troubleshooting I may try that down the road. Which OS is a good environment to test in? I’d assume the same OS I’m having issues with?
I installed evtest from the software center (offical repo) doesn’t work whatsoever. I need to find an alt program that will help me get closer to finding the root cause of this num pad nonsense.
Just for the record, this is a forum, not a corporate bug-handling system. We don’t have any tickets here, with the exception of those of us who decided to park in the wrong place just when law enforcement was making its rounds.
Please don’t use acronyms. Only US Americans understand those — hint: I’m from one of those obscure patches of land positioned outside of the USA — and this here is an international community.
