373646 – NUMLOCK configuration not taken into account

Bug 373646 - NUMLOCK configuration not taken into account

Summary: NUMLOCK configuration not taken into account

Status:	RESOLVED DUPLICATE of bug 368063

Alias:	None

Product:	systemsettings
Classification:	Applications
Component:	kcm_keyboard (show other bugs)
Version:	5.8.3
Platform:	openSUSE Linux

Importance:	NOR normal
Target Milestone:	---
Assignee:	Andriy Rysin

URL:
Keywords:

Depends on:
Blocks:

Reported:	2016-12-14 15:39 UTC by jcdole
Modified:	2020-08-11 16:59 UTC (History)
CC List:	3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.

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 ***