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

Re: basics of CUPS troubleshooting

On Fri, Jun 15, 2018 at 3:36 PM, Brian <ad44@cityscape.co.uk> wrote:
On Mon 11 Jun 2018 at 18:40:49 -0500, Mark Copper wrote:

> On Tue, May 29, 2018 at 2:29 PM, Brian <ad44@cityscape.co.uk> wrote:
> > On Mon 28 May 2018 at 18:20:13 -0500, Mark Copper wrote:
> >
> > > Having upgraded to Stretch, a file that I need to print no longer prints
> > > properly. (It did before.)
> > >
> > > I am sure the difficulty is so idiosyncratic no one here will have
> > > experienced it. So I'm not asking how to fix it specifically.  Rather I'm
> > > looking for advice how to isolate the difficulty, generally speaking.
> >
> > What is offered in the printing section of the wiki could help.
> >
> Thanks for this. I was unaware.
> The problem I'm seeing seems to be in the CUPS filter gstoraster. That is,
> all is well at the preceding step:
> # /usr/sbin/cupsfilter -p /etc/cups/ppd/Zebra.ppd -m
> application/vnd.cups-pdf -o orientation-requested=3 tag_generator.pdf >
> out.pdf

The output of pdfinfo for tag_generator.pdf would be useful.
> Well, almost. It was necessary to include the "orientation-requested=3"
> option to keep the document from rotating.

That directive produces a rotation of 0 degrees. It is difficult to see
how it promotes or stops rotation.

> But at the next step, the document is laid on its side no matter the
> orientation requested:

"laid on its side" means?

Thanks for response.

Here is pdfinfo for input pdf file:
$ pdfinfo tag_generator
Producer:       PDF::API2 2.023 [linux]
Tagged:         no
UserProperties: no
Suspects:       no
Form:           none
_javascript_:     no
Pages:          1
Encrypted:      no
Page size:      90 x 144 pts
Page rot:       0
File size:      14233 bytes
Optimized:      no
PDF version:    1.4

I'm unable to reproduce the autorotation in the absence of orientation-requested=3 option.  I must have been mistaken. Sorry.

"laid on its side" to mean rotated 90° clockwise.

Reply to: