[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#375926: marked as done (discover: Fails to detect and modprobe lp driver is parport is found)



Your message dated Fri, 18 Feb 2011 22:44:01 +0000
with message-id <201102182244.01852.elmig@debianpt.org>
and subject line 
has caused the Debian Bug report #375926,
regarding discover: Fails to detect and modprobe lp driver is parport is found
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
375926: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=375926
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: discover
Version: 2.0.7-2.1
Severity: important

Hi,

discover is not loading the lp driver when a parport device is found.
This leaves a system without a working /dev/lp? device, leading to
printing not working without manual setup by the user (e.g. adding
lp to /etc/modules).  The lp device is a fairly basic (but
important) device, which should work without user action.

See also #375395 for more information about the problem.


Regards,
Roger

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (990, 'unstable')
Architecture: powerpc (ppc)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17
Locale: LANG=en_GB.UTF8, LC_CTYPE=en_GB.UTF8 (charmap=UTF-8)

Versions of packages discover depends on:
ii  libdiscover2                  2.0.7-2.1  hardware identification library

discover recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Closing as #375395 with the explanation was already closed years ago.


--- End Message ---

Reply to: