Bug 579307 - hplips-3.10.2 thinks that 'low ink' is a reason to not print
Summary: hplips-3.10.2 thinks that 'low ink' is a reason to not print
Keywords:
Status: CLOSED DUPLICATE of bug 579355
Alias: None
Product: Fedora
Classification: Fedora
Component: hplip
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-04 02:33 UTC by Don Lindsay
Modified: 2010-04-07 14:39 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-04-07 14:39:23 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Don Lindsay 2010-04-04 02:33:31 UTC
Description of problem: hplips-3.10.2 thinks that 'low ink' is a reason to not print.


Version-Release number of selected component (if applicable):


How reproducible: Print to an HP Officejet J5780 printer with an Office Max refilled ink cartridge, which always incorrectly reports 'low ink'.

  
Actual results: print jobs pile up in print queue and nothing is printed.


Expected results: Jobs in print queue are printed.


Additional info: this property was noticed immediately after an upgrade came through from hplip-3.9.8 to hplip-3.10.2. I did a "yum downgrade hplip hplip-common hplip-libs hpijs", restarted the CPUS daemon via the system\administration\services GUI, and print jobs now print fine.

Comment 1 Don Lindsay 2010-04-04 02:35:51 UTC
erk, restarted the CUPS daemon. Sorry.

Comment 2 Rob Wills 2010-04-04 19:14:10 UTC
I now have the same problem after applying the latest hplip package updates. You said that restarting CUPS solves the problem; how do I go about doing this?

Thanks!

Comment 3 Rob Wills 2010-04-04 19:30:17 UTC
Restarted CUPS, but still unable to print files due to "low ink" Any suggestions?
The printing troubleshooter compiled a crash report, I can post that if it'll be useful.

Comment 4 Tim Waugh 2010-04-07 14:39:23 UTC

*** This bug has been marked as a duplicate of bug 579355 ***


Note You need to log in before you can comment on or make changes to this bug.