You are not logged in.
Pages: 1
After the last system update of today, I noticed that the numlock led is off when I log into KDE: but if I hit a number on the keypad, it work as expected (I mean, it gives me a number...). If I hit the numlock key itself, the led switches on but the keypad doesn't work: 8 and 2 are mapped to up and down.
I wonder which update might have caused this, since the led has worked normally until an hour ago...
Does anybody have some hint?
Offline
Offline
And old issue that i crossed over many times too... But i think it isn't kde specific, i never use kde so, maybe xorg problem...
Offline
Well, I'll be...I thought it was an E17 e-cvs problem. Googling points to xorg problems in the past with Ubuntu but that was on laptops. Mine is a desktop computer, btw. Any ideas out there???
Last edited by bgc1954 (2008-03-29 15:05:24)
Time is a great teacher, but unfortunately it kills all its pupils ... - Louis Hector Berlioz
Offline
I just noticed that if I switch to another virtual console, the led works right: I type numbers when the led lights on. So the "inversion" happens only in X.
Offline
I have a similar problem here after upgrading to Gnome 2.22. LED indicates active numpad, but typing numbers doesn't work in X (it does work in console-only mode); but it doesn't work either with numlock being deactivated. :-(
Offline
Same problem for me using XFCE4.
Offline
I know I'm resurrecting an old thread, but thought this may be appreciated. At least I know it's a HUGE bother for me. What seems to work with me is to enable numlock through the slim:
/etc/slim.conf
numlock on
What I used to have in Gentoo, is there was a numlock script that was loaded upon entering run level 3. So I guess another way would be to make a wrapper script in /etc/rc.d and have it called upon.
The issue is only there when I have numlockx in ,xinitrc.
Last edited by Berticus (2008-08-07 03:37:16)
Offline
my .xinitrc file for slim
#! bin/bash
numlockx &
exec startxfce4
#exec awesome
nvidia-settings -a InitialPixmapPlacement=2 -a GlyphCache=1
I use numlockx and start it in .xinitrc and never had numlock issue's
Last edited by rooloo (2008-08-07 12:27:12)
Offline
for me, that's actually what caused the problem.
Offline
Pages: 1