Bug 136851

Summary: KDE 3.5.5. - Setting 'Numlock=On' in kdmrc doesn't work
Product: [Unmaintained] kdm Reporter: Svein Liby <s.liby>
Component: generalAssignee: kdm bugs tracker <kdm-bugs-null>
Status: RESOLVED NOT A BUG    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Svein Liby 2006-11-04 22:25:21 UTC 
Version:            (using KDE KDE 3.5.5)
Installed from:    Unspecified Linux
Compiler:          gcc 4.1 
OS:                Linux

Distro: Debian Etch.
 
To have Numlock turned on at boot-time when the login screen appears, seting 'Numlock=On' in the KDM-config. file kdrmc has been working without problems until KDE 3.5.5. It doesn't matter if kernel 2.6.16 or 2.6.17 is selected at boot time. 
Xorg was recently upgraded to v.7.0.1, and I'm not sure if this is relevant ?
Comment 1 Nick Warne 2006-11-05 17:40:17 UTC 
I am not sure if this is relevant, but in your rc.local, add:

setleds +num

Nick
Comment 2 Svein Liby 2006-11-06 05:12:23 UTC 
Your suggestion is partly correct configuring X-terminals to always have
NumLock turned on. To make this work you'll have to apt-get the
"console-tool" package, and the numlockx package. In a directory called
/etc/console-tools, there is a file named config. containing the following
statement: #LED=+num. Uncommenting this file turns on NumLock at boot
time.
This is OK if you're only using X-terminals. I don't know about GNOME though.
The problem is: KDE 3.5.5 and/or Xorg 7.01 turns it off when initialized,
i.e. just before the KDM login-screen appears.
Why I care:
1. Using passwords containig digits.
2. Switching users on the same computer. One user may have an open
spreadsheet when another user needs to login. When the first user switch
back the numlock-key is turned off.
It's not a big deal, but quite annoying.


[bugs.kde.org quoted mail]
Comment 3 Oswald Buddenhagen 2006-11-06 09:05:00 UTC 
xorg7 must have changed something, indeed.
Comment 4 Oswald Buddenhagen 2007-05-12 11:43:48 UTC 
ok, this suddenly works again after an upgrade to Xorg 7.2, so i deny any responsibility and claim it was an X bug.