I made the next step. After I have changed the user from saned to root in scanbd.conf I am able to start scanbd and it starts polling the usb device.
scanbd.conf looks like this now: # drop priviliges to this user #============================= # Linux (most distributions use the saned user): # user = saned # ArchLinux (ArchLinux doesn't have saned user) # user = daemon # *BSD # user = root # user = saned user = root I have started scanbd from command line and it works well. $ scanbd -c /etc/scanbd/scanbd.conf -d7 -f scanbd: foreground scanbd: reading config file /etc/scanbd/scanbd.conf scanbd: debug on: level: 7 scanbd: dropping privs to uid root scanbd: dropping privs to gid scanner scanbd: group scanner has member: scanbd: saned scanbd: drop privileges to gid: 124 scanbd: Running as effective gid 124 scanbd: drop privileges to uid: 0 scanbd: Running as effective uid 0 scanbd: dbus_init scanbd: dbus match type='signal',interface='org.freedesktop.Hal.Manager' scanbd: SANE_CONFIG_DIR not set scanbd: sane version 1.0 scanbd: Scanning for local-only devices scanbd: found device: plustek:libusb:002:008 Canon CanoScan LiDE25 flatbed scanner scanbd: start_sane_threads scanbd: Starting poll thread for plustek:libusb:002:008 After I have pressed one of the buttons, scanbd calls my script - let's say scan.sh - in order to finally run the scanimage command. Perfect! Nevertheless, I said one step. The normal case is to start scanbd via systemd. But in this case my scan.sh-script with scanimage does not find devices. In this case I find the following messages in syslog: Dec 8 13:41:28 my-desktop dbus-daemon[617]: [system] Activating via systemd: service name='de.kmux.scanbd.server' unit='dbus-de.kmux.scanbd.server.service' requested by ':1.270' (uid=1 pid=14081 comm="/usr/sbin/scanbm -c /etc/scanbd/scanbd.conf " label="unconfined") Dec 8 13:41:53 my-desktop saned[14110]: saned (AF-indep+IPv6) from sane-backends 1.0.27 starting up Dec 8 13:41:53 my-desktop saned[14110]: check_host: access by remote host: ::ffff:127.0.0.1 Dec 8 13:41:53 my-desktop saned[14110]: init: access granted to saned-user@::ffff:127.0.0.1 Dec 8 13:41:54 my-desktop scanbd[12422]: scanimage: no SANE devices found Dec 8 13:41:54 my-desktop saned[14110]: saned exiting Dec 8 13:41:54 my-desktop dbus-daemon[617]: [system] Activating via systemd: service name='de.kmux.scanbd.server' unit='dbus-de.kmux.scanbd.server.service' requested by ':1.270' (uid=1 pid=14081 comm="/usr/sbin/scanbm -c /etc/scanbd/scanbd.conf " label="unconfined") Dec 8 13:42:01 my-desktop systemd-resolved[496]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Dec 8 13:42:01 my-desktop systemd-resolved[496]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. I haven't solved it yet. In general I guess that all this is related to permissions and roles. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747115 Title: scanbd does not find scanner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scanbd/+bug/1747115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
