Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 8 Apr 2014 11:16:32 -0400
From:      Thomas Hoffmann <trh411@gmail.com>
To:        FreeBSD Questions <freebsd-questions@freebsd.org>
Cc:        "O. Hartmann" <ohartman@zedat.fu-berlin.de>
Subject:   Re: print/cups: since update to 1.7.1: error : Send-Document client-error-document-format-not-supported
Message-ID:  <CAB7-od=HABwzD-b%2Bt9NnMFoh1NBbD637WhbERkTb0oHNiDaP=w@mail.gmail.com>
In-Reply-To: <20140408154210.1aec26a8.ohartman@zedat.fu-berlin.de>
References:  <20140408154210.1aec26a8.ohartman@zedat.fu-berlin.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 8, 2014 at 9:42 AM, O. Hartmann <ohartman@zedat.fu-berlin.de>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.
>
> 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
>
> This happens with the "rescued" configuration of the printing system as
> well with a
> brand-new setup. Googling reveals, that maybe /var/db/cache could be the
> culprit, but I
> deleted all files there as well as other spool folders and I already setup
> each printer
> from scratch since I suspected changes in the configs.
>
> Has anybody ideas where to look further?
>
> I was wondering if I might be the only one with trouble after that cups
> update.
>
> Please CC me when responding,
>
> thanks in advance,
>
> Oliver
>

Some folks on the Forums reported that the (re)-installation of
print/cups-filter resolved this issue for them. Maybe for you too?

For reference: https://forums.freebsd.org/viewtopic.php?f=46&t=45738

-Tom



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAB7-od=HABwzD-b%2Bt9NnMFoh1NBbD637WhbERkTb0oHNiDaP=w>