Just a comment, because I forget that:

With F14 rawhide numlockx work fine two or three days ago, but there is a lot of updates , and after this updates numlockx don't work.
When I do in console:
numlockx on

There is no effect and no error message...

This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

I installed fedora-14-alpha-rc3, install package numlockx-1.0-16.fc12.x86_64 and the problem still persist.

numlockx on or numlockx off don't work.

Hi..
For test I rebuild the fc12 package to fc14, with this command:
rpmbuild -ba rpmbuild/SPECS/numlockx.spec

I have a numlockx-1.0-16.fc14.x86_64.rpm package, I install it, and numlockx on or off work, but the led of my keypad don't work.

And when I active my keypad by the numlock button, led work, but if I am in numlockx on option, keypad is not enable, and vice versa...

Really, numlockx on and numlockx off commands don't work in Laughlin.

(In reply to comment #5)
> Really, numlockx on and numlockx off commands don't work in Laughlin.

Why dev don't rebuild numlockx for F14 (see my comment 4)?

Because "but the led of my keypad don't work".

I built numlockx-1.2 from http://ktown.kde.org/~seli/numlockx/ and installed it to Fedora 14. Numlockx-1.2 work, but not change a LED status.

F14 is for the 02 November, and this bug is not closed...
Nobody know how solve this problem?

this turned out to be a quite huge problem and we don't know a good solution yet. there are several options on how to fix this but all cause regressions in other behaviours. I doubt this will be fixed before the F14 release, we don't have a solution for upstream yet.

numlockx-1.0-18.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/numlockx-1.0-18.fc14

Don't work numlockx-1.0-18.fc14. :(

No change LED status, and no change keypad status.

I install numlockx-1.0-18.fc14 and that don't work...
In console I do numlockx on or numlockx off, and my keypad is not enable or disable, without error message (like my comment 3)...

Tried numlockx-1.0-18.fc14 with both USB and PS2 keyboard and I get the same as #12 & 13

For test I re-build numlockx-1.0-18.fc14 to numlockx-1.0-18.fc13 and install.
That work for f13, but led is on when keypad is off and vice versa...

            unsigned int mask;
            XkbVirtualModsToReal( xkb, 1 << i, &mask );
            return mask;

Always return to mask == 0? (I used gdb.)

numlockx-1.0-18.fc14 has been pushed to the Fedora 14 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update numlockx'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/numlockx-1.0-18.fc14

Do you see this issue on normal keyboards or on a laptop?
on my T61, I can't switch the leds on for the laptop keyboard, but the external one works fine.

Checking the event flow, what the driver does is correct (i.e. set the led for all devices) but the one on the laptop doesn't light up. Likewise, hitting numlock on the laptop only sends an event when _setting_ numlock, not when unsetting it. This part seems to be handled in hardware.

I install numlockx-1.0-18.fc14 from updates-testing repo, and that don't work...
Same result as comment 12 and 13.

In reply comment 18, I have a laptop, Toshiba X200.

numlockx-1.0-18.fc14 from updates-testing repo doesn't work on my desktop pc either. (led off and no num lock when running "numlockx on").

(In reply to comment #20)
> numlockx-1.0-18.fc14 from updates-testing repo doesn't work on my desktop pc
> either. (led off and no num lock when running "numlockx on").

Same here, both USB and PS2 keyboards.

Same problem here with PS2 keyboard and numlockx-1.0-18.fc14.x86_64 from koji.

numlockx has no effect.

Same problem on F14 final x86_64.

numlockx-1.0-18.fc14.x86_64 has no effect here.

Paul

numlockx-1.0-18.fc14.x86_64 has no effect for me.  Could we be missing a pre-req?  The readme says it relies on XKB.

It looks like upstream is on version 1.2.  Maybe updating the code base will fix it?

http://ktown.kde.org/~seli/numlockx/

(In reply to comment #26)
> It looks like upstream is on version 1.2.  Maybe updating the code base will
> fix it?
> 
> http://ktown.kde.org/~seli/numlockx/

No. Please see comment #8.

I saw that numlockx 1.2 have a new option "toogle". Perhaps somedoby can try if this works.

toggle() {
  if (status() == "on") switch("off") else switch("on");
};

;)

Since I have enabled the auto-login (/etc/gdm/custom.conf), the numeric keypad is now enabled at starup (since it's set "on" in BIOS).

Is it possible, that the same problem is hitting F13 now too? As I seem to have problems with numlock also on F13..

I can confirm that the errant behavior presents in F14 Security Spin running numlockx 1-0-16.fc12 (i686), which is the version defined currently as most recent stable.

There are 2 keyboards attached to the machine which is an HP Mini 110 netbook. One is the embedded keyboard, another is attached via USB.

I haven't seen any movement on this issue since #17 (2010-10-28), which didn't fix the problem.  It really is annoying to manually push numlock every time I boot up my pc.  As an alternative to fixing numlockx, is there any setting I can change -- perhaps something in a configuration file -- that can turn numlock on automatically?

Also, Peter Hutterer in #10 (2010-10-21) said that there are a few ways to fix it, but those ways caused regression errors.  If someone were to describe those fixes and the regression errors they caused, perhaps it would help.

Lastly, this bug is marked with the keyword "Triaged" which policy says should only be applied if there is a roadmap to fix it.  I suspect that this is out-of-date (because the fix in #17 failed QA) and should be removed.  If it is still valid, could you please post the roadmap?

Thanks.

(In reply to comment #33)
> Also, Peter Hutterer in #10 (2010-10-21) said that there are a few ways to fix
> it, but those ways caused regression errors.  If someone were to describe those
> fixes and the regression errors they caused, perhaps it would help.

https://bugs.freedesktop.org//show_bug.cgi?id=16145#c22

(In reply to comment #18)
> Do you see this issue on normal keyboards or on a laptop?

I have a MSI K9A2 CF-F (BIOS: 7388v1D) http://eu.msi.com/index.php?func=prodmbspec&maincat_no=1&cat2_no=&cat3_no=&prod_no=1333 and Logitech PS2 keyboard. My Fedora 14 is up to date, and numlockx don't work. :(

rpm -q numlockx
numlockx-1.0-18.fc14.x86_64

I have tested numlockx-1.0-18.fc14 on a standard desktop (with external keyboard) and on a laptop with external keyboard attached.

It doesn't work on either.

As long as we don't have a working numlockx, are there other ways to enable the numlock key for gdm ?

It still does not work.

According to diff the only difference between the 1.0 and 1.2 version of numlockx is addition of the "toggle" feature.

The numlockx at first tries the xkb extension and in case of failure it falls back to the xtest extension.

But it seems that the xkb handling is broken by the 0001-XI2-support.patch (I will look deeper on it later). Rebuilding without it seems to solve the issue for me, scratch build for testing:
http://koji.fedoraproject.org/koji/taskinfo?taskID=2756682

However some notebooks seems to have hard-wired the numlock handling in firmware, thus it need not work in some specific cases.

(In reply to comment #37)

Thank you! It works, but does not alter the status LED.

(In reply to comment #38)
> Thank you! It works, but does not alter the status LED.

Is it laptop or external keyboard? Laptop's internal keyboards have issues and sometimes it is impossible to get it correctly working. Did it work before? Does it work through xtest? e.g.:

$ xte 'key Num_Lock'

I would like to propose a workaround.  When my computer boots up, the BIOS turns numlock on.  It's X that resets the keyboard and turns numlock off.  Could we just have X not reset the keyboard and leave numlock on if it's already on?

@Joseph D. Wagner
I don't think it's X which turn off the numlock. See my comment #30.

I want to confirm the comment #38. Tested on four hosts with external keyboards - numlock is on, but LED is off (which is worse than to set numlock manually).

xte 'key Num_Lock' does the same - turns numlock on and off, but with LED unaffected

xset led named 'Num Lock' do not work either, although xset led named 'Scroll Lock' works well

So rpm -e numlockx is the best what I can do for my IceWM desktops.

MSI K9A2 CF-F, external PS2 Logitech keyboard.
http://eu.msi.com/index.php?func=proddesc&maincat_no=1&prod_no=1333

xte 'key Num_Lock'

command work, but don't change LED status. Same, then numlockx.

(Sorry, my english is very bad. :( )

(In reply to comment #39)
> Is it laptop or external keyboard? Laptop's internal keyboards have issues and
> sometimes it is impossible to get it correctly working. Did it work before?
> Does it work through xtest? e.g.:
> 
> $ xte 'key Num_Lock'

(In reply to comment #8)
> I built numlockx-1.2 from http://ktown.kde.org/~seli/numlockx/ and installed it
> to Fedora 14. Numlockx-1.2 work, but not change a LED status.

To the maintainer of this bug: This reporter was NOT asking for a LED=off status. They were trying to let you know that the LED light was remaining off.

I found how you took it here: http://forums.fedoraforum.org/showpost.php?p=1410894&postcount=5 - that's not the way it was meant.

I am also struggling with this in every known version of numlockx that's been released. I'm on a 32-bit machine.

This problem is solved in Fedora 15, thanks! Numlock status and keyboard LED status is changed correctly.

rpm -qa libX11\* numlockx\* | sort
libX11-1.4.3-1.fc15.i686
libX11-1.4.3-1.fc15.x86_64
libX11-common-1.4.3-1.fc15.noarch
libX11-devel-1.4.3-1.fc15.x86_64
numlockx-1.2-1.fc15.x86_64

Yes I confirm, it works within F15.

(In reply to comment #47)
> Yes I confirm, it works within F15.

Reporter, do you agree with this assesment? Or do you still require fix in F14?

Thank you for your patience

I'm happy that bug is solved.
Now I use kde 4.6 (F14 and F15) and I don't kneed numlockx for enabling my keypad. It's a configuration option in KDE.

But I tested the last numlockx in F15 and I confirm that work.

I don't test for F14, but I think this bug can be closed.

Too be honest, I would not mind a fix in F14 as F14 will not be EOL for more than 6 month and it is an annoying bug.

Thanks

I second Pierre's words.

Thanks, Paul

Same here, several of my (and my customer's) machines are still on F14 and will be for a while. Are there technical obstacles that prevent this fix from being backported to F14 ?

It looks to me that after a fresh install of F14 on Acer Apire 5742, keypad worked fine with no numlockx. I installed also Keyboard Lock Keys to see the status of a NumLock key as this laptop has no LEDs. 
Tonight I noticed that numeric keypad does not work :(((
Pressing NumLock changes status of the applet, but keypad still does not work. What is weird in gdm login it works, in BIOS it works, in GRUB menu it works, in Windows 7 it works.
Is there any way to fix this??? It is a shame that in modern OS numeric keypad simply does not work :-O

Regards,
Ges

Grzegorz, on my f14 installation my keypad started working fine at some point with no numlockx installed. Then it stopped working but i found that unsetting system > keyboard > mouse keys > pointer can be controlled using the keypad, got it working again. maybe this will work for you?

Hi p.johns, 

That is the solution for this issue.
Thanks so much. 
Fixed.

Regards,
Ges

So, the fix will/won't be backported to F14? I'm on it, and am not moving for a while. Desktop 32-bit machine, not a laptop. Thanks.

probably won't be backported because tbh I have no idea what actually fixed it. seems to have been an accidental fix upstream.

numlockx works fine on F15 and F16 for me. F14 is EOL now, so I assume no fix will be released anymore for that version.

Shouldn't this bug be closed then ?

(In reply to comment #58)
> numlockx works fine on F15 and F16 for me. F14 is EOL now, so I assume no fix
> will be released anymore for that version.
> 
> Shouldn't this bug be closed then ?

Done.