By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 561 - Keyboard numlock light no longer works
Summary: Keyboard numlock light no longer works
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: tdebase (show other bugs)
Version: R14.0.0 [Trinity]
Hardware: i386 Debian Squeeze
: P5 major
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2011-10-27 04:29 CDT by Nick Leverton
Modified: 2012-10-19 15:37 CDT (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Leverton 2011-10-27 04:29:52 CDT 
My kbstatus applet confirms that kb state is being correctly changed, but the numlock light is permanently off.

Flagging this until I can do more investigation.  Not related to my xorg update last night as it was the same under xorg 7.5.

Note that I've had a strangeness for some time in KDE 3.5, where my numlock light showed the *opposite* of the numlock status.   I suspect interactions between input subsystem and KDE forcing numlock state at startup.  Having the light not work at all, however, is new to TDE 3.5.13.
Comment 1 Timothy Pearson 2011-10-27 09:57:07 CDT 
Interesting--the code that handles Numlock autosetup was modified some time back to try to fix the incorrect indication issue.  I will need to look into how the light can be forced back on...
Comment 2 Timothy Pearson 2011-10-27 10:22:55 CDT 
The change to Trinity appears to be the use of XKB instead of the unreliable XTEST hacks.  That being said, the offending section of Trinity code was originally taken from NumLockX and I will see if it needs an update.
Comment 3 Timothy Pearson 2011-10-27 10:41:46 CDT 
I have updated the numlockx source that was embedded in the kxkb keyboard module, but I suspect that you will still experience problems on Squeeze.  This change was made in SVN revision 1261045.

See this thread for more information: http://forums.debian.net/viewtopic.php?f=10&t=55725&start=15
Comment 4 Nick Leverton 2011-10-27 13:34:19 CDT 
Thanks for the update, I can confirm it doesn't fix numlock LED in Squeeze, but for me this is a low priority problem - I've been used to using the kbstatus applet anyway since Lenny/Squeeze had other issues with keyboard state.
Comment 5 Timothy Pearson 2011-10-27 13:43:46 CDT 
Also, from a certain perspective no indication is better than erroneous indication.  This issue needs to be looked at in more detail for 3.5.14.
Comment 6 Ian Goddard 2011-11-21 17:20:24 CST 
In my case neither the Num lock nor the Caps lock lights work consistently.  Sometimes they work, sometimes they don't.
Comment 7 Timothy Pearson 2012-01-20 00:05:22 CST 
It appears that this issue is caused by the tsak daemon incorrectly filtering LED events.

Raising priority to block R14.0.0.
Comment 8 Timothy Pearson 2012-01-20 03:00:20 CST 
Fixed in GIT hash 8468d9b.

Thanks for reporting!