registry team mailing list archive

[Bill Trimmer <235399@xxxxxxxxxxxxxxxxxx>]

Hi, David;

I'm not Till, the guy who did the the hplip update. I have talked with him. he wrote hplip 3.10.6 to go into cups 1.4.4-6ubuntu2 in Meerkat. I looked around and found hplip 3.10.6 separately, without any documentation for dependencies. Since development notes indicated that 3.10.6 had been written to go into cups with Meerkat I decided to wait the few remaining days until Meerkat was released. Hplip 3.10.6 is downloadable through Package Manager, and I imagine that now Meerkat has been released there will be a return to Lynx updates, although I don't know how frequently, so it shouldn't be too long until the cups update arrives. In the meantime you can set the Printer/Properties/Device in any application you use to print to grayscale and in the Printer/Options remember to check on the Print Black box. You have to check the Print Black box for each job, because the printer settings don't hold. Once you have hplip 3.10.6 you can check the printer driver
 directly and pick one of the two cartridge options. You can pick the grayscale option in your current HP printer driver, too, but it does stop you from using color with some printers.

Hope that helps. Rather than juggle packages, I installed Meerkat,
partly from laziness, partly because I love being a beta tester, and now
I'm waiting for the Meerkat team to give me back some control. I
deliberately killed Unity the other night and spent an hour running
xwindows in recovery just to see what I could do with Meerkat in basic
GNOME. I ran a print job out of Open Office using an HP 3500 with an
empty color cartridge I want to replace next weekend. Everything looks
fine.

Bill Trimmer

--- On Thu, 10/14/10, David Rahrer <235399@xxxxxxxxxxxxxxxxxx> wrote:

From: David Rahrer <235399@xxxxxxxxxxxxxxxxxx>
Subject: [Bug 235399] Re: "Print black" does not use black ink cartridge
To: liam_668@xxxxxxxxx
Date: Thursday, October 14, 2010, 2:49 PM

Excellent work, Till, thank you for picking up HP's slack.  I was just
about to dump our printers for another brand.  I'm having some trouble
patching and building this to incorporate your fix.  Before I screw it
up further, is there now a patched, compiled version for Lucid
somewhere?  Since Lucid is a LTS release, I would think a backport or
update would be in order, or perhaps someone has a PPA available even.
Whatever it takes to get this issue cleared up quickly now that you have
fixed it!

Thanks again for your work on this.

-- 
"Print black" does not use black ink cartridge
https://bugs.launchpad.net/bugs/235399
You received this bug notification because you are a direct subscriber
of a duplicate bug (652307).

Status in HP Linux Imaging and Printing: Confirmed
Status in “hplip” package in Ubuntu: Fix Released
Status in “hplip” package in Debian: Confirmed

Bug description:
Binary package hint: openoffice.org

If I want to save money and print black text with black ink, I have to
select the "greyscale" printout mode. Of course, when I do that, my
images also come out black & white. There are evidently workarounds, or
I can run the pages through twice and hope the alignment is perfect, but
I don't think that should be necessary.

I'm running Kubuntu Hardy (8.04) with linux kernel 2.6.24-17-generic.

The version of OpenOffice.org is 1:2.4.0-3ubuntu6.

My printer is an HP Officejet 5610 All-in-One, which is a USB printer.

I thank you in advance for everything you do.

ProblemType: Bug
Architecture: i386
Date: Tue May 27 22:04:32 2008
DistroRelease: Ubuntu 8.04
NonfreeKernelModules: ath_hal
Package: openoffice.org-core 1:2.4.0-3ubuntu6
PackageArchitecture: i386
ProcEnviron:
 PATH=/usr/lib/openoffice/program:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: openoffice.org
Uname: Linux 2.6.24-17-generic i686

To unsubscribe from this bug, go to:
https://bugs.launchpad.net/hplip/+bug/235399/+subscribe

-- 
"Print black" does not use black ink cartridge
https://bugs.launchpad.net/bugs/235399
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Debian.