You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 26, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 26, 2026. It is now read-only.
I came across a minor problem when recovering from a scanner error on my Linux box with paperwork 1.2.2 . Every time I get a pysane error message the error persists and blocks the scanner even after the physical problem is solved.
As I haven't got a Windows machine: Can anybody verify the situation on windows?
Workaround:
Changing to another scanner in the preference and back (or restarting paperwork) clears the pysane-error and allows me to scan again.
I would kindly suggest to hard-reset the scanner after an error to recover full scanner-function. This can be a real pain in the back when you have to scan a bigger amount of paper.
A page too much was entered. -> "No page found" - error.
Put more documents in the feeder and made sure the scanner recognized them
Scanning from feeder still states the "No page found" - error.
It's the same for any other error. ("device busy", "device error", "scanner jammed" etc.)
Closing and restarting paperwork helps - as does selecting another device and switching back.
Hm, unfortunately, Paperwork diagnostic output is not verbose enough regarding scanning at the moment. However, I've made a scanner database and a test program to automatically generate and upload reports to this database. This test program includes the latest version of the library Pyinsane. It also include logs much more detailed than what Paperwork has.
Either the problem is reproduced with this test program (in which case I will hopefully have enough info to fix the problem), or the problem has been fixed in the latest versions of Pyinsane.
Activity
jflesch commentedon Jan 15, 2018
Regarding Windows, it's a whole different implementation (WIA instead of Sane), so I don't think it would be of any help.
jkrenzer commentedon Jan 15, 2018
Situation:
It's the same for any other error. ("device busy", "device error", "scanner jammed" etc.)
Closing and restarting paperwork helps - as does selecting another device and switching back.
I attached the output of the diagnostics.
Thank you!
Jörn
paperwork_diagnostics_#736_20180115.txt
jflesch commentedon Mar 5, 2018
Hm, unfortunately, Paperwork diagnostic output is not verbose enough regarding scanning at the moment. However, I've made a scanner database and a test program to automatically generate and upload reports to this database. This test program includes the latest version of the library Pyinsane. It also include logs much more detailed than what Paperwork has.
Could you run a test scan using this test program please ?
https://openpaper.work/en/scanner_db/#contribute
Either the problem is reproduced with this test program (in which case I will hopefully have enough info to fix the problem), or the problem has been fixed in the latest versions of Pyinsane.