Closed ShadesJeff closed 3 years ago
Unfortunately, I cannot do anything about this. scanbd needs exclusive access to the scanner device, and will only release it during script execution. If you try to actually scan using scanimage while scanbd is active, I think it will fail as well.
Actually, running the following command does produce output:
sudo -u saned scanimage -b --format png -d 'net:localhost:fujitsu:ScanSnap iX500:1225526' --source 'ADF Front' --resolution 150
So, I think AirSane should also work...
Unfortunately, scanbd is terribly documented, but it is configured such that the scanbd service proxies requests for the scanner from clients through the net
interface and then releases the scanner to execute those requests. So, while scanbd does have exclusive access to the device 'fujitsu:ScanSnap iX500:1225526'
it shares the scanner as device 'net:localhost:fujitsu:ScanSnap iX500:1225526'
and accessing that device with the saned interface should work and does with the native clients.
As expected, AirScan does work with scanbd if configured correctly. In my case, the default scanbm.socket
configuration only allows 1 socket connection at a time. When I increased this limit to 64, then AirScan works as anticipated.
It is unclear to me why this value did not need to be increased for scanimage
to work... only for AirScan to work.
AirSane is working nicely when using saned alone with my scanner, but when I introduce scanbd to make the on-scanner buttons works, AirSane errors when opening the scanner.
I started AirSane with the following command:
sudo -u saned airsaned --debug=true --access-log=- --local-scanners-only=false
and got the following output:
The standard SANE front-ends (scanimage and scanadf) work properly, e.g.: