[sane-devel] [scanbd] using scanbd and saned over network at the same time

Rolf Leggewie foss at rolf.leggewie.biz
Fri Feb 19 16:29:07 UTC 2016

Hello Wilhelm,

thank you for the quick response.

On 19.02.2016 22:52, Wilhelm wrote:
> Am 19.02.2016 um 14:38 schrieb Rolf Leggewie:
>> Hello,
>> I'd like to know if it is possible to have a computer that does
>> button-triggered scanning via scanbd but also exports the scanner over
>> the network to be accesible via the common. How would one do that?
> Well, absolutely: thats the whole story of scanbd (see the readme.txt of
> scanbd).

Well, I am aware of the general idea how saned and scanbd are supposed 
to interact.  It can be pretty complicated to configure this error-free. 
  Going from one machine back to a real network adds yet another layer 
of complexity (and I was bitching when getting saned over network to run 
for the first and a couple subsequent times).

As you probably know, I added a couple of checks for common 
configuration errors to the Debian scanbd startup script.  Anything 
detected by 
is OK on my scanbd server machine.  Button presses are detected fine by 
scanbd.  But with this configuration, the scanner will only be detected 
by sane-find-scanner and not be "scanimage -L".

$ sane-find-scanner | grep ^found
found USB scanner (vendor=0x04a9 [Canon], product=0x2213 [CanoScan]) at 

Should this really be libusb?

Only if I add the genesys backend to /etc/sane.d/dll.conf, shut down 
scanbd and start up saned do I get an output from "scanimage -L".

$ scanimage -L
device `genesys:libusb:001:035' is a Canon LiDE 35/40/50 flatbed scanner

That's when I also get a response from a network-connected client.

$ scanimage -L
device `net:himbeere.local:genesys:libusb:001:035' is a Canon LiDE 
35/40/50 flatbed scanner

So, what am I likely doing wrong here? Any idea?

When scanbd is running (and thus scanimage is broken locally as well as 
over the network), the following is the status:
- scanbd service is running
- saned service is stopped
- /etc/sane.d/dll.conf contains only the net backend
- /etc/scanbd/dll.conf does NOT contain the net backend
- /etc/scanbd/dll.conf contains the necessary genesys backend
   (and a few others)



More information about the sane-devel mailing list