Strange NUMLOCK behavior after migration to openSUSE Leap 16.0

English Install/Boot/Login
1

After migration to 16.0 from 15.6, I’m seeing strange behavior of numlock. After login, it’s shines as if it is on but it is not. After hitting numlock key, strangely LED continues to shining but numlock is activated.

I believe the pseudo-activation comes from /etc/sysconfig/keyboard. What am I supposed to change?

Screenshot_20251027_201741
Screenshot_20251027_201741484×112 13.5 KB

Operating System: openSUSE Leap 16.0
KDE Plasma Version: 6.4.2
KDE Frameworks Version: 6.16.0
Qt Version: 6.9.1
Kernel Version: 6.12.0-160000.5-default (64-bit)
Graphics Platform: Wayland

2

@GreenFoolSmokingHarmlessTobacco:

First, welcome to the openSUSE Forums.

At the Virtual Terminal level – before a Graphical User Interface is activated at boot time – the console configuration is here:

 > cat /etc/vconsole.conf 
# Written by systemd-localed(8) or systemd-firstboot(1), read by systemd-localed
# and systemd-vconsole-setup(8). Use localectl(1) to update this file.
KEYMAP=de-nodeadkeys
FONT=suse12x22.psfu
FONT_MAP=
FONT_UNIMAP=
XKBLAYOUT=de
XKBMODEL=cymotionlinux
XKBOPTIONS=terminate:ctrl_alt_bksp
XKBVARIANT=nodeadkeys
 >

As the file’s comments state, you use the CLI command “localectl” to change the entries in this file.

Catch-22 with Leap 16.0 and KDE Plasma 6 –

  • After the upgrade from Leap 15.6, you have to login to each and every KDE Plasma user and, with the KDE Plasma “System Settings”, in the Keyboard Settings, setup the “Numlock on startup” setting.
3

I was considering numlockx but wanted to know what’s going on first. Thank you. I used the KDE system settings.