Bug 197351 - NumLock led behaves inversely if num lock is turned on kde4 startup
Summary: NumLock led behaves inversely if num lock is turned on kde4 startup
Status: RESOLVED DUPLICATE of bug 187410
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: 4.2.2
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-21 11:22 UTC by Hakan Bayindir
Modified: 2009-06-21 22:20 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hakan Bayindir 2009-06-21 11:22:00 UTC
Version:            (using KDE 4.2.2)
OS:                Linux
Installed from:    Debian testing/unstable Packages

When NumLock on KDE startup is set to Turn on in Keyboard & Mouse in System settings, NumLock turns on but not its LED on keyboard. This results in a reversely behaving (NumPad is enabled when LED is off, disabled when on) NumLock and happens consistently.

Expected behaviour:
NumLock LED should turn on when NumLock is turned on on KDE startup
Num pad should work when NumLock LED is on
Num pad should perform other functions (home, end, arrows and such) when LED is off.

How to reproduce:
1- Go to system settings
2- Open keyboard and mouse
3- Select Turn on under NumLock on KDE startup section under Keybard tab.
4- Restart computer (I don't know if restarting KDE or logging off and on will reproduce it)
5- Viola! You have an inversely behaving NumLock LED.

Notes:
- Keyboard is a Microsoft Ergonomic Keyboard 4000 USB but reproduced in an HP laptop and other USB keybards successfully.
- Bug is present since 3.5.9 days.
- Bug disappears in virtual terminals (VTs).
Comment 1 Dario Andres 2009-06-21 22:20:45 UTC
Thanks

*** This bug has been marked as a duplicate of bug 187410 ***