Re: f-spot printing problem

[Adam Tauno Williams <awilliam whitemice org>]

On Thu, 2013-12-05 at 10:32 +0000, Dave Howorth wrote: 
> Stephen Shaw wrote:
> > Can you run f-spot from the console with f-spot --debug and see if there is
> > any output there?
> I did, but there was no debug output, apart from it telling me as it
> opened each image.
> But I found a solution. I can print OK to a PDF file, and I found that
> the acroread print dialog has a button squirreled away that says 'print
> as image' (or similar, I'm not in front of that computer now). Clicking
> that allowed the print to work :)

"print as image" sounds correct; for many types of jobs this is sadly
'normal' when printing from acroread.

If you have multiple printers does it print on one and not the other?
Our older HP's frequently need to be printed-as-image, while newer
Brother's [with x16 the RAM] will print a document without issue.  These
are all "page printers";  they need to render and entire page in memory
before printing can begin, with print-as-image Acrobat [or whatever]
does this first scaling the contents down the the resolution of the page
before submitting the job to the printer.  Otherwise the image [or
whatever] is simply encapsulated in the PDF / Postscript and it is the
printer's job to deal with it ... but the printer probably has older
firmware, a less powerful CPU, less memory, and no virtual memory.

Does it also fail if printed from Evince?