Bug 31222

Summary:	When installed through MCC, USB-connected, eSCL-capable HP MFPs can only use the eSCL driver: hpaio produces errors.
Product:	Mageia	Reporter:	Thomas Andrews <andrewsfarm>
Component:	RPM Packages	Assignee:	All Packagers <pkg-bugs>
Status:	REOPENED ---	QA Contact:
Severity:	major
Priority:	High	CC:	mageia
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Attachments:	screenshot of scannerdrake results

Description Thomas Andrews 2022-12-05 01:49:00 CET

Description of problem:
When a USB-connected HP Multi-Function-Printer (MFP) that is eSCL-capable is installed using system-config-printer through MCC, only the eSCL scanner driver is actually available. The simple-scan utility that is installed by system-config-printer shows the eSCL and hpaio drivers as available, but only the eSCL one works.

The same is true of xsane, installed after the printer. I checked, and the line "hpaio" is on the end of /etc/saned/dll.conf. But the hpaio driver throws an IO error when the user attempts to use it. The printer part seems to work normally.

The scannerdrake utility shows three scanners "available" but only the eSCL option works. I will attach a screenshot of the scannerdrake output.

The affected printer is an HP Envy Photo 7858, but I believe that any HP eSCL-capable MFP would be affected. My printer is not supposed to require the HP plugin. I do not know if other brands are affected, as I only have the one MFP. I also do not know as yet if this hardware would be affected if it had been installed as a network printer/scanner, rather than USB.

I believe Mageia 8 may also have been affected since the introduction of eSCL support, but I have not been able to check that out yet. I will try to do that tomorrow and report it here.

This may be a duplicate of Bug 31007, but I'm not sure of that. The reporter for that bug reported printer issues as well, and uses a different model of printer. That might be making the difference, and it might not.

I'm going to call this critical, even though the eSCL driver does work, as I don't know if the hpaio drivers for non-eSCL-capable MFPs are also affected.

Comment 1 Thomas Andrews 2022-12-05 01:50:35 CET

Created attachment 13543 [details]
screenshot of scannerdrake results

Thomas Andrews 2022-12-05 01:51:01 CET

Priority: Normal => High

Comment 2 Nicolas Salguero 2022-12-05 15:06:58 CET

Hi,

With hplip-3.22.10-2.mga9, I reverted back to the previous behaviour, which was the cause of bug 10072.  Does it works better?

Best regards,

Nico.

CC: (none) => nicolas.salguero

Comment 3 Thomas Andrews 2022-12-05 17:44:07 CET

Doesn't seem to make a difference on an installed MFP. Removing the MFP and re-installing it made no difference, either.

Comment 4 Lewis Smith 2022-12-05 21:43:22 CET

Nicolas, as you have already looked at this, may we assign it to you?
But please do re-assign it if you know better.

Assignee: bugsquad => nicolas.salguero
CC: nicolas.salguero => (none)

Comment 5 Lewis Smith 2022-12-05 21:47:24 CET

Downgraded Critical because it does not look like it: "only the eSCL one works", so I do not think a unique vital function is broken. Revert this TJ if I have it wrong.

Severity: critical => major

Comment 6 Thomas Andrews 2022-12-05 22:44:38 CET

My concern was that if it is the hpaio protocol/driver that isn't working, then hp scanning devices that aren't eSCL-capable may not be working at all. 

But, not having hardware with which to test for this possibility, I can't say that it is actually happening.

Comment 7 Martin Whitaker 2022-12-07 22:29:35 CET

As also reported on qa-discuss:

Running the Mageia-9-beta1-Live-Xfce-x86_64 ISO in VirtualBox, after connecting my elderly HP MFP, scannerdrake shows this:

  The following scanner

    -  Hewlett-Packard Photosmart_C4100_series all-in-one

  is available on your system.

and simple-scan is able to scan a document. After configuring the printer in MCC, HP Device Manager sees the scanner and will launch XSane, which can also scan a document.

CC: (none) => mageia

Comment 8 Martin Whitaker 2022-12-07 23:20:54 CET

And I just confirmed, by first removing then readding 'hpaio' to /etc/sane.d/dll.conf, that it is using the hpaio scanner driver.

Comment 9 Thomas Andrews 2022-12-07 23:42:46 CET

Thank you Martin. Now we know.

So, since my printer refuses to work with anything but the eSCL driver, it would be easy to jump to the conclusion that a user can have one driver for a particular scanner active, despite what Xsane and the other scanning apps are telling me. If this is true, then the scanning apps should only be offering to use the active driver.

Comment 10 Thomas Andrews 2022-12-08 00:00:52 CET

Well, that's interesting. I just tried removing "escl" from /etc/sane.d/dll.conf.

 It didn't make any difference. Xsane still presents the escl and hpaio choices, and will only come up if escl is chosen. The hpaio choice brings up an error.

Comment 11 Thomas Andrews 2023-01-02 22:47:07 CET

This appears to have been fixed shortly after the second round of beta1 test isos. My HP MFP now uses hpaio for scanning, and the eSCL driver is no longer invoked when I install the MFP. 

Marking this as resolved - for now, anyway.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 12 Thomas Andrews 2023-01-04 00:01:57 CET

And just like that, it's back again. After some more updates over the last couple of days, the hpaio driver no longer works with that scanner, but an escl driver does. This must be the escl driver that is included with SANE, as the sane-airscan packages are NOT installed.

I believe it has something to do with the nagging hplip "device communication error" situation, but with my limited knowledge, I can't point to anything for sure.

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Comment 13 Thomas Andrews 2023-01-15 21:26:50 CET

(In reply to Thomas Andrews from comment #12)
> 
> I believe it has something to do with the nagging hplip "device
> communication error" situation, but with my limited knowledge, I can't point
> to anything for sure.

Additional usage indicates this is the case. As with that bug in Mageia 8, if one boots with the scanner powered up, the hpaio driver will not work but the escl driver will. And if the system is booted with the scanner powered down,and the scanner powered up once booting is finished, then the hpaio driver works.

Nicolas Salguero 2023-10-19 10:20:38 CEST

Assignee: nicolas.salguero => pkg-bugs