I can confirm this bug on Ubuntu (GDM/Gnome) Hardy (upgraded from Gutsy). I didn't have this problem on Gutsy, it has appeared probably after few upgrades on Hardy.
Rebuilding the numlockx package - as Martin-Éric recommends - fix this problem. See eg. this page for how to: http://www.cyberciti.biz/faq/rebuilding-ubuntu-debian-linux-binary-package/ However, you'll need to increase the version number (for example by adding new entry (1.1-8) into debian/changelog) or lock your custom build package, because the update-manager would like to use official version from repository.
Also there's probably no need to edit /etc/gdm/Init/Default since numlockx is launched from Xsession.d
I can confirm this bug on Ubuntu (GDM/Gnome) Hardy (upgraded from Gutsy). I didn't have this problem on Gutsy, it has appeared probably after few upgrades on Hardy. www.cyberciti. biz/faq/ rebuilding- ubuntu- debian- linux-binary- package/ However, you'll need to increase the version number (for example by adding new entry (1.1-8) into debian/changelog) or lock your custom build package, because the update-manager would like to use official version from repository. Init/Default since numlockx is launched from Xsession.d
Rebuilding the numlockx package - as Martin-Éric recommends - fix this problem. See eg. this page for how to: http://
Also there's probably no need to edit /etc/gdm/