Bug 15197 - Numlock is not on in kdm although the numlock rpm is installed and drakconf shows it running from startup.
Summary: Numlock is not on in kdm although the numlock rpm is installed and drakconf s...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Luc Menut
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2015-02-03 21:31 CET by Herman Viaene
Modified: 2015-06-01 14:05 CEST (History)
1 user (show)

See Also:
Source RPM: numlock
CVE:
Status comment:


Attachments

Description Herman Viaene 2015-02-03 21:31:05 CET
Description of problem:


Version-Release number of selected component (if applicable): 2.12-11.mga8


How reproducible:


Steps to Reproduce:
1.Fresh install of MGA5-Beta3 with KDE
2.Install numlock rpm, also put numlock on in systemsettings
3.Restart PC, numlock is not on


Reproducible: 

Steps to Reproduce:
Comment 1 Herman Viaene 2015-02-03 21:32:47 CET
2.12-11.mga5 of course, sorry.
I've seen the same thing happening in Beta2, but there it disappeard after a few startups.
Comment 2 Barry Jackson 2015-02-03 21:52:07 CET
Is numlock service in "Configure your Computer (MCC) -> System -> Services -> Numlock" checked to start on boot?

CC: (none) => zen25000

Comment 3 Barry Jackson 2015-02-03 22:07:29 CET
Sorry - misread above - you already said that it was running.
David Walser 2015-02-08 02:21:08 CET

Assignee: bugsquad => lmenut

Comment 4 Luc Menut 2015-02-23 21:48:51 CET
When numlock doesn't work in kdm,  could you please report the output of :
- systemctl status numlock  (as root)

- ls -l /var/lock/subsys/numlock
Comment 5 Samuel Verschelde 2015-06-01 00:16:47 CEST
Herman, could you provide the needed information?

Keywords: (none) => NEEDINFO

Comment 6 Herman Viaene 2015-06-01 13:36:40 CEST
The problem does not appear in MGA5-64 final round 4.
Comment 7 Samuel Verschelde 2015-06-01 14:05:42 CEST
fixed then

Resolution: (none) => FIXED
Status: NEW => RESOLVED


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