Bug 373646

Summary:	NUMLOCK configuration not taken into account
Product:	[Applications] systemsettings	Reporter:	jcdole <jcdole>
Component:	kcm_keyboard	Assignee:	Andriy Rysin <arysin>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	bshah, nate, plasma-bugs-null
Priority:	NOR
Version First Reported In:	5.8.3
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description jcdole 2016-12-14 15:39:46 UTC

After having configured the keyboard numlock behavior using yast in "sysconfig/keyboard/kbd_numlock = yes" and also configured in KDE using systemsettings5 in "System settings/Hardware/Input Devices/Keyboard/Hardware/Numlock on Plasma startup = Turn On" , The Numlock is always off at boot time or when changing user.
Displaymanager is ssdm

Comment 1 jcdole 2016-12-16 18:17:08 UTC

Please read for a workaround

http://forums.opensuse.org/showthread.php/521645-NUMLOCK-configuration-not-taken-into-account?p=2804132#post2804132

and

http://forums.opensuse.org/showthread.php/521127-SDDM-and-Num-Lock?p=2803512#post2803512

Comment 2 jcdole 2017-01-28 18:02:36 UTC

Nobody here ?

Comment 3 Alberto Salvia Novella 2017-08-24 16:42:17 UTC

Related bug: The Num Block key status isn't remembered between sessions:
(https://bugs.kde.org/show_bug.cgi?id=383962)

Comment 4 Nate Graham 2017-11-29 03:29:33 UTC


*** This bug has been marked as a duplicate of bug 368063 ***