Canon PIXMA IP xxxx don't work (Fix expected in 5.0.1)

Bug #34599 reported by Reinhard Duczek
34
Affects Status Importance Assigned to Milestone
Baltix
Invalid
Undecided
Unassigned
cupsys (Ubuntu)
Warty
Invalid
Medium
Unassigned
Hoary
Invalid
Medium
Unassigned
Breezy
Invalid
Medium
Unassigned
gutenprint (Ubuntu)
Fix Released
Medium
Martin Pitt

Bug Description

The Canon IP4200 printer is not supported yet. (added by VETSEL : many PIXMA IP models by CANON have the same problem)

ADDED : NO TURBOPRINT BUGS HERE (for this go to #41386)

Note: the original reporter indicated the bug was in package 'cups'; however, that package was not published in Ubuntu.

Revision history for this message
Lakin Wecker (lakin) wrote :

I'm assigning this to gnome-print in the hopes that someone there can make sure this bug report gets assigned to the appopriate package.

Revision history for this message
Reinhard Duczek (duczek) wrote :

I am still testing and checked the following:

rmmod ehci_hdc
USB 2.0 disabled in BIOS
smp kernel, no smp kernel (processor is an PIV 2.8 GHZ HT)
acpi on/off
ht on/off
changed usb-interface
 i think there is sömeting wrong with udev or maybe a too small buffer in the backend or a synching problem?

Revision history for this message
Reinhard Duczek (duczek) wrote :

@lakin

thank you and feel free to contact me at <email address hidden> for further testing

Revision history for this message
Sebastien Bacher (seb128) wrote :

Reassigning to cups package

What do you mean by "Note: the original reporter indicated the bug was in package 'cups'; however, that package was not published in Ubuntu"? You use that sentence often for component which are available (cups by example). From where do you forward the bug too? If that's from an another bug tracker that could be useful to put a reference to it

Changed in gnome-print:
assignee: gnome → pitti
Revision history for this message
Patrice Vetsel (vetsel-patrice) wrote :

We can not support proprietary software like turboprint.
so i close this bug.
For bugs in turboprint please see http://www.turboprint.info/feedback.html

If you have more important informations (like informations from turboprint that it's our cupsys that is broken) please re-open that bug.
Thank you.

Changed in cupsys:
status: Unconfirmed → Rejected
Revision history for this message
Corey Burger (corey.burger) wrote :

Reopening. Sorry for the confusion. While we do not support the Turboprint driver, we are interested in making this piece of hardware work with Free drivers.

Changed in cupsys:
status: Rejected → Confirmed
Revision history for this message
Reinhard Duczek (duczek) wrote :

No, it is not a problem only wirh Turboprint, the same happens with gutenprint. I tested the driver for the PIXMA4000 (the driver works only in low res and the colors are shifted, but it is the same behavior. The printer starts printing and stops in the middle of the job.

If i could help testing, please let me know. Printing is importend for me...

Revision history for this message
Patrice Vetsel (vetsel-patrice) wrote :

I'm sorry to tell you that I'v exactly the same problem with my : canon ip3000 :(

Revision history for this message
Blake Drager (artifact-alone) wrote :

yup, same problem with turbprint, cups, dapper, and my ip5000.. printing stops in the middle. really frustrating!

Revision history for this message
David Meier (droebbel-melta) wrote :

It seems to work with cups 1.1.23 (built from the sid src).

Revision history for this message
John C Hatch (henwyn) wrote :

The problem is not with the Turboprint driver, which works correctly with the cups 1.1.23 version which currectly loads in Hedgehog. The problem seems to be with either the version of cups and printer management or with the management of usb. Printing start is either delayed or starts and stopspartway through the first page. Extra versions of the same printer are detected and installed. Also an older printer which was removed from this computer before I installed D.D. and hooked up to my son's computer was also detected somehow . . . possibly over the network.

If any information about my installation would help resolve this please let me know and I will try to get it for you.

Revision history for this message
John C Hatch (henwyn) wrote :

The latest installed version of cupsys 1.1.99.b1.r4929.out exhibits the same behavior.

Revision history for this message
Gabriel Lemarié (glemarie) wrote :

Same problem with a Pixma 4000 and cupsys 1.1.99.b1.r4929

Revision history for this message
Giuseppe Noviello (giunov) wrote :

Same problem with Pixma IP4000R and USB connection. I tryed both the PIXMA860 drivers and the PIXMA IP4000 driver, same behavior, it stops after 1 page and half.
I try also to print using the WiFi connection of the printer instead of the USB interface, no problem at all, perfect printing, just a slow down when it reach the same point where it stops with USB connection.
If you need more details let me know.

Revision history for this message
Giuseppe Noviello (giunov) wrote :

I forgot to say that I am running Dapper Flight 6 fully updated.

Changed in cupsys:
status: Unconfirmed → Rejected
status: Unconfirmed → Rejected
Changed in cupsys:
status: Unconfirmed → Rejected
Revision history for this message
dchest (dchest) wrote :

Same problem with PIXMA iP3000 here.
Switched to a different driver (Canon BJC-7004) and it works well.

Revision history for this message
dchest (dchest) wrote :

Sorry, wrong - BJC-7004 worked with the same issue.

description: updated
Revision history for this message
Patrice Vetsel (vetsel-patrice) wrote : Re: Canon PIXMA IP xxxx don't work

I'v made many tests with my IP3000. Test with driver : bjc7000, from japanes canon official ip3100 driver, tests with latest turboprint driver.

With different drivers, each times that the impression stop in the middle i can see in /var/log/cups/error_log a line like :
E [22/Apr/2006:16:14:01 +0200] [Job 8] No %%BoundingBox: comment in header!
or
E [22/Apr/2006:16:05:10 +0200] [Job 7] No %%BoundingBox: comment in header!

Revision history for this message
Christian (linux-ch-baer) wrote :

I have the same problem with IP 3000, tested with bjc3000, gutenprint and turboprint-Driver, connected with USB or SMB.
Some lines from the /var/log/cups/error_log:

E [22/Apr/2006:19:49:53 +02E [22/Apr/2006:19:51:24 +0200] [Job 585] No %%BoundingBox: comment in header!
00] Creating missing directory "/var/run/cups/certs"
E [22/Apr/2006:20:09:39 +0200] CUPS-Add-Modify-Printer: Unauthorized
E [22/Apr/2006:20:09:52 +0200] CUPS-Delete-Printer: Unauthorized
E [22/Apr/2006:20:14:00 +0200] cupsdAuthorize: Local authentication certificate not found!

Revision history for this message
Prinz Igor (pigor) wrote :

Same problem with canon pixma ip3000.

Revision history for this message
Gerry Tool (gerry-thetoolshed) wrote :

For a successful report about using Turboprint 1.94-2 in Dapper with a Canon PIXMA ip-4000, see my comment on bug 41386.

Revision history for this message
GeorgeNorton (george-norton-uk) wrote :

Same poblem with Canon i350.

Revision history for this message
Daniel Koć (kocio) wrote :

The same with Kyocera FS-1010+PostScript driver on networked WinXP station on Dapper beta with current updates:

E [04/May/2006:15:39:53 +0200] [Job 41] No %%BoundingBox: comment in header!
E [04/May/2006:15:39:53 +0200] PID 20299 (/usr/lib/cups/backend/smb) crashed on signal 11!
E [04/May/2006:15:39:55 +0200] PID 20298 (/usr/lib/cups/filter/foomatic-rip) stopped with status 9!

Revision history for this message
Martin Pitt (pitti) wrote :

@Daniel: The crash is most likely bug 39484.

Revision history for this message
Daniel Koć (kocio) wrote :

@Martin: you were right, modified samba packages fromlinux2go did the job, thanks. =}

Revision history for this message
Patrice Vetsel (vetsel-patrice) wrote :

Please everybody update dapper packages. And try to reproduce your bug.
NOTE that in THIS bug we are not talking about bugs with turboprint (for this see #41386)

description: updated
Revision history for this message
Gabriel Lemarié (glemarie) wrote :

I don't know if it was linked to cupsys or turboprint, but I wirks fine for my Pixma 4000 after upgrading to Cupsys1.2 and Turboprint 1.94-3 (released today)www

Thanks.

Revision history for this message
Martin Pitt (pitti) wrote :

thanks for checking. Indeed, the latest turboprint claims to work with cups 1.2.0.

Changed in cupsys:
status: Confirmed → Fix Released
Revision history for this message
Reinhard Duczek (duczek) wrote :

Yes, all systems up and running :-)

Installed Turboprint 1.94-3 and the printer works!!!!

Revision history for this message
chalob (chalob) wrote :

Yes! Finally i can use Ubuntu fully productive! :)

And the oscar goes to: turboprint

...for charging 29bucks for a private license while keeping to pretend that it wasn´t their fault

Danke Jungs!

Revision history for this message
John C Hatch (henwyn) wrote : Re: [Bug 34599] Re: Canon PIXMA IP xxxx don't work

Are you sure the problem was with Turboprint? I thought others were having
problems with other drivers and that the bug seemed to be associated with
the USB drivers, sinse some folks were able to use their printers if they
were connected to a print server rather than directly to their computer.
I'm very glad it got figured out, but I would like to hear eventually what
got figured out.

On 5/18/06, chalob <email address hidden> wrote:
>
> Yes! Finally i can use Ubuntu fully productive! :)
>
> And the oscar goes to: turboprint
>
> ...for charging 29bucks for a private license while keeping to pretend
> that it wasn´t their fault
>
> Danke Jungs!
>
> --
> Canon PIXMA IP xxxx don't work
> https://launchpad.net/bugs/34599
>

Revision history for this message
Patrice Vetsel (vetsel-patrice) wrote : Re: Canon PIXMA IP xxxx don't work

I ask everyone who still have problems to open new bugs.
Because turboprint and cupsys and gnome-cups-manager (and samba) have been greatly updated, many bugs have been resolved.

So if you have still problem please open new bugs, with description, version of package, driver used and how to reproduce bug.

Thank you

Revision history for this message
meshugga (philip-linuxteam) wrote :

i am on latest dapper, canon pixma ip4200 still breaks after a certain data volume. this is NOT exclusively turboprint related, yet i tried it with turboprint and it doesnt work either. normally i use the asian pixma ip4200 drivers. i dont know if it worked with breezy, didnt try, bought the printer a few days ago when i've already been on dapper.

Revision history for this message
meshugga (philip-linuxteam) wrote :

i'm sorry for the comment a few minutes ago - it seems that turboprint works ok, just the asian driver seem to f*ck up :(

Revision history for this message
meshugga (philip-linuxteam) wrote :

i just tried the asian driverpack (2.6.0) with gentoo and cups 1.1.23-r7 and it works like a charm... :/

Revision history for this message
cfraz89 (cfraz89) wrote :

I don't think this is fixed. It's better, and works if i print one page at a time. However, jobs larger than two pages still choke up. Please fix this!!!!

Changed in cupsys:
status: Fix Released → Confirmed
Revision history for this message
Patrice Vetsel (vetsel-patrice) wrote :

cfraz89 :
Please if you want to help, just give us informations, because "Please fix this!!!!" have never helped...

Are you uptodate ?
have you made a clean install ?
what's your printer ?
wich driver do you use ?
provide us steps to reproduce your bug.

Revision history for this message
Prinz Igor (pigor) wrote :

hello,

my system (ubuntu dapper lts) is uptodate. i have a canon pixma ip3000 an using turboprint 1.94-3.

printing with acroread on a4-sized-paper works fine.

printing photos on special paper sizes (4x6 inch borderless) does not work.

i have tested gimp, gnome-photo-printer and digikam. in all cases i get a blank output or just a little band at the "end" of the paper.

under breezy it has worked fine.

i do not know if it is a ubuntu- or turboprint-issue.

if you need any more special info, say it.

regards,

prinz igor

Revision history for this message
cfraz89 (cfraz89) wrote :

Hi.
Sorry about the lack of info.
I am using Dapper, and am keeping it updated. I have a Pixma iP4000, connected through USB.
The problem I get if a print job takes too long (maybe something to do with data thoroughput), say after about 2 pages of printing, the printer quickly slows down to the point where it stops printing. The page stays in, and the light still flashes. This does not happen, however, if i print the document one or two pages at a time. To get printing again, I have to delete the job, turn printer off, and back on.
I use the Gutenprint-5.0-rc2 driver, however this still occurs with the bj*.upp driver as well.
To reproduce the bug, all I have to do is print any moderately-sized document.

Revision history for this message
Marco Cimmino (cimmo) wrote :

Canon driver for ip4000 and ip4200 are out.
http://it.software.canon-europe.com/software/canon_print_filter_for_linuxs24302.asp?model=

I've tried for my ip4200, they install, but if I print the job remains in the queue.
Is it possible to fix it or the bug is in the driver?

best regards

Revision history for this message
rekcor (koos-vanderkolk) wrote :

Same problem here. In my case, the queue is emptied (so it looks like everything works) but the printer doesnt give a sigh.

Revision history for this message
Marco Cimmino (cimmo) wrote :

can be this cups bug related?
http://www.cups.org/str.php?L1738

Revision history for this message
cfraz89 (cfraz89) wrote :

No, I don't believe that is the bug affecting it, as I don't get that message in my error log. But I had a go at installing cups 1.2.1 from source. when i do, i am no longer able to use local printers, for some reason. all other types are ok (in the kde add printer wizard) but local printer is greyed out, and all existing usb printers are rejecting jobs.

Revision history for this message
Adam Pond (adpond) wrote :

Ubuntu - Dapper with updates
Printer - Canon Pixma IP4200
Drivers - Pixma IP4200
Connection - usb://Canon/iP4200
Resolution - 600x600 DPI
Remaining Settings - defaults
(No third party printing packages installed at all)

Summary
    - colour printing seems to be of a very low quality
    - printing images freezes the printer

Description
    - The test page is not clear (I would describe it as scratchy)
    - The test page colours are not as expected. eg, the red line goes from black through browns then oranges then Magenta (not Red, and no, I'm not colour blind).
    - The test page colours (where the magenta colour is showing) is outside of the border.
    - When printing a large image, the printer locks after about 2cm. The print job remains in the queue. The image so far also suffers from the same "scratchy" texture.
    - The print queue reports that the print job was 18.2Mb when the file was only 1.8Mb. (I just mention this in case this helps diagnose the problem, not that I think we should be too worried about it).

I hope this helps in reclarifying what we are working towards here. After reading through the comments, it seems some people are having problems with third party tools (turboprint) as well, but that is not within the scope of this bug.

I agree with Corey Burger that we really should try to have printers working natively un ubuntu without requiring users to go and buy third party drivers.

VETSEL Patrice, do you still think that we should be creating new bug reports for this issue ?

Revision history for this message
Marco Cimmino (cimmo) wrote :

Adam I have no Pixma IP4200 driver, only ip4000 by cupsys, where do you find it? They were canon's drivers?

Revision history for this message
Marco Cimmino (cimmo) wrote :

tried cupsys 1.2.2 and canon ip4200 driver 2.60 printing jobs now disappears, no printing at all yet.
Someone can look into the code and/or contact canon?

Revision history for this message
Michael (michaeljt) wrote :

I have submitted code to Gutenprint to add a driver for the iP4200. It is currently only available from their CVS, but should go into 5.0.1 if there are no problems. I would be grateful to anyone willing to give it a try (it worked in my minimal tests).

Revision history for this message
Marco Cimmino (cimmo) wrote :

can be backported the patch related to ip4200 waiting for 5.0.1? If not we will have another ubuntu without ip4200 support and have to wait an update from ubuntu after the release....

Revision history for this message
Marco Cimmino (cimmo) wrote :

anyway now there are these packages that works great in Edgy with ip4200!
http://mambo.kuhp.kyoto-u.ac.jp/~takushi/

Revision history for this message
IbeeX (ibrkanac) wrote :

Latest gutenprint from CVS is working fine (ip4200)

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Please try the new Gutenprint packages on

http://www.linux-foundation.org/~till/tmp/ubuntu/feisty/gutenprint/binary/

They are on the way into Feisty,

Changed in gutenprint:
status: Confirmed → Fix Committed
Changed in gutenprint:
status: Fix Committed → Fix Released
Revision history for this message
Marco Cimmino (cimmo) wrote :

please backport to Edgy

Revision history for this message
IbeeX (ibrkanac) wrote :

I can confirm that ip4200 is working in fiesty :)

Revision history for this message
Marco Cimmino (cimmo) wrote :

ok confirmed here with Feisty, however to install the printer under kubuntu must go to localhost:631 in a browser because in kde print manager canon ip4200 (and all others from gutenprint driver) wasn't present.

Revision history for this message
Pascal De Vuyst (pascal-devuyst) wrote :

@Cimmo
> because in kde print manager canon ip4200 (and all others from gutenprint driver) wasn't present
This bug has already been reported as bug #99372, please add further information about this issue in that bug report.

Revision history for this message
Marco Cimmino (cimmo) wrote :

thanx pascal, searched it but cannot found, now I put other informations.

Przemek K. (azrael)
Changed in baltix:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.