Bug 1031745 - SDDM turns on NUM LOCK
Summary: SDDM turns on NUM LOCK
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: sddm
Version: 20
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Martin Bříza
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1021052 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-18 16:42 UTC by Gerald Cox
Modified: 2014-10-07 09:28 UTC (History)
10 users (show)

Fixed In Version: sddm-0.2.0-0.31.20140627gitf49c2c79.fc20
Clone Of:
Environment:
Last Closed: 2014-06-30 10:30:35 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Gerald Cox 2013-11-18 16:42:38 UTC
Description of problem:

SDDM turns on NUM LOCK.  I discovered this when trying to enter my name when logging into my laptop and for an instant thought my keyboard was broken.  I then tried on my desktop and can see that the NUM LOCK is turned on when the SDDM login screen is displayed. 

Version-Release number of selected component (if applicable):
sddm-0.2.0-0.16.20130914git50ca5b20.fc19.x86_64

How reproducible:

At system login...

Steps to Reproduce:
1.  Logoff or restart system
2.  SDDM login screen is displayed
3.  NUM LOCK is turned on

Actual results:
NUM LOCK set

Expected results:
NUM LOCK off

Additional info:
While there is a quick fix for this (manually turning off NUM LOCK), NUM LOCK should not be arbitrarily turned on, especially when people are entering their userids and passwords.  It's just causes unnecessary confusion.

Comment 1 Scott Dowdle 2013-11-21 21:07:12 UTC
This is also present in Fedora 20... and has bitten myself as well as few others in #fedora-kde who couldn't login and though their keyboard was mapped incorrectly.

Comment 2 Fedora Update System 2013-11-25 17:40:10 UTC
sddm-0.2.0-0.21.20131125git7a008602.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/sddm-0.2.0-0.21.20131125git7a008602.fc20

Comment 3 Fedora Update System 2013-11-26 17:59:45 UTC
Package sddm-0.2.0-0.22.20131125git7a008602.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing sddm-0.2.0-0.22.20131125git7a008602.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-22158/sddm-0.2.0-0.22.20131125git7a008602.fc20
then log in and leave karma (feedback).

Comment 4 Kevin Kofler 2013-12-14 21:21:18 UTC
*** Bug 1021052 has been marked as a duplicate of this bug. ***

Comment 5 Andre Robatino 2013-12-16 12:31:06 UTC
Happens in F20 with sddm-0.2.0-0.16.20130914git50ca5b20.fc20. Have not tried the updates-testing version due to the reported problems with it. Does not happen with KDM. Changing Version to 20. (If this gets fixed in 20 and is still broken in 19, I'll reopen for 19.)

Comment 6 Gerald Cox 2014-01-01 00:53:24 UTC
NUM Lock issue still exists with sddm-0.2.0-0.16.20130914git50ca5b20.fc20

Comment 7 Joseph Pesco 2014-01-24 19:42:23 UTC
Hi, 

A very fast status report from yours truly. I've a hardware improvemnt: Asus, 1.9Ghz 14 inch display and VT-x that doesn't replace my Acer 725-0412 therefore this issue is still a conern.  

1. I downloaded the source, built it and got a breakpoint on main ().

2. I've noticed that if enter sddm on the command prompt the num lock is foobar once again.

Comment 8 Martin Bříza 2014-01-27 10:47:53 UTC
Hi,

this issue is completely addressable by your configuration - just set NumLock in /etc/sddm.conf to "None" and SDDM won't touch your settings.
The bug is all about default settings and the release containing configuration where it's set to None by default has not been pushed yet because there were other issues...
I'm still working on a new, complete release...

Comment 9 Joseph Pesco 2014-01-29 13:07:40 UTC
I tested the conf file entry set to none on my my Asus last night (Eastern Standard Time) and on my Acer earlier this morning.  This solves my problem, thank you!

Comment 10 Fedora Update System 2014-06-25 11:09:13 UTC
sddm-0.2.0-0.29.20140623gitdb1d7381.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/sddm-0.2.0-0.29.20140623gitdb1d7381.fc20

Comment 11 Fedora Update System 2014-06-25 11:13:22 UTC
sddm-0.2.0-0.29.20140623gitdb1d7381.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/sddm-0.2.0-0.29.20140623gitdb1d7381.fc19

Comment 12 Fedora Update System 2014-06-26 01:57:14 UTC
Package sddm-0.2.0-0.29.20140623gitdb1d7381.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing sddm-0.2.0-0.29.20140623gitdb1d7381.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-7749/sddm-0.2.0-0.29.20140623gitdb1d7381.fc19
then log in and leave karma (feedback).

Comment 13 Fedora Update System 2014-06-30 10:30:35 UTC
sddm-0.2.0-0.31.20140627gitf49c2c79.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 14 Fedora Update System 2014-10-07 09:28:58 UTC
sddm-0.9.0-1.20141007git6a28c29b.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/sddm-0.9.0-1.20141007git6a28c29b.fc19


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