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

Bug#399126: marked as done (installation: Debian Installer etch RC1 installs lpr package )

Your message dated Wed, 08 Sep 2010 03:58:21 +0000
with message-id <E1OtBnh-0005Q4-0t@ravel.debian.org>
and subject line Closing old installation report #399126
has caused the Debian Bug report #399126,
regarding installation: Debian Installer etch RC1 installs lpr package 
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.)


-- 
399126: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=399126
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: installation
Severity: normal

Having installed using etch RC1 candidate and choosing the default 
'desktop' configuration, I was no longer able to print from many 
applications.  It turned out that the applications I was having 
problems with were trying to use lpr commands (like Adobe Acrobat).

I was further confused since a recently installed Ubuntu machine had no 
such problems.  After several hours lost time, I found that in the 
Debian install, lpd was not talking with CUPS.  This 
was due to the fact that the lpr package was the old crufty one and not 
cupsys-bsd (which is necessary to allow lpr to communicate with CUPS).

Since CUPS is installed by default, shouldn't cupsys-bsd be installed by 
default too?  Many users will be clueless as to the solution (replacing 
lpr with cupsys-bsd).  Ubuntu seems to make this choice, why shouldn't 
Debian as well.

A second thing I found related to this is that lpr didn't work at all 
to start (basic install), due to the fact that the hosts file had the 
the 'hostname' bound to 127.0.1.1, and the lpd daemon isn't listening on that 
address.  This  caused commands like lpq to timeout waiting for the 
host.  The problem was solved by either commenting out the binding for 
the hostname, or binding it to 127.0.0.1 instead of 127.0.1.1.

e.g. hosts file

127.0.0.1       localhost
# JAH commented out to get lpq working.  DNS resolves hostname.
#127.0.1.1      provolone.East.Sun.COM provolone
...

Once cupsys-bsd is installed, lpq and lpr work fine with the 127.0.1.1 
hostname binding in the hosts file, since they now talk to CUPS in a 
different way (I verified this to be the case, but didn't bother 
understanding the exact details).

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i586)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-486
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

--- End Message ---
--- Begin Message --- 
We are closing this installation report for one of the following
reasons:
- it was reported with a pre-lenny version of Debian
  Installer.
- indications in the installation report give the feeling that
  the reported problem waslying in another software, unrelated to
  D-I, which we can't easily identify.
- indications in the installation report suggest that it may have been
  fixed in a more recent version of a D-I component
- it was successful and we forgot closing it..:-)
- it has no information we consider useful


The D-I team is currently in the process of cleaning out the old spool
of installation reports that haven't bene processed yet. 

In case you think that the problem you reported has chances to be
still present, please reiterate your installation test with
a more recent image of D-I, if you're in position of doing this.

You'll find daily builds at
http://www.debian.org/devel/debian-installer. We recommend you choose
the netboot image, in the "daily builds section", then choose to
install "squeeze" when prompted.

If some problems are found, please report them with a new bug sent
against installation-reports.

Many thanks for your understanding and your help improving Debian,
past and present.

--- End Message ---
Reply to: