Bug 21301 - NumLock LED indicator and NumLock functionality status are disparate
Summary: NumLock LED indicator and NumLock functionality status are disparate
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: All Linux
Priority: Normal minor
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-20 09:52 CEST by Mészáros Csaba
Modified: 2020-08-05 14:23 CEST (History)
3 users (show)

See Also:
Source RPM: sddm-0.14.0-13.mga6, sddm-kcm-5.8.7-1.mga6
CVE:
Status comment:


Attachments

Description Mészáros Csaba 2017-07-20 09:52:52 CEST
Description of problem:
In SDDM the state of NumLock key and its LED indicator are disparate.
The LED is on, but the NumLock key functionality is off.
You have to press the NumLock key once to be able to enter numbers using number block keys. After you press the NumLock key the NumLock LED remains on.

Version-Release number of selected component (if applicable):
sddm-0.14.0-13.mga6

How reproducible:
100%

Steps to Reproduce:
1. Turn on the computer
2. Wait until SDDM is loaded; lock at NumLock LED on keyboard, press number block keys to enter numbers

Actual results:
NumLock LED is on, but NumLock state is off. You cannot use the number block to enter numbers.

Expected results:
NumLock LED and NumLock state should be in sync. Either off or on.

Additional info:
When you log in to a session and log out the problem is present again.

Work around for SDDM:
in file '/etc/sddm.conf' in section '[General]' set either:
Numlock=on
OR
Numlock=off

reboot the computer.
Mészáros Csaba 2017-07-20 09:54:24 CEST

CC: (none) => pingvin

Comment 1 Marja Van Waes 2017-07-21 21:16:54 CEST
Assigning to the KDE maintainers.

@ KDE team:
Does numlock in SDDM _not_ need the numlock package? Then the bugs i'm adding to the "See also:" field, cannot have any influence on this bug, in that case please empty that field ;-)

Assignee: bugsquad => kde
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=18027, https://bugs.mageia.org/show_bug.cgi?id=19082
CC: (none) => marja11

Comment 2 Mészáros Csaba 2017-07-23 20:46:20 CEST
I removed the numlock package, but of course, as it was written. 
There is a problem with the removal.
But the "rpm -e --nodeps --noscripts numlock" command helped.
I restarted the computer. The numlock was powered on by BIOS. 
After the Grub2 it went off. 
When the X sddm came on, the numlock was also turned on.
Typing numbers into sddm was working fine.
Comment 3 Aurelien Oudelet 2020-08-05 14:23:34 CEST
This message is a reminder that Mageia 6 is end of life.

Mageia stopped maintaining and issuing updates for Mageia 6. At that time this bug will be closed as OLD (EOL).

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 6's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we cannot 
be able to fix it before Mageia 6 was end of life.
If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

Resolution: (none) => OLD
Status: NEW => RESOLVED
CC: (none) => ouaurelien


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