[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#879719: libsane-hpaio: Does not recognize OfficeJet Pro 8710



On Wed 22 Nov 2017 at 18:43:45 +0100, Gedalya wrote:

> On 11/21/2017 08:09 PM, Brian Potkin wrote:
> >
> > Hello Gedalya. Thank you for your report. I forwarded it upstream and
> > now you will see there is a reply. Please would you respond to that
> > message there as I am unable to speak for you.
> 
> I'll look into that. Thank you!

I see you already have. Thanks.
 
> >
> > Meanwhile, let's see what we can do here. First, upgrade hplip to the
> > latest, 1.17.10+repack0
> 
> Already done, I update my system frequently. No change regarding this issue.
> 
> >  and read
> >
> >  https://wiki.debian.org/SaneOverNetwork
> >
> > Post the output of
> >
> >  scanimage -L
> 
> ---
> 
> $ scanimage -L
> 
> 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).
> 
> ---
> 
> Note: In order to produce this, I need to stop cupsd. Somehow, at some
> point sane started finding the scanner via CUPS, the printer being
> configured there.

I take this to mean you configured the printer with something like
hp-setup and the device_uri for it begins with hp:/. Please post the
output of

 lpoptions -p <print_queue_name>

as confirmation of this. Also post what you get for

 avahi-browse -art | grep -i officejet

You might have to install the avahi-utils package. 

> On my laptop, where this printer is not installed in CUPS, there is no
> need to stop CUPS to get this error.

Post

 lpoptions -p <print_queue_name>

for this machine too.

> With CUPS running, or with models.dat edited:
> 
> $ scanimage -L
> device `hpaio:/net/officejet_pro_8710?ip=192.168.9.238&queue=false' is a Hewlett-Packard officejet_pro_8710 all-in-one

I think an explanation for the "CUPS running" can be provided. How
editing models.dat affects this is still uncertain. Upstream says:

 > ...no need to modify the printer name in models.dat file
 > because it is taking the actual name of the printer.

It appears to be the source code file dat2drv.py which takes care of
this as there is some replacement of strings in the model name. Not
understanding python, I'm unable to see how exactly how it all fits
together.

Regards,

Brian.


Reply to: