From owner-freebsd-questions@FreeBSD.ORG Tue Apr 8 14:19:41 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 43714931 for ; Tue, 8 Apr 2014 14:19:41 +0000 (UTC) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 04E831694 for ; Tue, 8 Apr 2014 14:19:40 +0000 (UTC) Received: from r56.edvax.de (port-92-195-84-247.dynamic.qsc.de [92.195.84.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx02.qsc.de (Postfix) with ESMTPS id 1102727843; Tue, 8 Apr 2014 16:19:30 +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 s38EIQl5005267; Tue, 8 Apr 2014 16:18:26 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Tue, 8 Apr 2014 16:18:26 +0200 From: Polytropon To: "O. Hartmann" Subject: Re: print/cups: since update to 1.7.1: error : Send-Document client-error-document-format-not-supported Message-Id: <20140408161826.06beeddf.freebsd@edvax.de> In-Reply-To: <20140408154210.1aec26a8.ohartman@zedat.fu-berlin.de> References: <20140408154210.1aec26a8.ohartman@zedat.fu-berlin.de> 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 Cc: FreeBSD Questions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Apr 2014 14:19:41 -0000 On Tue, 8 Apr 2014 15:42:10 +0200, O. Hartmann wrote: > Since the update of print/cups from 1.5.X to 1.7.1 I'm unable to print from LibreOffice, > Firefox or Claws-Mail, but I can print LaTeX created documents via xpdf or Postscript > directly by naming the printqueue. Strange, then maybe it's not really a CUPS problem? > Checking the access- and error logs of cups when failing, I always see this weird message > (not for the particular queue, but for all): > > access_log: > "POST /printers/OJ8600PRO_SW_A4_simplex_draft HTTP/1.1" > 200 36510 Send-Document client-error-document-format-not-supported > > error_log: > [Client 14] Returning IPP client-error-document-format-not-supported for Send-Document > (ipp://localhost:631/printers/OJ8600PRO_SW_A4_simplex_draft) from localhost Oh the fun of CUPS error messages, how wonderful... ;-) Check your configuration files. Sometimes when an update is done, things change in those files, so the older ones do not keep working. Especially look for filter definitions for the MIME types which seem to be the basis of how CUPS invokes preprocessing. If you use the "Modify printer" option in the web interface, configuration files should be updated automacially with the new required settings (as CUPS can maintain those files without the user manually editing them). Reason: Within X and especially from LibreOffice to CUPS (but maybe also from other applications), data is sent "with no type" (which is application/octet-stream), whereas other applications declare a type (like application/pdf or image/png when addressing the printer input queue). CUPS seems to have lost the ability for properly preprocessing those "raw" data (which, sent from LO, actually is PS). You'll probably have to "cupsenable" and "cupsaccept" the printer afterwards. > Has anybody ideas where to look further? Check if the printer's "personality" (it's often really called personality!) has changed and if the printer refuses to accept anything that is not PS (maybe PCL?). Maybe one of your CUPS dependencies hasn't been updated properly. Are you using some special print filters in combination with CUPS? Check /usr/local/etc/cups/mime.convs as described above. > I was wondering if I might be the only one with trouble after that cups update. Not yet, still using 1.5.4. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...