Package: lirc
Version: 0.8.3-2
Severity: normal

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I checked some other bug reports before writing this one, I found somethings 
about the LSB headers that where added and some things about the output when 
pressing keys. I would like to report that the bootlog of the init script of 
lirc is strange and possible not compliant. It outputs a single dot, and the 
driver outputs its version and PID and thinks like userspace ready. These 
things should not show up during boot. Could there be a good check on all the 
outputs of the scripts and the lircd itself? I would like to have a clean 
correct bootlog that makes sence. Thanks in advance.

- -- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages lirc depends on:
ii  debconf [debconf-2.0]        1.5.23      Debian configuration management sy
ii  libasound2                   1.0.16-2    ALSA library
ii  libc6                        2.7-13      GNU C Library: Shared libraries
ii  liblircclient0               0.8.3-2     infra-red remote control support -
ii  libusb-0.1-4                 2:0.1.12-13 userspace USB programming library

lirc recommends no packages.

Versions of packages lirc suggests:
pn  lirc-modules-source           <none>     (no description available)
pn  lirc-svga                     <none>     (no description available)
pn  lirc-x                        <none>     (no description available)

- -- debconf information excluded

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iJwEAQECAAYFAkjeZysACgkQ1WclBW9j5HmX3gP/VjEnbP9HdyWRWktHzjkp+ZXy
h5fvHGAwtsqYCoIU7J279ElMloSUK2i5VAZmdJ8J7I+ILQsKw/vHbcFrgFtI1alm
EQ4vqAVpVMJDaeIq9vdkqgydNCXEBlC6j/2TwgNMrT5Khhcg+Rz1kaoBcMkI1the
NQcO48TiXJs7eDmND4c=
=yQJZ
-----END PGP SIGNATURE-----



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to