Problems with color printing on Laserjet 2600n

Bug #90250 reported by Shawn McMahon
2
Affects Status Importance Assigned to Milestone
ghostscript (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: cupsys

Color printing to the HP Color Laserjet 2600n in Edgy has two problems:

1) By default color printing is not enabled, and cannot be enabled through the GUI. A file must be edited; see:

https://wiki.ubuntu.com/HardwareSupportComponentsPrintersHp
http://www.ubuntuforums.org/showpost.php?p=1949451&postcount=9

2) Once color printing is enabled, the color is way off from what Windows will produce with the same picture.

I've tried the default "Default ICM color correction", the "File hpclj2600n-0.icm", and "No ICM color correction". All produce the same results on a test page, which is that the "blue" scale appears to be shades of a dark purple. The other colors look, to my untrained eye, to be OK.

If necessary I'll be glad to snail-mail you a test page.

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

The problem of needing to add the "-c" in the PPD file is an upstream bug. I will report it to the author of the foo2hp driver (part of the foo2zjs package).

The problems with color accuracy can be cause by GhostScript. Try to install the gs-gpl package and then run

sudo update-alternatives --config gs

and choose "gs-gpl". Are the colors better now?

Changed in cupsys:
importance: Undecided → Medium
status: Unconfirmed → Needs Info
Revision history for this message
Shawn McMahon (smcmahon) wrote : Re: [Bug 90250] Re: Problems with color printing on Laserjet 2600n

Yeah; the quality still sucks, but the colors are a lot better.

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

You do not need to edit the PPD file to change the color mode. You only need to change the default setting of the "Color Mode" option. To do so, right-click the printer icon in the gnome-cups-manager and choose "Properties". On the "Advanced" tab you can set "Color Mode" to "Color". To get a better output quality try also to set "Bits per Plane" to "2 Bits per Plane".

If these changes have no effect, call the CUPS web interface via http://localhost:631/, click the "Printers" tab and click "Set printer options" at the entry for your printer. Set the above-mentioned options there and try again.

Does it work now?

Revision history for this message
Shawn McMahon (smcmahon) wrote :

On Wed, Mar 07, 2007 at 12:41:12PM -0000, Till Kamppeter said:
> You do not need to edit the PPD file to change the color mode. You only
> need to change the default setting of the "Color Mode" option. To do so,
> right-click the printer icon in the gnome-cups-manager and choose
> "Properties". On the "Advanced" tab you can set "Color Mode" to "Color".
> To get a better output quality try also to set "Bits per Plane" to "2
> Bits per Plane".
>
> If these changes have no effect, call the CUPS web interface via
> http://localhost:631/, click the "Printers" tab and click "Set printer
> options" at the entry for your printer. Set the above-mentioned options
> there and try again.
>
> Does it work now?

Yeah, on three different boxes doing it via "gnome-cups-manager" didn't
work; I never tried the web interface though. I'll try changing the
file back and using that to fix it when I get home. Note that the
forums contain reports from other people that it doesn't work, and lots
of non-Ubuntu forums talk about it too, always with either editing the
file or not using Ubuntu's foo packages at all as the solution. See the
links I provided.

Also tried setting Bits per Plane to 2, and that just causes printing to
silently fail. Setting it back causes printing to begin working again.
I was going to file that as seperate bug this weekend.

--
   Shawn McMahon |
   EIV Consulting | Peace is a symptom of victory.
 http://www.eiv.com |

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

The author of foo2zjs tells that this is a problem of GhostScript and you should use the newest version.

Download the files from

http://www.linux-foundation.org/~till/tmp/ubuntu/gutsy/ghostscript/

into the same directory. Then do

sudo apt-get install build-essential fakeroot
sudo apt-get build-dep gs-esp gs-gpl
dpkg-source -x ghostscript_8.60.dfsg.2-0ubuntu1.dsc
cd ghostscript-8.60.dfsg.1
dpkg-buildpackage -rfakeroot
cd ..
sudo dpkg -i *gs-esp*.deb *gs-afpl*.deb *gs-gpl*.deb *libgs*.deb *ghostscript*.deb

and you will have the latest Ghostscript.

Answer every question which appears with "y", so that all needed packages get installed.

Please tell us your results with the test packages.

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

Bug 106003 is a similar problem and can be a duplicate of this one.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ghostscript (Ubuntu) because there has been no activity for 60 days.]

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.