Package: ledcontrol Version: 0.5.2-11+b1 Severity: serious I installed the ledcontrol package. After this, I was not able to type various things on my laptop keyboard. For example, the "u" key generated the digit "4".
This appears to have been because ledcontrol turned the num lock "led" on. As it happens the actual led on my laptop is broken and does not light up. But like many keyboard, my laptop behaves differently when num lock is lit: it generates digits, for example, for a number of alphabetic keys. I attempted to fix the problem by purging ledcontrol (which involved cutting and pasting some letters to type the command!) but this didn't help. Changing to VC 1 with "chvt" (the usual vc switch escape keys were nonfunctional) and then back didn't help. The normal way for me to turn on and off num lock from the laptop keyboard - pressing shift+scroll lock - didn't work, although it usually does work to turn it on and off. Luckily in my configuration and circumstances I was able to recover by plugging in a separate USB keyboard. It lit its num lock LED when plugged in. Pressing num lock on the separate keyboard caused its num lock LED to go out and fixed the main laptop keyboard. The bug here is that the ledcontrol package should under no circumstances change LED states simply by being installed, until it has been explicitly told to do so. That's because "LEDs" are often used by input devices to control keymaps etc., and changing their state can often be very disruptive. Ian. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
