[jaunty] Numlock always on inside X, cannot be disabled, big issue for laptop users

[Matteo Settenvini]

Since a couple of days, in Jaunty, logging into Xorg always brings my numlock on.
Problem is, I've got a laptop, so the numeric pad is overimposed to some normal keys (u-i-o-p-j-k-l-m).
I cannot disable the numlock inside X for some strange reason; hitting SHIFT+ScrollLock (equivalent to my numlock key on this ThinkPad G40) simply doesn't make anything happen.

I've got to CTRL+ALT+F1 to a console, and there I can disable it, then switch back to Xorg.

If someone made the numlock being on by default, please don't! This breaks things to most laptop users. Moreover, since disabling it inside Xorg is impossible at least for me, having to switch to a console and then back in is quite painful.

As a workaround, is there something I can put in xorg.conf to force the numlock to be disabled by default?

[Matteo Settenvini (tchernobog)]

Hello, I noticed that maybe this isn't due to xserver-xorg-input-keyboard, since during GDM login screen the numlock is off.

It becomes on during GNOME loading; could it be gnome-session or gnome-preferences-daemon?

[Matteo Settenvini (tchernobog)]

Seems to have been fixed with the GNOME 2.25.91 round of releases.

[NoOp (glgxg)]

Same issue here on A21m Thinkpad. Started today w/Jaunty 2.6.28-12-generic. 3 reboots and status stays the same. Have to use Ctrl-Alt-F1 to change & then back to Ctrl-Alt-F7.

Please let me know which logs you'd like to see.

$ apt-cache policy xserver-xorg-input-kbd
xserver-xorg-input-kbd:
  Installed: 1:1.3.1-2ubuntu1
  Candidate: 1:1.3.1-2ubuntu1
  Version table:
 *** 1:1.3.1-2ubuntu1 0
        500 http://archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

[NoOp (glgxg)]

Sorry for the noise. Looks like this might be the NX server issue that I'd reported in this bug:

https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/92482
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/92482/comments/40

I had upgraded all of my NX software yesterday & tested by logging into the A21m - so I think it's the NX causing the problem.

[NoOp (glgxg)]

Please see:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/92482/comments/46
for the workaround.