HP 5610 Checking ink levels fails

Bug #519971 reported by Esther
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cups (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: cups

system-config-printer 1.1.12
HP Officejet 5610 All-in-One
Ubuntu 9.10 Karmic Koala

I knew my ink levels were low, but not certain. I launched the printer properties box, navigated to the ink/toner levels window. The window reports that marker levels are not reported for this printer and no status messages. Hitting the refresh button returns a CUPS error message, "CUPS server error: There was an error during the CUPS operation: 'client-error-document-format-not-supported'."

I would have expected the ink levels to be reported when hitting the refresh button. But before that, I would have expected the ink levels to already be reported when opening the configuration property window.

ProblemType: Bug
Architecture: i386
CheckboxSubmission: fd057b0bdea60eb17cdbf0a26f3fba5f
CheckboxSystem: 0531969bcfd4f03af7405c98dc94a948
CupsErrorLog: E [10/Feb/2010:09:49:36 -0700] Returning IPP client-error-document-format-not-supported for Print-Job (ipp://localhost/printers/Officejet_5600_series) from localhost
Date: Wed Feb 10 10:23:19 2010
DistroRelease: Ubuntu 9.10
Lpstat:
 device for Officejet_5600_series: hpfax:/usb/Officejet_5600_series?serial=CN5CRDF7M804CY
 device for Officejet_5600_series_fax: hpfax:/usb/Officejet_5600_series?serial=CN5CRDF7M804CY
Lsusb:
 Bus 003 Device 002: ID 03f0:4f11 Hewlett-Packard OfficeJet 5600 (USBHUB)
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: To Be Filled By O.E.M. MS-7145
Package: cups 1.4.1-5ubuntu2.1
Papersize: letter
PpdFiles:
 Officejet_5600_series: HP Officejet 5600 Series hpijs, 3.9.8
 Officejet_5600_series_fax: HP Fax hpijs
ProcCmdLine: root=UUID=f86bcd21-a135-45c3-a637-a151c5920915 ro quiet splash
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
SourcePackage: cups
Uname: Linux 2.6.31-19-generic i686
XsessionErrors:
 (gnome-settings-daemon:1683): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:1775): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:1780): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-panel:1774): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -1 and height 27
dmi.bios.date: 06/07/2005
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080012
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: MS-7145
dmi.board.vendor: MSI
dmi.board.version: 200
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080012:bd06/07/2005:svnToBeFilledByO.E.M.:pnMS-7145:pvr0A:rvnMSI:rnMS-7145:rvr200:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: MS-7145
dmi.product.version: 0A
dmi.sys.vendor: To Be Filled By O.E.M.

Revision history for this message
Esther (melanes) wrote :
Revision history for this message
David Rahrer (david-rahrer) wrote :

I have the same issue on Lucid using the same printer as OP. The only difference between Karmic and Lucid, is that after refresh on Lucid there is no error, but a message about submitting a maintenance job number x. Executing "hp-levels" in terminal gives me the correct levels, so it would seem there should be a way for it to work in the printer gui as described.

Revision history for this message
gf (gf-interlinks-deactivatedaccount) wrote :

Hello Esther,
Thank you for submitting this bug and reporting a problem with cups and printing. You made this bug report some time ago and Ubuntu has been updated since then.

Could you confirm that this is no longer a problem and that we can close the ticket?
If it is still a problem, are you still interested in finding a solution to this bug?
If you are, could you let us know, and in the current version, run the following (only once):
apport-collect BUGNUMBER
and upload the updated logs and and any other logs that are relevant for this particular issue.

Thank you again for helping make Ubuntu better.
G

Changed in cups (Ubuntu):
status: New → Incomplete
Revision history for this message
Esther (melanes) wrote :

I no longer have this printer, so I will be unable to test to see if the bug has been fixed with this printer.

I currently have an HP 6700. Checking the ink levels for the printer properties returns, "Marker levels are not reported for this printer." I don't know if this is a CUPS problem or is just simply not a supported feature for this printer. If ink levels are supposed to be available for this and similar HP printers through the desktop printer properties, then a communication error still exists. Otherwise, ink levels are reported directly through the printer's screen interface. This was, of course, not a previously available feature for the prior printer. As the information is available through other means, it is not critical it be available through the printer properties. It would be nice if it could be available though and could signify incomplete communication between the printer and CUPS. I don't have enough information to know if this is an ongoing bug or not.

Revision history for this message
gf (gf-interlinks-deactivatedaccount) wrote :

Hi Esther. Thanks for the update and the extra info. I'll look at next steps. And I'll try to find duplicates for this no-ink-levels issue.
Take care
:)
G

Changed in cups (Ubuntu):
status: Incomplete → 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.