Canon IP4000 prints badly in Gutsy

[Jonah]

Hi I have Gutsy AMD64 which autodetected my Canon ip4000 printer, which i was pleased about as previously i've had to use Turboprint. Anyway i tried printing photos from gimp, pdf viewer, photo viewer, openoffice and a few other apps and couldn't get one to give me a print out of a decent photo quality. They all looked dotty and awful. The original photos are fine and all settings were set for high quality...

[Mario Young (mayeco)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at [WWW] https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in cupsys.

[Jonah (jonah)]

i've installed turboprint also, so now i have the turboprint ppd driver and the detected one in feisty, neither work very well but turboprint behaves a little better.

the normal driver with ubuntu not only prints badly and sometimes in the wrong place but also the paper settings don't match the canon paper settings that the printer should have. it has entries for 3 cds, but the canon ip4000 has a cd printing plate that is a set size, so you can't print any discs with these option the ubuntu driver is giving. the turboprint driver offer cd recommended and cd other, both the set size to print in the right place. the ubuntu driver doesn't give either of these options and instead gives sizes for the cd which are then in the wrong place for printing...

it's a print nightmare, i've had to instead use my mac to print from, which also detects the ip4000 itself without a proprietary driver from canon (they don't provide one for mac), yet cups on the mac is fine and prints great and has the right paper types etc...

can someone please fix this up thanks so much

[Daniel T Chen (crimsun)]

Is this symptom still reproducible in 8.10?

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.