HP OfficeJet Pro 8710: no scanner detected

Bug #1728107 reported by brian_p
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
HPLIP
In Progress
Undecided
Unassigned

Bug Description

A Debian user reports that scanning with his HP OfficeJet Pro 8710 is only possible after adjusting models.dat to add the device to it. Bug #879719.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879719

Regards,

Brian.

Revision history for this message
Afshan F (afshan) wrote :

Hi Brian,

Can you please mention on which version of debian you had tested and what is the exact error you are getting while you're performing scan operation?

I am trying to reproduce the issue but the scanner seems to work fine in Debian and there is no need to modify the printer name in models.dat file because it is taking the actual name of the printer.
Please check once with the latest hplip-3.17.10.run file. And try with hp-scan -g command in the terminal to get the debug logs.

Thanks,
Afshan

Changed in hplip:
status: New → In Progress
Revision history for this message
brian_p (claremont102) wrote :

Hello Afshan, thank you for the response.

I am only the middleman (I do not possess the device) and am triaging a bug submitted to the Debian BTS. On reflection, I could have done a bit more triaging before forwarding it.

I will inform the bug submitter of your reply and encouage him to answer for himself here. The fact that the scanner works for you is noted.

Cheers,

Brian.

Revision history for this message
gedalya (gedalya) wrote :

Hi,

I'm the original reporter on the Debian BTS.
I'm using Debian Testing "buster", with hplip 3.17.10+repack0-1.
This is my output, with cupsd notably stopped. When cupsd is running and the AIO is configured as a printer in CUPS, this issue does not occur.

jedi@ws2:~$ date; scanimage -vv -L
Wed Nov 22 19:31:46 CET 2017

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).
Calling sane_exit
scanimage: finished
jedi@ws2:~$ date; hp-scan -g
Wed Nov 22 19:31:56 CET 2017

HP Linux Imaging and Printing System (ver. 3.17.10)
Scan Utility ver. 2.2

Copyright (c) 2001-15 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

hp-scan[20904]: debug: getDeviceUri(None, None, ['hpaio'], {'scan-type': (<built-in function gt>, 0)}, , True)
hp-scan[20904]: debug: Mode=0
error: No device selected/specified or that supports this functionality.
jedi@ws2:~$

syslog:

Nov 22 19:31:51 ws2 scanimage: io/hpmud/model.c 532: no officejet_pro_8710 attributes found in /usr/share/hplip/data/models/models.dat
Nov 22 19:31:51 ws2 scanimage: io/hpmud/model.c 543: no officejet_pro_8710 attributes found in /usr/share/hplip/data/models/unreleased/unreleased.dat
Nov 22 19:32:02 ws2 python3: io/hpmud/model.c 532: no officejet_pro_8710 attributes found in /usr/share/hplip/data/models/models.dat
Nov 22 19:32:02 ws2 python3: io/hpmud/model.c 543: no officejet_pro_8710 attributes found in /usr/share/hplip/data/models/unreleased/unreleased.dat
Nov 22 19:32:02 ws2 /hp-scan: hp-scan[20904]: error: No device selected/specified or that supports this functionality.

My guess was that the logged "officejet_pro_8710" is an ID which is expected to match a section name in models.dat. Said file is shipped with a section named "hp_officejet_pro_8710" and removing the "hp_" prefix indeed fixes the issue. This is not the same thing as the properly capitalized and styled printer name used for display purposes. See my detailed debian bug report.

Revision history for this message
brian_p (claremont102) wrote :

Hello,

Gedalya (the Debian bug report submitter) and I have spent some time looking at this issue. My conclusions are summarised at

https://lists.debian.org/debian-printing/2017/12/msg00004.html

and Gedalya gives his take at

https://lists.debian.org/debian-printing/2017/12/msg00005.html

Is this a firmware or HPLIP bug. If it is the former, I can close the Debian bug report.

Regards,

Brian.

Revision history for this message
brian_p (claremont102) wrote :

From my testing with an avahi service file for the 8710 it seems to me that LP #1797501 is involved:

https://bugs.launchpad.net/hplip/+bug/1797501

Please would HPLIP upstream take a look at this aspect of this issue?

--
Brian.

Revision history for this message
brian_p (claremont102) wrote :

> From my testing with an avahi service file for the 8710 it seems to me that LP
> #1797501 is involved:

gedalya now reports in the referenced Debian bug that his ability to scan has been restored. Prior to this, I had demonstrated to my own satisfaction that a failure to find officejet_pro_8710 should be followed by looking for hp_officejet_pro_8710. The latter did not happen; hence the problem.

This seems to be fixed now. The Release Notes mention nothing.

--
Brian.

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.