Bug 1014629 – YaST2 /etc/sysconfig Editor: KBD_NUMLOCK expects the systemd module kbd.service

Bug 1014629 - YaST2 /etc/sysconfig Editor: KBD_NUMLOCK expects the systemd module kbd.service


Summary:	YaST2 /etc/sysconfig Editor: KBD_NUMLOCK expects the systemd module kbd.service

Status:	RESOLVED DUPLICATE of bug 1014991

Classification:	openSUSE
Product:	openSUSE Distribution
Classification:	openSUSE
Component:	YaST2
Version:	Leap 42.2
Hardware:	x86-64 openSUSE 42.2

Priority:	P5 - None Severity: Normal (vote)
Target Milestone:	---
Assigned To:	E-mail List
QA Contact:	Jiri Srain

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Create test case

Clone This Bug

Reported:	2016-12-08 16:14 UTC by Donald Curtis
Modified:	2016-12-15 14:13 UTC (History)
CC List:	3 users (show)

See Also:
Found By:	---
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Donald Curtis 2016-12-08 16:14:17 UTC

If the YaST2 /etc/sysconfig Editor is used to change the value of KBD_NUMLOCK, when the change is saved an error is raised because the systemd module "kbd.service" is expected but can not be found.

The file /etc/sysconfig/keyboard is however, correctly modified with the new value.

The systemd module "kbd.service" was present with 13.2 but. it seems to have been removed with Leap 42.2.

The Leap 42.1 status of this issue is not known.

Comment 1 Luca D'Amico 2016-12-08 19:45:44 UTC

I can confirm this issue. Forum thread: https://forums.opensuse.org/showthread.php/521540-Strange-problem-with-etc-sysconfig-editor-kdb?p=2803431

Comment 2 Imobach Gonzalez Sosa 2016-12-14 16:02:25 UTC

Yes, you're absolutely right: that service does not exist anymore and we'll need to fix that.

Stanislav: please, does exist any command to re-apply the settings from the sysconfig file? Thanks in advance!

Comment 3 Stanislav Brabec 2016-12-15 14:13:55 UTC

However you reported this issue two days earlier, I replayed to the later bug 1014991, which already contains detailed analysis.

Marking as duplicate of the bug 1014991. The answer is already there.

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