Hello, On Oct 19 11:05 Rejaine Monteiro wrote (shortened):
I'm using CUPS and a IPP/Xerox printer.
This printer works fine with Suse 9.0 using driver (PPD files) "HP LaserJet Plus" or "Xerox Docuprint P12 ljet2p"
But don't work with Suse 9.2 with this same drivers
I think it works with this same drivers but what seems to fail is the plain data transfer to the printer by the ipp/http backend. Note the difference between drivers (i.e. filtering) and data transfer (i.e. spooling and what the backends do), see http://portal.suse.com/sdb/en/2004/05/jsmeix_print-cups-in-a-nutshell.html
So, I don't think this errors is caused by cups, incorrect configuration or an incorrect driver, because this drivers and cups configurations are the same in Suse 9.0 and all works fine...
The ipp/http backend has changed from 9.0 to 9.2 and the new version seems to detect a problem with the data transfer to the printer which may have been ignored by the old version. I.e. I think it has worked before only by luck.
The Printer URI is http://172.22.10.33:631/Print
Why do you use the most complicated protocol (IPP) for only plain data transfer to the printer? It is well known that many network printers have somewhat problematic implelentations of the IPP protocol (e.g. some IPP functionality may be missing) and then the CUPS ipp/http backend fails to communicate correctly with such a device. It is recommended to use the simple TCP socket data transfer if it is supported by the printer. Look for a free port at your printer (often it is port 9100) - read your printer's manual or use "nmap". Alternatively any network printer should support the LPD protocol. See the administration manual.
Debuging cups: ... I [19/Oct/2005:10:43:45 -0200] Started filter /usr/lib/cups/filter/pstops (PID 23696) for job 5. ... I [19/Oct/2005:10:43:45 -0200] Started filter /usr/lib/cups/filter/foomatic-rip (PID 23697) for job 5. ... I [19/Oct/2005:10:43:45 -0200] Started backend /usr/lib/cups/backend/http (PID 23698) for job 5. ... E [19/Oct/2005:10:43:48 -0200] PID 23698 stopped with status 0! ... D [19/Oct/2005:10:43:48 -0200] StopJob: printer state is 5
This shows that the filters work well but the backend finishes with an error (ignore the misleading status value "0", the crucial information is the leading "E" which indicates that it is actually regarded as an an error) so that the queue becomes disabled ("printer state is 5", for example see "ipp_pstate_t" in /usr/include/cups/ipp.h in the package cups-devel). Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/