From owner-freebsd-questions@freebsd.org Tue Sep 19 09:47:30 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2A781E0916A for ; Tue, 19 Sep 2017 09:47:30 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.fagskolen.gjovik.no", Issuer "Fagskolen i Gj??vik" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C586B74BF4 for ; Tue, 19 Sep 2017 09:47:29 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.15.2/8.15.2) with ESMTPS id v8J9lJ1H072580 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Tue, 19 Sep 2017 11:47:19 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.15.2/8.15.2/Submit) with ESMTP id v8J9lJ0o072577 for ; Tue, 19 Sep 2017 11:47:19 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Tue, 19 Sep 2017 11:47:19 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Sender: Trond.Endrestol@fagskolen.gjovik.no To: "freebsd-questions@freebsd.org" Subject: Re: how to fix " unable to print , broken pipe ! " when passing through CUPS protocol after successfully adding printers in vmware. In-Reply-To: <20170919112258.cf2362cf.freebsd@edvax.de> Message-ID: References: <20170919112258.cf2362cf.freebsd@edvax.de> User-Agent: Alpine 2.21 (BSF 202 2017-01-01) Organization: Fagskolen Innlandet OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.fig.ol.no X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Sep 2017 09:47:30 -0000 On Tue, 19 Sep 2017 11:22+0200, Polytropon wrote: > On Tue, 19 Sep 2017 14:10:37 +0530, manash pal wrote: > > I am very new to FreeBSD, after stuyding at google and youtube, I have > > started to wipe out some embarrassment to go through this unix like os. > > however, after succussfully adding my printer through cups , I tried to > > proceed printing of a pdf document. but , got a repeated reply " UNABLE TO > > PRINT DOCUMENT, BROKEN PIPE ! " what does it mean ? > > Depends. The error "broken pipe" indicates a problem with data > transmission between programs, usually the kind of "output of > program A is input of program B". In CUPS, this piping concept > creates a "data flow" through the different parts of the whole > printing mechanism (technically not fully correct, but think of > it like entry queue -> printer spooler -> printer filter -> out- > out channel to printer). On that way, something happened. > > Open your web browser and go to http://localhost:631/ where > you find the CUPS web interface. In the printer listing, you > can see the full error. > > More information can be obtained from the CUPS log files, > for example /var/log/cups/error_log. See if you find additional > details there. > > Sidenote: When you say "I print a PDF document", please specify > _how_ you print it, as there are several ways to do so, and > this could also be part of the problem you're experiencing. > For example, > > % lpr somefile.pdf > > is one way to print a PDF document, but so is opening it in > a PDF viewer (which there are at least 5 availabe on FreeBSD) > and hitting the "Print" button. Printing PDFs from Gimp is > possible, too. > > The same (!) applies for the error message: Where did you read > it? Which program provided the error message? CUPS? The PDF > viewer you printed from? Was it a console message? If possible, > provide the full text of the error message. In many cases, the > error message text contains 50 % of the solution of the problem > it is informing you about. > > The fewer guesswork is involved, the easier is it to get the > desired diagnostic result. :-) > > > > > and how to solve this > > problem ? > > Without proper diagnostics, there is nothing that I can say... Watch your PATH. I've seen plenty of CUPS and lpd(8) problems due to /usr/bin/l* being used instead of /usr/local/bin/l*, and vice versa. -- Trond.