Version: (using KDE 4.2.0) OS: Linux Installed from: Ubuntu Packages It seems that whenever KDE starts, either from first startup, or by logging out and back in, or restarting X, the numlock becomes disabled. I have a session going with numlock enabled, then restart my session for whatever reason, then numlock isn't enabled any more.
You can configure it to be enabled at startup from systemsettings->keyboard & mouse->keyboard->numlock on kde startup. I think you did not notice that option.... :)
Well, you're right, I had noticed that setting. However, looking at it now, it is currently set to "Leave unchanged". My computer turns on the numlock at boot time, and it's turned off when I log in. It's on when I'm in a session, and when I log out or restart my session, it's turned off. Therefore, the setting isn't working as designed. I could just set it to "Turn on", but if the default action is "Leave unchanged" (as it appears to be, since I've never modified that setting), then the default setting is working improperly and should probably be fixed. Unless I'm crazy and what I've described only happens for me that is.
The problem is that this is not something that KDE controls. numlock goes off when X starts, that is X's behavior. KDE can change it after logging in and there are three options: Turn on: turn on numlock no matter what it was before login Turn off: turn off numlock no matter what it was before login Leave unchanged: leave numlock to the same state as it was before login. Before login, normally kdm (or some other login manager) runs. Now, if you are in kdm's screen and you enable numlock, with "leave unchanged" it will be left unchanged when you enter your password and log in. With "turn off", though, it will be turned off right after login. I hope you understand what I mean. KDE can control what numlock does by the time the user logs in. Before that, numlock is not controlled by KDE. And bear in mind that X always starts with numlock disabled.
Well, to me the "Leave unchanged" option should remember the numlock setting from the last session, not necessarily from KDM and certainly not the X setting. When I'm logged into a session, and I log out and back in again, it's expected that some settings are remembered, like widgets, startup programs, and the last known state of numlock. Besides, if the "Leave unchanged" option starts remembering from KDM and propagates to KDE, then why even have the option at all? Like you said, X turns off numlock, and this setting takes into account the setting while in KDM, then in most cases, numlock will default to off with this option enabled. I can't speak for all users, but in my experience not many people use the numpad for their passwords (of course, some might argue this, but then they'd be in support of what I'm proposing).
Ok, I understand. Your point is valid. I'm reopening and retitling this bug.
Thanks :)
*** Bug 249349 has been marked as a duplicate of this bug. ***
You can add an extra option: "Remember from the last time". And this option probably should be the default since KDE already memorizes mixer levels and other setting.
As Yuri points out, there's a setting for this.