SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have set in settings for my Logitech 104 key Value keyboard, to set the keyboard to num-lock when KDE5 starts. It simply, and definitely, remains off. I can press the key after KDE starts, and the light comes on and stay on for the number pad as expected.
This function works as expected in XFCE4.
I have tried different keyboard types from the drop down, but nothing works with KDE 5. All other keys work normally.
Does any one else see this behavior?
I search the forum and did not find anything that helped.
I don't have a Logitech keyboard. I wonder if System Settings->Startup and Shutdown->Autostart and run a script would work. It seems like a long term issue: https://bbs.archlinux.org/viewtopic.php?id=201686
I thought of one thing I modified, it may or may not have had an effect. When I first went to current, on this system, several months ago, I switched the login manager to slim. It is on SBo. I will investigate and see if that has anything to do with this problem. I will report back.
I read through the link RadicalDreamer posted. I edited /etc/slim.conf and removed the # sign in front of numlock on, and Num Lock is on in KDE 5 on a cold boot. So, this is solved.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.