I can confirm this bug. It's there since I switched from edgy to feisty (kubuntu) and after some debugging I came to the following conclusions:
- The cause for this behavior is that the PS/2 keyboard is not recognized as a new device by the kernel until the user presses a key. If you press this first key when entering your user/password, dmesg shows the new keyboard device as its very last entry: [ 80.944130] input: AT Translated Set 2 keyboard as /class/input/input5 If you press the first key in an earlier stage of the boot process, before X is started, the LED will switch to off at that point (if activated before by BIOS) and dmesg shows that the keyboard has been detected at that moment. This first key does not act as a NUM-key replacement but simply forces the kernel to see the keyboard. the kernel then immediately sets the numlock LED to the kernels internal numlock state, which is OFF. Then kdm sets the numlock LED to the value specified in /etc/kde3/kdm/kdmrc, if configured. - The bug vanishes when acpi=off is added to the kernel parameters. In this case the keyboard device is detected at the beginning of the boot process: [ 20.970702] input: AT Translated Set 2 keyboard as /class/input/input1 shortly after this line [ 20.903071] serio: i8042 KBD port at 0x60,0x64 irq 1 (For me, this only works on reboots but not on cold starts.) - Therefore it seems this bug is not XServer, kdm, gdm, kde, gnome, ... related. -- Numlock turns off at login and misses first keystroke https://bugs.launchpad.net/bugs/119259 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
