Canon iP4000 does not print in Feisty

[walders]

Hi,

I have been searching various forums, and can only find one other person with this bug (http://ubuntuforums.org/showthread.php?p=2567118).

My Canon Pixma iP4000 was working fine out of the box with Edgy. It was listed in the printer list and installed perfectly (locally and through my router).

It broke when I upgraded to Feisty. It is not listed in the printer list. I downloaded the Gutenprint driver (as recommended on http://www.linuxprinting.org/show_printer.cgi?recnum=Canon-PIXMA_iP4000). The ppd apparently installs OK. WHen I print (either locally or through my router), the job stops with an error. The ipp report states the reason for the stop/error as "job-stopped".

The above was all done in Kubuntu; I also tried to do the same in Ubuntu, but with no success either.

[Brian Murray (brian-murray)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. To better help us troubleshoot your issue could you follow the procedure at https://wiki.ubuntu.com/DebuggingPrintingProblems and add any information you find out. Thanks in advance.

[walders (launchpad-walders)]

First set of info...the output of the USB detection (note that I normally print to this as a network printer attached to my router, but for these purposes have connected via USB)

walding@walders-laptop:~$ lsmod | grep usb
usblp 14848 0
usbcore 134280 4 usblp,ehci_hcd,uhci_hcd
walding@walders-laptop:~$ tail -f /var/log/messages
May 1 21:03:05 walders-laptop gconfd (root-7020): Exiting
May 1 21:13:42 walders-laptop -- MARK --
May 1 21:33:44 walders-laptop -- MARK --
May 1 21:34:27 walders-laptop kernel: [ 2532.812000] usb 1-1: new full speed USB device using uhci_hcd and address 2
May 1 21:34:27 walders-laptop kernel: [ 2533.044000] usb 1-1: configuration #1 chosen from 1 choice
May 1 21:34:28 walders-laptop kernel: [ 2533.208000] drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 2 if 0 alt 0 proto 2 vid 0x04A9 pid 0x1093
May 1 21:34:28 walders-laptop kernel: [ 2533.208000] usbcore: registered new interface driver usblp
May 1 21:34:28 walders-laptop kernel: [ 2533.208000] drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
May 1 21:34:53 walders-laptop kernel: [ 2558.280000] usb 1-1: USB disconnect, address 2
May 1 21:34:53 walders-laptop kernel: [ 2558.280000] drivers/usb/class/usblp.c: usblp0: removed
May 1 21:35:20 walders-laptop kernel: [ 2585.560000] usb 1-1: new full speed USB device using uhci_hcd and address 3
May 1 21:35:20 walders-laptop kernel: [ 2585.736000] usb 1-1: configuration #1 chosen from 1 choice
May 1 21:35:20 walders-laptop kernel: [ 2585.744000] drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 3 if 0 alt 0 proto 2 vid 0x04A9 pid 0x1093

walding@walders-laptop:~$ lpinfo -v
network socket
network beh
network bluetooth
direct usb://Canon/iP4000
direct hpfax
direct hp
network http
network ipp
network lpd
direct parallel:/dev/lp0
direct scsi
network smb

[walders (launchpad-walders)]

Error log after trying to print attached.

[Pascal De Vuyst (pascal-devuyst)]

Thanks for your bug report.

Your cups error log show the following:
D [01/May/2007:21:42:27 +0100] [Job 23] /opt/gutenprint/cups/lib/filter/rastertogutenprint.5.0: No such file or directory
E [01/May/2007:21:42:27 +0100] PID 9945 (/opt/gutenprint/cups/lib/filter/rastertogutenprint.5.0) stopped with status 22!

This looks like a duplicate of bug #111038.

Did you install the distribution-independent gutenprint 5.0.0.99.1-3 package in Edgy and then do a dist-upgrade to Feisty?
Did you do any manual changed on your /opt directory? If it is a separate partition, is this partition mounted? Or did you delete files in /opt?
In general you will not need this LSB package, as it is the same upstream version as the Gutenprint coming with Feisty (5.0.0.99.1) and may cause the problem. If you want to return to the Feisty package, do

sudo dpkg -e gutenprint
sudo apt-get install cupsys-driver-gutenprint

and re-create your print queue.

[walders (launchpad-walders)]

>Did you install the distribution-independent gutenprint 5.0.0.99.1-3 package in Edgy and then do a dist-upgrade to Feisty?
No, I installed the printer in Edgy from the list. I then upgraded to Feisty, but the printer was not listed. So I Googled and found the gutenprint driver.

>Did you do any manual changed on your /opt directory?
Only installed Project-X software. Nothing else. I think the printer problems happened before that.

> If it is a separate partition, is this partition mounted?
No - it's in the same partition as /root. /home is a separate (mounted) partition

> Or did you delete files in /opt?
No

[walders (launchpad-walders)]

I tried the commands you suggested. Output below:

walding@walders-laptop:~/Desktop$ sudo dpkg -e gutenprint
Password:
dpkg-deb: failed to read archive `gutenprint': No such file or directory
walding@walders-laptop:~/Desktop$ sudo apt-get install cupsys-driver-gutenprint
Reading package lists... Done
Building dependency tree
Reading state information... Done
cupsys-driver-gutenprint is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

[Pascal De Vuyst (pascal-devuyst)]

The right commands are:

$ sudo dpkg --purge --force-all gutenprint
$ sudo dpkg --purge --force-all cupsys-driver-gutenprint

followed by a:

$ sudo apt-get install cupsys-driver-gutenprint

[Pascal De Vuyst (pascal-devuyst)]

BEFORE running the above commands can you give the output of the following command:
$ ls -l /usr/lib/cups/driver/

[walders (launchpad-walders)]

walding@walders-laptop:~$ ls -l /usr/lib/cups/driver/
total 36
lrwxrwxrwx 1 root root 29 2007-04-22 20:42 foomatic -> ../../../bin/foomatic-ppdfile
-rwxr-xr-x 1 root root 33272 2007-03-27 11:44 gutenprint.5.0

[Pascal De Vuyst (pascal-devuyst)]

Running the following command should return the gutenprint drivers for your Canon Pixma iP4000 printer:
$ /usr/lib/cups/driver/gutenprint.5.0 list | grep iP4000
"gutenprint.5.0://bjc-iP4000/expert/C" en "Canon" "Canon PIXMA iP4000 - CUPS+Gutenprint v5.0.0.99.1" ""
"gutenprint.5.0://bjc-iP4000/simple/C" en "Canon" "Canon PIXMA iP4000 - CUPS+Gutenprint v5.0.0.99.1 Simplified" ""

And running this command should output the PPD file:
$ /usr/lib/cups/driver/gutenprint.5.0 cat 'gutenprint.5.0://bjc-iP4000/simple/C'

Run this command to find out the drivers for your Canon Pixma iP4000 known to CUPS (may take a while):
$ lpinfo -m | grep iP4000
gutenprint.5.0://bjc-iP4000/expert/C Canon PIXMA iP4000 - CUPS+Gutenprint v5.0.0.99.1
gutenprint.5.0://bjc-iP4000/simple/C Canon PIXMA iP4000 - CUPS+Gutenprint v5.0.0.99.1 Simplified

Output shown is from my feisty system, what is the output of the above commands on your system?

[walders (launchpad-walders)]

My output is *identical* to yours.

[walders (launchpad-walders)]

OK....

In Gnome, the printer is listed (well, as 4200), but nothing prints.
In Kubuntu, the printer is found on scanning, but the driver is not listed. All the same, it doesn't print anything.

[Till Kamppeter (till-kamppeter)]

So it seems that there are two problems:

1. The KDE Printing Manager does not list the PPDs of Gutenprint 5.0.0.99.1 neither the auto-generated ones of Feisty's Gutenprint package nor the static (ready-made) ones of the distribution-independent LSB Gutenprint 5.0.0.99.1 package from OpenPrinting. This meaans there must be a bug in the KDE Printing Manager. This problem is already reported in bug #99372. Please continue discussing it there.

2. The Canon iP 4000 does not print with Gutenprint 5.0.0.99.1 under Feisty when set up with the GNOME CUPS Manager and using the Gutenprint package coming with Feisty (Walders had the same driver listing output as Pascal in the end). Please continue discussing this problem in this bug report.

Walders, have you removed and recreated your print queue(s) after uninstalling the OpenPrinting package and installing the Feisty package of Gutenprint?

Have you taken care that your print queue is enabled? Check with "lpstat -p", enable with the "sudo cupsenable <queue name>" command.

Otherwise post your printingbuginfo and error_log again.

[walders (launchpad-walders)]

Hi,

Thanks for that summary.

Regarding the printing queue, excuse my ignorance...I removed the printer and added it again.
The print queue is enabled, using the command you've given.

Do you still want the printingbuginfo and error_log?

[Till Kamppeter (till-kamppeter)]

I only need it if you are not able to print.

If you are able to print now, I will close this bug report.

[walders (launchpad-walders)]

I'm still not able to print.

[Till Kamppeter (till-kamppeter)]

Your error_log does not contain anything about a print job (lines with "[Job xx]", where xx is a number). Please try to print something and immediately after that get your error_log.

[walders (launchpad-walders)]

I had 2 jobs in the queue...I have cancelled them and tried again.
The job gets stuck in job-printing, so that's a different problem to yesterday.

[Till Kamppeter (till-kamppeter)]

It seems that your error_log files are both exactly the same. Can you do the following commands:

sudo /etc/init.d/cupsys stop
sudo rm -f /var/log/cups/*
sudo rm -f /var/spool/cups/*
sudo rm -f /var/spool/cups/tmp/*
sudo /etc/init.d/cupsys start

Now print a small job and do repeatedly

lpstat -o

A soon as the job disappears do

sudo cp /var/log/cups/error_log /tmp

If the job stays in the queue for mor than a minute, do

sudo cp /var/log/cups/error_log /tmp

anyway.

Attach /tmp/error_log to this bug report.

Do also

cat /tmp/error_log | grep -i 'job' > /tmp/error_log2

and attach /tmp/error_log2 to this bug report.

[walders (launchpad-walders)]

It stays for more than a minute. In fact, the previous job was still there from 120 minutes ago. I deleted that one.
I can't upload the error_log file from /tmp/ as I get an error that it cannot upload empty file.

[walders (launchpad-walders)]

chown helped there...

[Pascal De Vuyst (pascal-devuyst)]

Thanks Till for pointing us to the KDE Print Manager bug.

>In Gnome, the printer is listed (well, as 4200), but nothing prints.

You should be able to set up your printer in gnome-cups-manager (System -> Administration -> Printing) using the iP4000 driver instead of the iP4200 driver, gnome-cups-manager lists the same drivers as the output of the command 'lpinfo -m", since you have the same output you should be able to select the iP4000 driver in gnome-cups-manager.

If this does not work you can always use CUPS web interface by typing http://localhost:631/ in your web browser to set up your printer using the iP4000 driver, this should work in both KDE and GNOME.

Please attach you cups error_log again if you are still unable to print with the iP4000 driver.

[walders (launchpad-walders)]

Thanks. I can now get it to work in Gnome as you have said. It only works directly attached. I'll have another go with it as a network printer another day.
I guess this part of the issue can be closed.

[Omk (ossi-viljakainen)]

I am having the same problem with Canon LBP 4U printer. The error was occurring with cjet (recommended) driver. With the instructions given here, Itried lbp8 driver and it worked. I have been using the printer (auto-edtected) with cjet driver without any problems in dapper. Now having a fresh install of Feisty and I was not able to print until found these tips from here.

[Pascal De Vuyst (pascal-devuyst)]

@Arjuna
You have a completely different issue.

> The error was occurring with cjet (recommended) driver.
> I have been using the printer (auto-edtected) with cjet driver without any problems in dapper.

The cjet driver is and has never been installed out of the box on Ubuntu: this is the case for Feisty, Edgy and Dapper. Either Dapper recommends a different driver for your printer or you manually installed the cjet package in Dapper to make it work.

The real issue is that CUPS lists the cjet driver as recommended while the binary driver package is not installed:
$ lpinfo -m | grep -i "LBP-4U"
foomatic:Canon-LBP-4U-cjet.ppd Canon LBP-4U Foomatic/cjet (recommended)
foomatic:Canon-LBP-4U-lbp8.ppd Canon LBP-4U Foomatic/lbp8

This is a known issue and has already been reported into our bug tracking system as bug #59324. Please do not add further unrelated comments in this bug. If you have any additional information you should add this in bug #59324.

>Now having a fresh install of Feisty and I was not able to print
Installing the cjet package from synaptic or a command line should work:
$ sudo apt-get install cjet

[Pascal De Vuyst (pascal-devuyst)]

> Thanks. I can now get it to work in Gnome as you have said. It only works directly attached.
> I'll have another go with it as a network printer another day.
> I guess this part of the issue can be closed.

Closing this bug as a duplicate of bug #99372 then for the remaining issue.
Feel free to open a new bug report if you can't set up your printer as a network printer.