lightdm does not keep numlock status on boot

Bug #835532 reported by Nathanel Titane
208
This bug affects 46 people
Affects Status Importance Assigned to Milestone
LightDM GTK Greeter
Expired
Low
Unassigned
unity-greeter (Ubuntu)
Expired
Low
Unassigned

Bug Description

when booting or logging out, the numlock status 'on' is not kept for password or pin input via numpad.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: lightdm 0.9.3-0ubuntu8
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
Architecture: amd64
Date: Sat Aug 27 12:22:27 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
SourcePackage: lightdm
UpgradeStatus: Upgraded to oneiric on 2011-08-27 (0 days ago)

Revision history for this message
Nathanel Titane (nathanel.titane) wrote :
Changed in lightdm (Ubuntu):
importance: Undecided → Low
status: New → Triaged
Revision history for this message
jerrylamos (jerrylamos) wrote :

Last couple new pc's I bought have no indicator for Num Lock and the num pad page up-page down are easier to reach than the PgUp & PgDn (yeah, overkill, tower, notebook, netbook, Android tablet).

With no indicator no problem on Narwhal, stays where it was. Oneiric keeps fiddling around with Num Lock state. Don't do that.

Oneiric should put Num Lock management back where Narwhal had it. If it's not broke, DON'T FIX IT.

Thanks for your attention,

Jerry

Revision history for this message
Sebastien Bacher (seb128) wrote :

Robert, is that something that would be easy to do for Oneiric? It's a detail but an annoying one ;-)

Changed in lightdm:
status: New → Confirmed
Revision history for this message
Robert Ancell (robert-ancell) wrote :

Not sure where the responsibility for this lies. Can anyone confirm which greeter(s) this happens on? I'm wondering if GNOME settings daemon handles this in unity-greeter, and we need something into the GTK greeter to handle this.

Changed in lightdm:
status: Confirmed → Triaged
importance: Undecided → Low
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Yes, this is something which gnome-settings-daemon takes care of, but it's disabled in the current version in oneiric (there's a big block of code in gsd-keyboard-manager.c commented out). This recent commit will fix it though:

http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=808640667656668693cedd685f6a830bddc0117d

affects: lightdm (Ubuntu Oneiric) → gnome-settings-daemon (Ubuntu Oneiric)
Revision history for this message
Sebastien Bacher (seb128) wrote :

bug #841748 is the g-s-d issue, but as Robert pointed only the unity greeter uses g-s-d so reassigning that bug to lightdm because the gtk greeter will need to do that in some manual way

affects: gnome-settings-daemon (Ubuntu Oneiric) → lightdm (Ubuntu Oneiric)
Revision history for this message
studentz (studenz) wrote :

Hi there

This works for me

sudo gedit /etc/lightdm/lightdm.conf

add the next line at the end

greeter-setup-script=/usr/bin/numlockx on

I review my xorg.log and I did not found any errors.

Revision history for this message
alexduf (dufournetalexandre) wrote :

I would add that LightDm resets the numlock status when choosing your Window Manager.

1-activate numlock
2-choose another WM
3-numlock is now off

Even if activating numlock by default is not possible because of Netbooks, it would be great to have a way to easily choose if numlock is on or off on startup.
I mean, an easier way than installing numlockx and editing a config file as root.

Revision history for this message
Sebastien Bacher (seb128) wrote :

What greeter do you use? The unity greeter runs gnome-settings-daemon which should store and restore the previous session status for numlock

Changed in lightdm (Ubuntu Oneiric):
status: Triaged → In Progress
status: In Progress → Fix Committed
status: Fix Committed → Won't Fix
Revision history for this message
anthropornis (anthropornis) wrote :

I am not sure if this is related (or if the affected package is even LightDM), but on my laptop running 11.10 32 bit (clean install, no upgrade), every time I lock the screen and then come back to my laptop the dialog box warns me that the numlock key is on even though it isn't.

My laptop doesn't have a numeric keypad per se, and I really have to go out of my way to engage the numlock (using the Fn key), so I don't use it.

The first time this happened I tried doing the above -- ostensibly to disengage my numlock -- but of course then my password was rejected, because the numlock was never engaged to begin with.

As best I can tell I don't have any screensaver any more, so I don't know if the affected package would be a gnome-screensaver type thing, LightDM, or something else, but I'd be glad to post this where ever it needs to go.

Revision history for this message
Mark Alan (malan) wrote :

Same problem here while using Xubuntu 11.10.

The usual tweaks do (briefly) light the numlock led upon login, but then the led goes off and numlock stays off.

By 'usual tweaks' I mean:
1. sudo apt-get install numlockx
2. followed by:

either:
  (cd ~/.config/autostart;ln -s $(which numlockx))

or:
  printf "[Desktop Entry]\nVersion=1.0\nType=Application\nName=numlockx\nExec=/usr/bin/numlockx\nStartupNotify=false\nTerminal=false\nHidden=false\n" > "$HOME/.config/autostart/numlockx.desktop"

affects: lightdm → lightdm-gtk-greeter
Revision history for this message
Nicolas Delvaux (malizor) wrote :

Still the same problem on Precise.

papukaija (papukaija)
tags: added: i386 pecise
Phill (phill.l)
tags: added: trusty
Revision history for this message
Kev Bowring (flocculant) wrote :

following todays lightdm update - the workround to get numlock at login screen fails

tags: added: wily xubuntu
Revision history for this message
Gunnar Hjalmarsson (gunnarhj) wrote :

On 2015-06-17 18:53, flocculant wrote:
> following todays lightdm update - the workround to get numlock at
> login screen fails

Please see this Ubuntu documentation page:

https://help.ubuntu.com/stable/ubuntu-help/numeric-keypad.html

The method suggested there works fine for me both on an updated vivid (with latest lightdm) and an updated wily.

Revision history for this message
Kev Bowring (flocculant) wrote :

that workround appears to be working here

no longer affects: lightdm (Ubuntu Oneiric)
affects: lightdm (Ubuntu) → unity-greeter (Ubuntu)
dino99 (9d9)
tags: added: xenial
removed: oneiric
tags: added: precise
removed: pecise
Revision history for this message
Chris Rainey (ckrzen) wrote :

Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.

Changed in lightdm-gtk-greeter:
status: Triaged → Incomplete
Changed in unity-greeter (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for unity-greeter (Ubuntu) because there has been no activity for 60 days.]

Changed in unity-greeter (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for LightDM GTK+ Greeter because there has been no activity for 60 days.]

Changed in lightdm-gtk-greeter:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.