severity 609916 important
thanks
Hi Ian
I agree with you that it may not be the best thing to change the
leds on the system. However I do not agree with you that a software
component should never change anything by mearly being installed.
If you follow that reasoning (for example) apache should never open
any network ports by default.
ledcontrol contains a daemon process to manage the leds. The default
is to start the daemon.
>From the documentation:
ledd The LED daemon. ledd must be running when the other programs
are used. On startup, it executes programs and/or scripts to
tell it how to set the LEDs. It is configured in ledd.conf.
What we can do to solve this issue is to change the default for ledd
so that it do not start by default. Most people do however expect daemons
to be started when installed.
The reason for your serious problem is obviously because you have a
broken keyboard. I do not expect normal software components to be able
to handle broken hardware.
I'm not sure this should be fixed, but I'm open for discussion. However
serious is a bit hard as it would remove the package from next release
and this have been the case for all releases with ledcontrol as far as
I can tell. So it is not a new problem.
Due to this reasoning I'm lowering the severity of this bug with a hope
that we can discuss it.
Best regards,
// Ola
PS. The package is up for adoption. Anyone is free to take the package
over, and if that person have a different opinion I will not object.
DS.
On Thu, Jan 13, 2011 at 07:36:33PM +0000, Ian Jackson wrote:
> 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.
>
>
>
--
--------------------- Ola Lundqvist ---------------------------
/ o...@debian.org Annebergsslingan 37 \
| o...@inguza.com 654 65 KARLSTAD |
| http://inguza.com/ +46 (0)70-332 1551 |
\ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 /
---------------------------------------------------------------
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
