From owner-freebsd-questions@freebsd.org Tue Sep 19 09:23:09 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 C8EC0E07E6C for ; Tue, 19 Sep 2017 09:23:09 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mailrelay10.qsc.de (mailrelay10.qsc.de [212.99.163.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.antispameurope.com", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3CAB673C88 for ; Tue, 19 Sep 2017 09:23:08 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de ([213.148.129.14]) by mailrelay10.qsc.de; Tue, 19 Sep 2017 11:22:59 +0200 Received: from r56.edvax.de (port-92-195-1-252.dynamic.qsc.de [92.195.1.252]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 26F763CC3F; Tue, 19 Sep 2017 11:22:58 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id v8J9MwoS004050; Tue, 19 Sep 2017 11:22:58 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Tue, 19 Sep 2017 11:22:58 +0200 From: Polytropon To: "manash pal" Cc: "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. Message-Id: <20170919112258.cf2362cf.freebsd@edvax.de> In-Reply-To: References: Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-cloud-security-sender: freebsd@edvax.de X-cloud-security-recipient: freebsd-questions@freebsd.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mailrelay10.qsc.de with 6E6426837DD X-cloud-security-connect: mx01.qsc.de[213.148.129.14], TLS=1, IP=213.148.129.14 X-cloud-security: scantime:.1366 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:23:09 -0000 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... -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...