Replies: 5 comments 1 reply
-
|
Are you sure SANE doesn't work at all in NAPS2? When I try with my LIDE400 I get IOError the first time I try, but it works the second time. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Yep, SANE doesn't work at all. When I run the first scan, NAPS2 displays the progress window but nothing happens and the window shows endlessly zero progress. When after 30-40 seconds of zero progress I hit the cancel button and then restart the scanning, I get IoError for the next and all consequent attempts until the scanner is reconnected: 
I've collected logs with LIBUSB_DEBUG=4 for the first run (endless progress window): No more logs after that point until I cancel&restart scanning and then I get the following logs (just straight continuation of the previous one): Unfortunately, I'm not an expert in libusb to understand what's wrong there. |
Beta Was this translation helpful? Give feedback.
-
|
What Mac model? Specifically is it a newer M1/M2 Mac or an older Intel Mac? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I have a MacBook Pro 16" x86_64 and a MacBook Pro M2. Both show identical errors. BTW, I connected a scanner to a real Linux machine (not a virtual one as I mentioned at the beginning of the discussion), and "scanimage" has successfully acquired an image. This renders an issue as macOS specific since even a Linux VM running on a macOS cannot work properly with the hardware. Also, the UTM app I'm using to run virtual machines has some mentions about USB specifics which could explain why the scanimage on the Linux VM doesn't differ much from the macOS:
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Weird, I have almost exactly the same hardware and OS and it works fine for me. Can you collect logs with SANE_DEBUG_PIXMA=255? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Here they are: Now happens nothing, progress is stuck, let's cancel and scan again: Weirdly, I'm not getting IoError anymore. UPD: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello everyone,
I'm stuck with my issues and I don't know how to get them resolved, the only thing I know they are not related to my scanner. I have two issues.
My environment:
macOS Sonoma 14.1
Canon LiDE 400
NAPS2 7.1.2
SANE backend
The SANE backend detects my scanner but scanning itself fails either in NAPS2 or in CLI in macOS and Linux VM:
I came across the discussion over a similar issue on GitHub: libusb/libusb#919. According to the discussion the libusb and NAPS2 v7.0 have fixed it for macOS, but I'm still getting it.
Apple's scanning backend
Since the SANE backend isn't working I'm generally using Apple's. Unfortunately, Apple has a bug in its backend and all images acquired through it are heavily corrupted by compression artifacts despite the lossless output format selected like tiff or png.
All apps using this backend are getting these artifacts, including NAPS2 and Apple's Image Capture. The only exception here is VueScan which gives a clear image (I guess it uses its own proprietary backend).
Examples of images scanned at 600dpi from different apps:
Since VueScan gives a clear image on the same hardware, the issue is in the software.
I would appreciate any help.
Beta Was this translation helpful? Give feedback.
All reactions