Scanner no longer operational

Leveret

Leveret

HP OfficeJet 4650 on FreeBSD 15.1 I used to scan perfectly using Xsane. Now I get an error message saying the scanner cannot be accessed. It works fine on a linux system so the hardware isn't the problem. I install hplip as usual and various tests using the handbook's advice on setting up an image scanner. Does anyone know if something was changed with FreeBSD? Simple-scan gives me the same result. Even on GhostBSD, I get the same error. Thanks in advance for any help.
 
Yes. It shows up on command line when using usbconfig list. The gui almost opens when using Xsane or SimpleScan but then crashes.
 
It's been 20 years since I've messed with sane but isn't there a command line interface (scanimage)? Kind of humorous that SANEis Scanner-Access-Now-Easy, but is anything but. LOL
 
I experienced today something similar with my Canon Scanner (FreeBSD 14.4). Gimp wasn't capable anymore to find any device.
I started xsane from the CLI, simply typed xsane in the shell, worked.
So, maybe it's not xsane but the software that uses it, like Gimp. Since I don't not really use Gimp, and xsane is working by starting from the CLI, to me it's OK.
 
Does HP have relevant configuration files? I don't generally print directly from my computer, but I know that some manufacturers like Canon provide configurations in their Linux packages that can be used. I don't see any reason why CUPS and sane configurations from there wouldn't work if there's one that you can copy from Linux.
 
Leveret said:
HP OfficeJet 4650 on FreeBSD 15.1 I used to scan perfectly using Xsane. Now I get an error message saying the scanner cannot be accessed. It works fine on a linux system so the hardware isn't the problem. I install hplip as usual and various tests using the handbook's advice on setting up an image scanner. Does anyone know if something was changed with FreeBSD? Simple-scan gives me the same result. Even on GhostBSD, I get the same error. Thanks in advance for any help.
Click to expand...
I can confirm the same issue with my hp deskjet 2544 printer. Scanning doesn't work anymore after the update to hplip 3.26.6. It works on Linux Mint with an older hplip version.

When I try to scan from hplip or xsane from the command line I get the following error message: Error opening device "hpaio:/net/Deskjet_2540_series". Error during device I/O

It worked for years on FreeBSD. I think the issue is related to the hplip-update but I'm not sure. Printing works!
 
I'm not familiar enough with Linux to use configurations in their packages. I think it has to do with the hplip-update based on what Stefan wrote. That's the exact message I get and printing also works on my machine.
 
Maybe something permissions based changed. IE. tightened up permissions on hplip or similar.

Do you have a devd rule setup for users and access to the device?

Using Xorg as root is horrible but checking a scanner it can save troubleshooting time.

henryleach.com

Setting Up a Scanner on Freebsd

Scanning is possible on FreeBSD, and well described in the handbook, but doesn't explain how to make scanning work for non-root users, which is what I wanted, as I don't want to running as root for day-to-day tasks.
henryleach.com henryleach.com
 
here is what my ai chatbot lumo says:

Yes, there is clear evidence of this on the internet. The problem is well documented:

## The Facts

**The actual bug:** On Launchpad (the HPLIP bug tracker), the issue was reported as bug [#2172090](https://launchpad.net/hplip): *"hpaio: chunked http_read() double-counts bytes_read → LEDM scan over USB fails."* Specifically, the `http_read()` function in `scan/sane/http.c` counts read bytes twice, which causes the error **"response exceeds buffer"** during scanning (e.g. `read=8174 len=28 max=8192`). Devices communicating via the LEDM protocol are particularly affected — typically HP DeskJet and OfficeJet All-in-One printers, mostly when connected via USB.

**Confirmations from the forums:**

- On the [openSUSE forum](https://forums.opensuse.org/t/hp-scanner-no-longer-working/196317), several users report that after updating to HPLIP 3.26.6, the scanner is still detected by `scanimage -L`, but every scan attempt fails with **"Error during device I/O."** A downgrade to **3.26.4** fixed the problem for them. There is also a corresponding thread on the Arch Linux forum.
- The bug occurs on various devices — the Launchpad bug tracker includes reports for, among others, the HP Envy 5032 (*"scanning does not work since 3.26.6"*, bug #2169330), OfficeJet Pro 8710/8720, and the Smart Tank 500 — so classic AIO models like the DeskJets.

## What you can do

1. **Downgrade to HPLIP 3.26.4** — the solution confirmed by several users, provided your distribution still offers that package.
2. **Alternative: use ipp-sane/AirScan** — the SANE eSCL driver (`sane-airscan`) completely bypasses the broken HPLIP backend. One openSUSE user solved their problem this way without a downgrade; for this you simply need to set up the scanner via AirScan instead of `hpaio` (e.g. an entry in `/etc/sane.d/airscan.conf`, or just disable `hpaio` in `dll.conf` if AirScan finds the device automatically).
3. **Wait it out** — the bug has been reported on Launchpad; presumably it will be fixed in a subsequent release. There are already patches under discussion.

In short: yes, the update to 3.26.6 introduced a genuine regression bug in the scanning backend that causes exactly the symptoms you described. Printing is not affected — only scanning through the `hpaio` backend.

Do you need a concrete guide for the downgrade on your system (FreeBSD?) or for switching to AirScan?
 
Well, this is the problem on FreeBSD. You can't switch back to an older version when you use binary packages. Only the latest version is available in the FreeBSD Repository.

My solution is to "wait it out" on FreeBSD. If it is really urgent, I will start my Linux Mint Laptop ...

Sorry I can't give you a guide how to downgrade on FreeBSD.
 
No worries. I can wait until it is fixed. Scanning was the only thing I'm having trouble on and I can use a Linux distro for that if need be. Thanks for your help.
 
covacat said:
if you have the old one in /var/cache/pkg you can pkg delete -f the current one and add -f the cached one
then maybe lock it until the problem gets solved
Click to expand...

thanks a lot. I found hplip-3.26.4.pkg in /var/cache/pkg on one of my laptops that I don't use very often (usually I do a pkg clean before installing a quarterly update). now I am able to scan again :)
 
You must log in or register to reply here.
Back
Top