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

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



On 12/01/2017 02:04 PM, Brian Potkin wrote:

Sorry; another typo. It's drv:///hpcups.drv/hp-envy_4500_series.ppd


OK, finally I get:

device `hpaio:/net/envy_4500_series?ip=192.168.9.238' is a Hewlett-Packard envy_4500_series all-in-one
You are definitely not wasting my time. I'm unsure whether the issue is
the result of a bug. You report that

  scanimage -vv -d hpaio:/net/HP_OfficeJet_Pro_8710?ip=192.168.9.238 > image.pnm

works. This the strongest possible indication that this is the correct
device_uri.
Don't know what "correct" means. To me, "what works" is a good definition, and that points to multiple answers in this case.

It seems to be not case-sensitive, but the hp_ prefix is required.
This works:

scanimage -vv -d hpaio:/net/hp_officejet_pro_8710?ip=192.168.9.238

Casing set aside, whatever junk I put between hpaio:/net/ and ?ip= shows up in syslog:

scanimage: io/hpmud/model.c 532: no not_in_models_dat__1234 attributes found in /usr/share/hplip/data/models/models.dat

So once again, the correct URI is whatever is in models.dat. I can change models.dat to match the printer's broadcast, or the firmware can change. Or, we can make the hp_ prefix optional, as we have seen implemented in the code, just not in this particular place.

I'd expect using simple-scan and xsane instead of scanimage
also to work without any editing of models.dat. Do they?

Only when CUPS is running. simple-scan behaves exactly like scanimage without the -d parameter.

I have found your first mail and all the information you have provided
to be very detailed, clear and useful. The problem is fitting it all
together to form a coherent picture. One problem is this editing of
models.dat, which upstream says is unnecessary;

What's necessary is for the darn thing to work.
At least I think we have the problem clearly written out here, with some circumstantial evidence.
Upstream's comments are welcome now.


Reply to: