You are not logged in.
Hi,
I'm using Arch64, I do a -Syu almost every day.
I'm having some problems with numlock. Suddenly, it started to behave badly: even when its led is enabled, the keypad doesn't work. I have to press it twice to make it work as usually (i.e. led enabled and keypad working).
I have realized that numlock turns on automatically when booting, concretely when loading udev rules, but I have taken a look on them and I can't see anything related to it.
Is anyone having any problems with numlock? I don't remember when it started failing, but some weeks ago it worked ok. I was hoping it was a temporary problem, but it isn't
Offline
Yes I have exactly the same problem and no fix yet
Offline
I've had this problem for months. I ended up 'solving' it by creating a desktop file for it and starting it as an application at start up. It's not pretty but it works.
Last edited by skottish (2008-02-03 20:04:53)
Offline
Same thing. I just know and I press it once or thrice. I've also started to use the other numbers (above the letters on my keyboard).
Offline
I've had this problem for months. I ended up 'solving' it by creating a desktop file for it and starting it as an application at start up. It's not pretty but it works.
Interesting, would you mind sharing this little trick with us?
Offline
Interesting, would you mind sharing this little trick with us?
I have a text file named numlockx that's in ~/.local/share/applications. This is the contents:
[Desktop Entry]
Hidden=false
Name[en_US]=numlockx
NoDisplay=true
Exec=numlockx
Type=Application
Version=1.0
StartupNotify=false
Name=numlockx
Terminal=false
In E17 I set it active by Configuration--> Configuration Panel--> Applications--> Startup Applications. I also run stalonetray the same way.
Offline
Thanks alot skottish, nice, problem solved
Offline
Same problem here with i686 and KDEmod. :-/
Last edited by defcon (2008-02-25 17:08:45)
Registed Linux User 608596
Offline