Comment # 9 on bug 1017294 from Stanislav Brabec

This is a different issue than bug 1010880.

I have experienced this problem as well.

In normal situation, kbd always sets LED together with NumLock status change.

I am not sure what is the source of the problem. It could be kernel, kbd, X or
even systemd or boot process or splash screen implementation. It could be bad
setting of LEDs mask.

To debug the problem in the lowese level, you should check /sys/class/leds in
the inconsistent state. Is trigger properly set to kbd-numlock? Does brightness
correspond with the current LED state?