You are not logged in.
Pages: 1
Once logged in, my numlock key is not enabled, but the LED for it is on. It has to be pressed twice to enable it.
I have tried the following solutions from the wiki:
-mkinitcpio hook
-systemd service
-startx
-Enable it in KDE settings
-Enable it in SDDM conf
Only enabling it in sddm.conf has worked, but even then numlock is only enabled during login. Once on the desktop, no numlock.
Enabling numlock in bios also had no effect.
Any other suggestions?
Last edited by aHumanPerson (2022-04-13 18:28:03)
Offline
I have tried the following solutions from the wiki:
Since most of them are mutually exclusive: what session do you actually start how? (Sounds like SDDM and KDE?)
In doubt install numlockx and run that as an autostart service.
Online
Yes, SDDM and KDE. I did set numlockx as an autostart service in KDE settings, but it doesn't seem to be working.
Offline
https://bbs.archlinux.org/viewtopic.php?id=57855
"How" did you set it up (exactly) and "how" is it seemingly not working.
Can you run "numlockx toggle"?
Online
I added it as an application in the KDE system setting autostart screen. The command it runs is just "numlockx on".
Running "numlockx toggle", "numlockx on", "numlockx off" all work fine when I run them in terminal
Offline
Either the command isn't run or KDE steamrolls over it and deactivates the numlock afterwards.
Wrap it in an executable script where you can eg.
#!/bin/sh
touch /tmp/numlock.dbg
sleep 5
numlockx onOnline
That seems to have fixed it. Thank you!
Offline
"worked around it" - seems there's something wrong w/ plasmas handling of this configuration? Or maybe you're starting yet another numlock toggling service?
=> bugs.kde.org
nb. that neither the touch (was just to ensure the script is executed) nor actually the script (you can /bin/bash -c "sleep 5; numlockx on") is strictly necessary even for the workaround.
Online
Pages: 1