Wrong foomatic driver for Canon ip4300 in database

Bug #368224 reported by Paul Castle
2
Affects Status Importance Assigned to Milestone
Gutenprint
New
Unknown
gutenprint (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Binary package hint: foomatic-db-gutenprint

THE PROBLEM
Using the ip4300 driver from the database the colours on the ip4300 are very wrong (see launchpad question 68838).
WORKAROUND (and possible solution)
Selecting the ip5200 appears to give the correct colours if used for the ip4300. Can the database simply be updated to use the same driver for the ip4300 as is currently used for the ip5200.

I would be most happy to test any changes if required.

Further testing confirms that the IP4300 Driver CAN work correclty, but the user needs to go to the Printer Options, and change the COLOURS from RGB to CYMK. It strikes me that CYMK should be the default, since using this gives the correct colours for normal use.

(Using Intrepid Ibex)

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

Still a problem with the newer distribution-independent gutenprint 5.2.2 driver package from openprinting.org in Ubuntu 8.10 (Intrepid) or with the newer gutenprint 5.2.3 in Ubuntu 9.04 (Jaunty)?

Changed in gutenprint (Ubuntu):
assignee: nobody → Pascal De Vuyst (pascal-devuyst)
status: New → Incomplete
Changed in gutenprint (Ubuntu):
assignee: Pascal De Vuyst (pascal-devuyst) → nobody
Revision history for this message
Pascal De Vuyst (pascal-devuyst) wrote :

Thank you for reporting this bug to Ubuntu. Intrepid reached EOL on April 30, 2010.
Please see this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases.
Is this still a problem with Ubuntu 10.10? Risk-free testing without installation is possible with the live cd.

Changed in gutenprint:
status: Unknown → New
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.