Solved Num Lock works in terminals but not in Plasma

[Cath O'Deray]

Num Lock (number lock key) no longer works in Plasma

Stopped working a few weeks or months ago. Began working again, for a short while, then again stopped working. The key does have the required effect in terminals ([vt(4)](https://man.freebsd.org/cgi/man.cgi?query=vt&sektion=4&manpath=freebsd-release), I guess).

codeberg.org

Any ideas?

 

[YYY__]

Do you use SDDM?

/usr/local/etc/sddm.conf

[General]
NumLock=on

sddm.conf()

Did you try it?

368063 – NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard

bugs.kde.org

Update:
Do you have the KDE service activated?

 

[Cath O'Deray]

Sorry, I should have been clearer. I don't want it on at start.

I want it to work after I switch it on (after the LED appears on the keyboard).

 

[Charlie_]

What about x11/numlockx?

Usage : numlockx [on|off]
on     - turns NumLock on in X ( default )
off    - turns NumLock off in X
toggle - toggles the NumLock on and off in X

 

[Cath O'Deray]

What about x11/numlockx?

From the description:

… allows you to start X with NumLock turned on …

That's not what I want, but thanks. Again for clarity:

• I don't want it on at start.

 

[Cath O'Deray]

Update:
Do you have the KDE service activated?

Which service, please?

 

[Charlie_]

numlockx off
How about this？
numlockx toggle&&numlockx toggle

 

[Deleted member 65485]

Those may help: xkbcomp(1) - xev(1) - xkbvleds(1) - xkbcli(1)

 

[Cath O'Deray]

Tail of output from xev:

KeyPress event, serial 37, synthetic NO, window 0x7800001,
    root 0x2f9, subw 0x0, time 18620734, (-529,160), root:(435,620),
    state 0x0, keycode 77 (keysym 0xff7f, Num_Lock), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 40, synthetic NO, window 0x7800001,
    root 0x2f9, subw 0x0, time 18620845, (-529,160), root:(435,620),
    state 0x10, keycode 77 (keysym 0xff7f, Num_Lock), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

FocusOut event, serial 40, synthetic NO, window 0x7800001,
    mode NotifyNormal, detail NotifyNonlinear

PropertyNotify event, serial 40, synthetic NO, window 0x7800001,
    atom 0x17f (_NET_WM_STATE), time 18624949, state PropertyNewValue
^C
%

I pressed the Num Lock key (to enable the feature, and the LED appears), then 5.

 

[cracauer@]

Peter H. at work. Diving into this is probably overwhelmingly complex, but you might want to mail him directly.

 

[YYY__]

Which service, please?

I'd swear there was one dedicated to Num-Lock. I can't check it now.

 

[Cath O'Deray]

Four background services not running, none is keyboard-related.

Nothing for Num-Lock.

Two running services match key:

• Input Actions
• Keyboard Dæmon

Accessibility, mouse navigation, I had enabled:

• Use number pad to move cursor

After reverting to its default, disabled, no improvement. I'll reboot to recheck.

Keyboard hardware: confuses me. It was probably set to Generic 105-key PC. I tried Generic 104-key PC and Generic 104-key PC with L-shaped Enter key, no improvement.

One keyboard layout: gb map, English (UK) layout.

 

[Cath O'Deray]

Use number pad to move cursor

That was the problem.

I'll mark this topic Solved, but the big picture is very weird:

Stopped working a few weeks or months ago. Began working again, for a short while, then again stopped working.

When Num Lock didn't work, it was a daily aggravation.

For the period when it did work: I can't imagine changing any number pad-related preference without also thinking of Num Lock (part of the pad) not working.

In other words: the previous period during which Num Lock worked is a mystery.