[Scribus] How to print?

[BandiPat]

avox wrote:

> That's interesting. As Greg already mentioned, the bug that multiple copies
> are printed is fixed in the meantime.
> 
> Scribus uses mostly the same code for printing to file, printing directly or 
> printing with a custom command. For the latter two, the file
> ~/.scribus/tmp.ps
> is created. It is not deleted directly after the print, since some print
> commands
> do not copy the file and rely on it to exist for some time. It's only
> deleted when
> you print another file from Scribus (yes, there's a flaw in that logic).
> 
> For using a custom command, it executes <custom command> + " " + <filename>.
> When printing directly, it uses "lpr -P" + <printer name> + <cups options> +
> " " + <filename>.
> 
> Can you check the CUPS options you have set? That's the options button next
> to
> the printername combo. 
> Maybe CUPS has a log which tells us what options Scribus uses?
> 
> /Andreas
------------

I don't know if this will be of any help to you or not.  I'm posting the 
info from the CUPS log for the last test I just did.

I [04/Jun/2007:10:17:03 -0400] Adding start banner page "none" to job 84.
I [04/Jun/2007:10:17:03 -0400] Adding end banner page "none" to job 84.
I [04/Jun/2007:10:17:03 -0400] Job 84 queued on 
"EPSON_Stylus_Photo_R220_USB_2" by "tracerb".
I [04/Jun/2007:10:17:03 -0400] Started filter 
/usr/lib/cups/filter/pstops (PID 1253) for job 84.
I [04/Jun/2007:10:17:03 -0400] Started filter 
/usr/lib/cups/filter/pstoraster (PID 1254) for job 84.
I [04/Jun/2007:10:17:03 -0400] Started filter 
/usr/lib/cups/filter/rastertogutenprint.5.1 (PID 1255) for job 84.
I [04/Jun/2007:10:17:03 -0400] Started backend /usr/lib/cups/backend/usb 
(PID 1256) for job 84.

It seems it's sending the job or a job to CUPS successfully, but what's 
it is sending appears to be blank, thus the blank pages?  Although it 
does seem that the tmp.ps file is intact and the correct job/page. 
Hopefully that will be helpful to you.  I'll test more later, but right 
now, I don't seem to be getting any errors showing up in the logs and 
that may be because there are none.  CUPS is processing normally what it 
is getting from Scribus.

Pat

-- 
        ---Zenwalk v4.6--Linux 2.6.21---
         Registered Linux User #225206
     "Life's a garden, Dig It!"  --Joe Dirt