Network printer: remote jobs hang,print if requeued locally

Kurt Pfeifle kurt.pfeifle at
Sat Jun 23 05:11:02 PDT 2007

> > Thank you for taking the time to respond.  My apologies if my
> > initial comments weren't clear.
> I didn't have time to follow this threat in detail.
> However, one question: could it be....
>  ....that the original job is passing CUPS unfiltered (your Windows
> client + Samba server + CUPS setup makes the job print as "raw"),
> which format is not what your print device is able to consume?
>  ....that your 2nd shoot, where you submit the spool file from the
> CUPS server triggers the CUPS "auto-typing" function for jobs and
> that leads to the correct filtering chain applied?

I now looked at the error_log attached to your last posting, Frnak.

It is exactly as I assumed:

D [22/Jun/2007:15:40:26 -0400] print_job: request file type is application/vnd.cups-raw.
D [22/Jun/2007:15:40:26 -0400] [Job 95] argv[3]="smbprn.00000026 Hello_World.txt"
D [22/Jun/2007:15:40:26 -0400] [Job 95] envp[21]="DEVICE_URI=socket://brn_60fb75:9100/"
D [22/Jun/2007:15:40:26 -0400] [Job 95] envp[22]="PRINTER=mfc420cn"
I [22/Jun/2007:15:40:26 -0400] Started backend /usr/lib/cups/backend/socket (PID 1078) for job 95.

No filtering, you see?

Your job named "Hello World.txt" is going unfiltered to the printer (did it arrive as pure ASCII text in CUPS?). The printer can't handle ASCII printing, or whatever the specific file is that passed CUPS unfiltered (if you used a PostScript driver on your Windows client, that driver might have added an incomprehensible PJL header....).

The spool file is the same jobfile that arrived. If you submit it a second time through CUPS, it will be auto-typed.

If autotyped as "text/plain", the filtering chain "texttops --> pstops --> pstoraster --> rasterto[mfc420cn]" will convert the file to something that is digestable by the print device.

If autotpyed as application/postscript, the filtering chain will be "pstops --> pstoraster --> rasterto[mfc420cn]".

What may have happened when you upgraded your SUSE to 10.x: you'll get a brand-new Samba; you'll get a brand-new CUPS; a lot of default settings will have changed, and you or your upgrade process didn't take care about them.

Most likely the added "cups options = ..." settings in Samba's smb.conf has biten you. It defaults to "raw" (even, or especially!, if you did not set it up yourself). You can check that by running this command

   testparm -vs | grep -i cups

("testparm -v" shows you *all* the settings used by Samba, even the ones it uses "silently").


Kurt Pfeifle
System & Network Printing Consultant --- Linux/Unix/Windows/Samba/CUPS
Infotec Deutschland GmbH - A RICOH Company ......... Stuttgart/Germany

More information about the cups mailing list