[cups.development] CUPS Print Self Test Page does not work fornon-Postscript printers

George Liu george.liu at ricoh-tech.com
Tue Jan 11 12:12:40 PST 2011


What I'm seeing from CUPS error_log is CUPS did not send "print self-test page" to the filter chain, instead, it communicate with printer directly.
I understand different printers supports different print format.

May I suggest to change the wording in the "print self-test page" from "You are using the wrong driver" to "Printer Self-Test Page"?
The string I believe is located in commandtops filter.
 

------ For Print Self-Test Page ---------
D [08/Jan/2011:00:24:38 -0800] [Job 127] envp[19]="PPD=/etc/cups/ppd/2550PXL.ppd"
D [08/Jan/2011:00:24:38 -0800] [Job 127] envp[20]="RIP_MAX_CACHE=auto"
D [08/Jan/2011:00:24:38 -0800] [Job 127] envp[21]="CONTENT_TYPE=application/vnd.cups-command"
D [08/Jan/2011:00:24:38 -0800] [Job 127] envp[22]="DEVICE_URI=socket://172.30.4.227:9100"
D [08/Jan/2011:00:24:38 -0800] [Job 127] envp[23]="PRINTER_INFO=2550PXL"
D [08/Jan/2011:00:24:38 -0800] [Job 127] envp[24]="PRINTER_LOCATION="
D [08/Jan/2011:00:24:38 -0800] [Job 127] envp[25]="PRINTER=2550PXL"
D [08/Jan/2011:00:24:38 -0800] [Job 127] envp[26]="CUPS_FILETYPE=document"
D [08/Jan/2011:00:24:38 -0800] [Job 127] envp[27]="FINAL_CONTENT_TYPE=printer/2550PXL"
I [08/Jan/2011:00:24:38 -0800] [Job 127] Started filter /usr/lib/cups/filter/commandtops (PID 11124)
I [08/Jan/2011:00:24:38 -0800] [Job 127] Started backend /usr/lib/cups/backend/socket (PID 11126)




------ For Print Test Page -------------
D [08/Jan/2011:00:27:28 -0800] [Job 128] envp[19]="PPD=/etc/cups/ppd/2550PXL.ppd"
D [08/Jan/2011:00:27:28 -0800] [Job 128] envp[20]="RIP_MAX_CACHE=auto"
D [08/Jan/2011:00:27:28 -0800] [Job 128] envp[21]="CONTENT_TYPE=application/vnd.cups-banner"
D [08/Jan/2011:00:27:28 -0800] [Job 128] envp[22]="DEVICE_URI=socket://172.30.4.227:9100"
D [08/Jan/2011:00:27:28 -0800] [Job 128] envp[23]="PRINTER_INFO=2550PXL"
D [08/Jan/2011:00:27:28 -0800] [Job 128] envp[24]="PRINTER_LOCATION="
D [08/Jan/2011:00:27:28 -0800] [Job 128] envp[25]="PRINTER=2550PXL"
D [08/Jan/2011:00:27:28 -0800] [Job 128] envp[26]="CUPS_FILETYPE=document"
D [08/Jan/2011:00:27:28 -0800] [Job 128] envp[27]="FINAL_CONTENT_TYPE=printer/2550PXL"
I [08/Jan/2011:00:27:28 -0800] [Job 128] Started filter /usr/lib/cups/filter/bannertops (PID 11153)
I [08/Jan/2011:00:27:28 -0800] [Job 128] Started filter /usr/lib/cups/filter/pstopdf (PID 11154)
I [08/Jan/2011:00:27:28 -0800] [Job 128] Started filter /usr/lib/cups/filter/pdftopdf (PID 11155)
I [08/Jan/2011:00:27:28 -0800] [Job 128] Started filter /usr/lib/cups/filter/foomatic-rip (PID 11156)
I [08/Jan/2011:00:27:28 -0800] [Job 128] Started backend /usr/lib/cups/backend/socket (PID 11158)




-----Original Message-----
From: cups-dev-bounces at easysw.com on behalf of Michael Sweet
Sent: Tue 1/11/2011 11:57 AM
To: Mirror of cups.development Newsgroup
Subject: Re: [cups.development] CUPS Print Self Test Page does not work fornon-Postscript printers
 
On Jan 11, 2011, at 11:51 AM, George Liu wrote:
> I'm using Ubuntu 10.10 with CUPS 1.4.4.
> 
> I setup a printer queue for a PCL-XL printer, using socket 9100 protocol.
>> From CUPS web interface, I picked "Maintenance-> Print Self Test Page".
> 
> The test page printed, however, it printed the following information:
> 
> -----------------------------------------------------------------
> %!
>  userdict dup(\004) cvn{}put (\004\004)cvn{}put
>                            % You are using the wrong driver
> -----------------------------------------------------------------
> 
> It seems that the command did not go through filter chain and landed in printer directly. What will confuse the user is the sentence "You are using the wrong driver".
> 
> On a Postscript printer, it worked fine, and printed out printer model name along with PSVersion.
> 
> Can we change the print self-test content to be something neutral?

Well, the content can't be made that neutral because printers don't support a standard set of file formats (yet).

However, CUPS 1.4 and later *do* use a new (simple) CUPS banner format for the test page instead, using a filter to generate the necessary content for the printer.  It sounds like either Ubuntu's CUPS is broken or the correct driver was not chosen for the printer.

________________________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair

_______________________________________________
cups-dev mailing list
cups-dev at easysw.com
http://lists.easysw.com/mailman/listinfo/cups-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cups.org/pipermail/cups-devel/attachments/20110111/bca1d135/attachment.html>


More information about the cups-devel mailing list