by booting UBUNTU 9.04 numlockx don't work -or (if you like) works till after GDM login

[kapetr]

Binary package hint: numlockx

Hello and sorry please my English.

The numlockx package i properly installed and is automatic called by /etc/X11/Xsession.d/55numlockx
But the Numlock after boot (i.e. in GDM) is off.

To ensure me, that the xsession script is called, I did this modification:

# X session startup script: /etc/X11/Xsession.d/55numlockx

if [ -x /usr/bin/numlockx ]; then /usr/bin/numlockx on || /bin/true; fi

date >> /home/hugo/numlockx.log

# EOF

After boot is /home/hugo/numlockx.log filled with "date" data - also /etc/X11/Xsession.d/55numlockx is called properly.
But without effect.

But when I run /etc/X11/Xsession.d/55numlockx manually (as root or as hugo), the numlock goes ON ?

Any Idea, where is the problem ?

Thanks

[kapetr (kapetr)]

Hello

I HACKED this:

I had add to the end of /etc/gdm/Init/Default :

if [ -x /usr/bin/numlockx ]; then
/usr/bin/numlockx on
fi

It works.

P.S.: As I have find out, the /etc/X11/Xsession.d/55numlockx is working, but unfortunately too late - after GDM login. Also - by typing my password, I had to press NumLock key.
But with this my hack is it now not necessary.

[Rolf Leggewie (r0lf)]

making the numlock on the keyboard actually work and consistent with the LED has been a long-standing issue for me and should avery nice papercut for lucid.

[Vish (vish)]

Thank you for bringing this bug to our attention. However, a paper cut should be a small usability issue, in the default Ubuntu install, that affects many people and is quick and easy to fix. So this bug can't be addressed as part of this project.

- This is a bug , hardware-specific and not a papercut. [num lock does not work only for certain hardwares]
For further information about papercuts criteria, please read https://wiki.ubuntu.com/PaperCut.

Don't worry though, this bug has been marked as "Invalid" only in the papercuts project.

And , this is a dup. there is already another bug regarding this . [I'm just not sure of the bug#]

[Michal Čihař (nijel)]

Are you still able to reproduce this bug with current version of xserver and numlockx?

[kapetr (kapetr)]

I still have to use /etc/X11/Xsession.d/55numlockx hack in Ubuntu 10.10.

But now the numlock LED is not lighting during GDM, but numpad keys are working.
Numlock LED lights just after login.

I don't know, why this is not served by GDM by default !

Probably this is a GNOME strategy - all GNOME apps are with every new version less and less configurable, more and more "simple", ....

In GDM is now no commented config file, no documentation, no XDMCP, ...

:-((

[Rolf Leggewie (r0lf)]

Michal, in bug 218202 comment 41, I explicitly stated this bug and and bug 218202 are *NOT* dupes. Unduping.

[Michal Čihař (nijel)]

Rolf: Sorry, I somehow mixed this up with some different issue.

[Michal Čihař (nijel)]

Adding GDM into this bug as I currently do not see any way for numlocx to hook into gdm startup to be executed. Once such interface is available in gdm, numlockx can use it.

[kapetr (kapetr)]

Hello Michal,

I probably due my low English do not understand, what do you mean with your last replay.

I use my hack and it is still working in updated U10.10. The only problem is with LED, which is by login in GDM off, even if really is numlock active.

[Michal Čihař (nijel)]

Well if the only issue is LED, this is indeed duplicate of bug #218202.