Package: lm-sensors Version: 1:3.1.1-4 Severity: normal On boot, lm-sensors fails to start whining that "Setting sensors limits: failed."
This is also what happens when running # invoke-rc.d lm-sensors start manually. This is easy to fix locally - when you know the cause. Setting the init scripts to verbose mode reveals that: # invoke-rc.d lm-sensors start Setting sensors limitsNo sensors found! Make sure you loaded all the kernel drivers you need. Try sensors-detect to find out which these are. No sensors found! Make sure you loaded all the kernel drivers you need. Try sensors-detect to find out which these are. failed! vinci:/etc/init.d# Unfortunately, scripts are not verbose by default. The problem is that /etc/init.d/lm-sensors runs /usr/bin/sensors, redirecting stderr to /dev/null. The problem is not so much in /usr/bin/sensors, but IMO more in /etc/init.d/lm-sensors expecting /usr/bin/sensors to succeed. Although I'm filing this at normal severity since this causes no breakage, this really should be fixed, considering that libsnmp now depends on libsensors4, which recommends lm-sensors. We don't want most Debian 6 installs on PCs to get this. --- System information. --- Architecture: i386 Kernel: Linux 2.6.30-2-686 Debian Release: squeeze/sid 990 testing security.debian.org 990 testing ftp.ca.debian.org 500 unstable ftp.ca.debian.org --- Package information. --- Depends (Version) | Installed ============================-+-============= sed (>= 4.0.5-1) | 4.2.1-6 lsb-base (>= 3.2-13) | 3.2-23 libc6 (>= 2.1) | 2.10.2-2 libsensors4 (>= 1:3.1.1) | 1:3.1.1-4 perl | 5.10.1-8 Package's Recommends field is empty. Suggests (Version) | Installed ========================-+-=========== sensord | read-edid | i2c-tools | -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
