Red Hat Bugzilla – Bug 216023
Windows Network printer has to be power-cycled between print jobs
Last modified: 2007-11-30 17:11:49 EST
Description of problem:
CUPS set up to print to Canon BJC3000 on Windows ME PC on the local LAN. Printer
has to be power-cycled between print jobs or the job never gets printed, even
though it's shown as "submitted" to the printer. Windows side shows job
submitted to the printer, but printer doesn't print unless power-cycled. Will
even hang Windows print jobs if not power-cycled.
Using "foomatic/gimp-print-ijs" as driver.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Install Canon BJC3000 on Windows ME PC
2.Configure CUPS to print to shared Windows printer
3.Send multiple print jobs to shared windows printer
First job goes through fine, Subsequent jobs hang until printer is power-cycled.
All jobs should go through without having to power-cycle the printer.
Firstly I'd like to try to eliminate foomatic. To do this, we'll need to switch
to the native CUPS gimp-print drivers. Install the 'gimp-print-cups' package,
and then use system-config-printer (System->Administration->Printing). Click on
the queue you are using and then click the 'Change' button to the right of 'Make
The manufacturer should be correct so click Forward, and then you should see
'BJC-3000' already selected. Confusingly, the gimp-print-cups drivers for it
are listed under 'BJC 3000' (earlier in the list), so select that for the model
and then select 'C/bjc-3000.ppd.gz' for the driver.
Then click forward, select 'try to copy the option settings', and then click apply.
Now, does the modified queue show the same behaviour?
Unfortunately, I don't *have* an option for "bjc3000." I will try with
"foomatic: BJC-3000-bjc600.ppd" which is the only other option for driver. I did
search for "bjc-3000.ppd" and "bjc-3000.ppd.gz" on my system, but could not find
them. Can you advise where they should be?
Ok. Looks like it just didn't like that printer driver. I just re-read your
message and see that I overlooked the instruction to
"gimp-print-cups" package. Even though the new driver works, I'll try the
gimp-print-cups package and see if that fixes it. In any event, I would
recommend marking this as "closed." Thanks for your help.
FWIW, installing "gimp-print-cups" results in a NEW manufacturer entry "CANON"
(all upper-case" and THAT is where the new drivers are found. I'm going to try
that and see if I can get better quality printing. Thanks for the help!
Okay, sorry about that. I didn't spot that because I'm using a test version of
system-config-printer that merges upper- and lower-case manufacturers when they
are different.. :-/
I'd be very interested to know if the gimp-print-cups driver gives the same
symptom, because it will mean that we'll know if the problem comes from foomatic
or from gimp-print.