Bug#369286: hplip: Deskjet printer is turned on on boot and nightly
Package: hplip
Version: 0.9.10-1
Severity: normal
Hi all,
I'm using Debian Unstable, and I thank you for the hplip package ;)
However, I found an annoying behaviour... When I boot my Debian, the printer is turned on, what is not really necessary.
Also, each night, the printer is turned on too... I found these messages in /var/log/messages:
May 28 06:26:19 localhost hpiod: removing usblp driver interface=0 for hp:/usb/deskjet_5100?serial=MY41A4K3X57A io/hpiod/device.cpp 462
May 28 06:26:19 localhost kernel: drivers/usb/class/usblp.c: usblp0: removed
Is it possible to disable this "auto-booting" of the printer ? I notice that only the power led was turned on, I have never eared the printer's mecanism.
Good luck ;)
KnuX.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-noinitrd
Locale: LANG=fr_FR@euro, LC_CTYPE=fr_FR@euro (charmap=ISO-8859-15)
Versions of packages hplip depends on:
ii adduser 3.87 Add and remove users and groups
ii coreutils 5.96-2 The GNU core utilities
ii cupsys 1.1.23-15 Common UNIX Printing System(tm) -
ii hplip-data 0.9.10-1 HP Linux Printing and Imaging - da
ii libc6 2.3.6-9 GNU C Library: Shared libraries
ii libcupsys2 1.1.23-15 Common UNIX Printing System(tm) -
ii libgcc1 1:4.1.0-4 GCC support library
ii libsnmp9 5.2.2-3 NET SNMP (Simple Network Managemen
ii libssl0.9.8 0.9.8b-2 SSL shared libraries
ii libstdc++6 4.1.0-4 The GNU Standard C++ Library v3
ii libusb-0.1-4 2:0.1.12-2 userspace USB programming library
ii lsb-base 3.1-5 Linux Standard Base 3.1 init scrip
ii python 2.3.5-5 An interactive high-level object-o
ii python-qt3 3.15-4 Qt3 bindings for Python (default v
Versions of packages hplip recommends:
ii cupsys-client 1.1.23-15 Common UNIX Printing System(tm) -
ii hpijs 2.1.9+0.9.10-1 HP Linux Printing and Imaging - gs
pn python-reportlab <none> (no description available)
-- no debconf information
Reply to: