-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem using simple-scan when scanning document exceeds one page #1771
Comments
Issue opened at the request of @alfisya |
Okay, I managed to solve this on my printer (HP Deskjet 5820) by installing Now, the question is would it be good to just add |
New elements: From this day (01/08/2024) I scanned a 2-page document withsimple-scan, 3 updates were produced for the packages hplip and hplip-drivers:
NB. The previous update then dates back to 07/29/2023. I tested each version, from the most recent to the one that took place before my last scan. I was this one that worked, by typing the following terminal command: An important (and surprising) note: I was able to scan a 2-page document using a single page (Page unique) instead of multiple pages from a flat scanner (Pages multiples depuis un numériseur à plat)! |
@malfisya ask me to precise that this issue concerns @TraceyC77 (the maintainer of |
Thank you, @PennyFarthing-GH , for providing so much detail about this problem. That will help me narrow down the problem. I've done testing with my own HP Color LaserJet Pro MFP M479fdn printer / scanner. I'm looking into our hplip package to see if there's a problem caused by how we package it. @malfisya Testing detailsAll 3 scanning programs I tested with can connect to the printer (as in the original message). Simple Scan (Document Scanner) - scanned all pages successfully. Skanpage (flatpak) - no error. |
@TraceyC77 Maybe you already saw it, but this is the forum post where it all started https://discuss.getsol.us/d/10368-simple-scan-hp-printer-scanner. (With much unnecessary details 😅). |
@malfisya Yes, I was already following that forum thread. No need to ping me here. I keep an eye on printer related forum threads If you have any specific details to add, please add them here. |
Remove patch that causes scanning to fail Remove other patches that are no longer used or needed Depends on /pull/1893 Fixes /issues/1771
**Summary** Remove patch that causes scanning to fail Remove other patches that are no longer used or needed Depends on /pull/1893 Fixes /issues/1771 **Test Plan** Used simple-scan to scan a document from the ADF of an HP AIO, and then a document on the flatbed. Verified scan was successful and produced no errors. **Checklist** - [x] Package was built and tested against unstable
Please confirm there isn't an existing open bug report
Summary
I am a Budgie Desktop user and I use an HP Officejet 2622 printer.
Unable actually to scan a document exceeding one page with
simple-scan
.Steps to reproduce
When I want to scan a document of several pages with this application, the first page is scanned without any problem, but when I get to the second page, an error message "Impossible de se connecter au périphérique de numérisation" (unable to connect to scanning device) appears systematically.
Expected result
I want to scan documents with
simple-scan
whatever the number of pages to scan.Actual result
The following error message appears when scanning the 2nd page:
"Impossible de se connecter au périphérique de numérisation"
(unable to connect to scanning device)Environment
Repo
Shannon (stable)
Desktop Environment
Budgie
System details
Other comments
With the software
Skanpage
, I was able to scan all the pages of my document. But, from the 2nd page, by clicking on the Numériser button (scan), I obtained the message "Argument incorrect
"; so, by clicking this button a 2nd time, scanning was normally done.With another one called Master PDF Editor someone in the Solus Forum suggested to try, it says "
Error open device
".It's as if
simple-scan
(or other software like this) didn't recognize correctly the device printer.The text was updated successfully, but these errors were encountered: