So, what’s the deal with NumLock? I have it tuned on in the BIOS and in KDE settings, yet every time I boot up my PC or open the terminal as super user, it is turned off. Any way to deal with this? That happened on Bazzite, Fedora and now Cachy. I have a 100% keyboard and I want to use all 100% of it.

  • Vorpal@programming.dev
    16·
    8 days ago

    I don’t know the answer (I don’t care about numlock myself), but the arch wiki has an article on this: https://wiki.archlinux.org/title/Activating_numlock_on_bootup

    Perhaps that will be useful to you. In general checking the arch wiki is a good idea for any Linux issues, even if you don’t run arch, many things still apply to other distros and the articles are of very high quality.

    In this case, “Early bootup (mkinitcpio)” would likely not apply to most other distros that aren’t based on Arch, but the rest looks to apply widly.

    It is worth noting that in the KDE section it mentions the need to apply two settings, perhaps that could be it?

  • xxce2AAb@feddit.dk
    15·
    8 days ago

    Go to System Settings > Input & Output > Keyboard, in the Hardware tab, in the NumLock on Plasma Startup section, choose the desired NumLock behavior.

    For this to work, make sure that System Settings > System > Session > Background Services > Keyboard Daemon is enabled.

    Source

  • Lumisal@lemmy.world
    4·
    7 days ago

    I’ve been wondering about this. I’ve only had this issue with Fedora based distros, but not Ubuntu or Debian based ones. It’s extremely annoying, and the system settings having it on and same with bios don’t do anything. Num Lock is on by default for Mint for example - same system. Even freaking windows.