Custom Query (29 matches)

I am trying to get a Canon MP620 to print properly. I am using CUPS 1.48, Ghostscript 8.71 or 9.04, Gutenprint 5.2.7.1, and cups-bjnp-1.0-os2-20120518.zip. The printer seems to print okay when I do a simple text print, and with the test print.

I created a simple PDF file from Firefox 1.0.0.4 (FFtoPDF.PDF), then tried to print it from Lucide 1.3.4 GA. It seems that I get errors from Ghostscript 8.71, and the print job status is "stopped". See error_log for a debug log file.

If I use Ghostscript 9.04, it will print, but it is gray scale, with no color.

Not sure if this is a bug or configuration issue...

I have a printer attached to a CUPS 1.4.8 server (HP DeskJet? 990C with HPLIP) on eCS 2.1 that works well. I can print from remote eCS clients to the server using a CUPS output port on the printer object.

Now I need to have CUPS installed locally on the clients (for QT and Java apps). I need to be able to print to the local CUPS and have that sent to the CUPS running on the server with the printer. I have tried setting up the CUPS printer on the clients using the ipp:// backend, but trying to print the test page just hangs 'processing page 1' forever, and no print job gets to the server. Trying the ​http:// backend always results in 'http backend failed' messages.

I also tried using Alex Taylors 'CupsWiz?' program (in eCS 2.2 beta) on a client to install the printer, and after selecting my printer from the list offered, the program hangs 'Looking for connected printers. Please wait...'. Then a VX-REXX window appears that says: 'Password for unknown on 192.168.0.2?' (the CUPS server with the printer). There is no password (that I know of) so this is a bit baffling. CUPSWIZ is hung and must be killed.

I have a problem when printing to my Canon i960 printer. I do a simple print from E.EXE (AE.EXE), the page prints, and appears to finish. However, one of four processors (bouncing around) stays at 99.9%, until I kill USB.EXE.

I will add error_log, which shows a crash in USB.EXE, but I am pretty sure that happened when I killed USB.EXE.

11-04-12 1:26a 25,468 0 a--- usb.exe

Anything else that you need?

Thanks...