Hi Rolf. On Wed, Jun 1, 2016 at 3:22 PM, Rolf Leggewie <debian-b...@rolf.leggewie.biz> wrote: >>> Do you know how to compile software on your own? >>> >> Yes, standard procedures shouldn't be a problem. You can even contact >> me via private mail if that helps. > > Please try http://oss.leggewie.org/scanbd/scanbd_1.4.4-1rl1.dsc >
Please see below. > There are binary packages in that directory as well, but they are for > i386. I added a bunch of tests for common configuration mistakes into > the latest init script. Unfortunately, those didn't make it in time for > jessie. Before changing the binary packages, try to replace > /etc/init.d/scanbd with the latest version from git > http://anonscm.debian.org/cgit/collab-maint/scanbd.git/plain/debian/scanbd.init > It might be enough to inform you where your configuration is wrong. Do > "/etc/init.d/scanbd status" and "/etc/init.d/scanbd restart" as root to > see you where you stand. I am almost certain your problem is not a true > bug but a configuration mistake. > Changing the init script did not help. The scanner does not get recognized and status/restart do not show any errors or any other useful info. I strongly believe there is no configuration mistake because I did not change the dist config files at all (only debug-level = 7). After that I compiled scanbd_1.4.4-1rl1 and ... voila, it works :) Jun 1 23:36:37 scanbd: /usr/sbin/scanbd: SANE_CONFIG_DIR=/etc/scanbd Jun 1 23:36:37 scanbd: /usr/sbin/scanbd: sane version 1.0 Jun 1 23:36:37 scanbd: /usr/sbin/scanbd: Scanning for local-only devices Jun 1 23:36:41 scanbd: /usr/sbin/scanbd: found device: plustek:libusb:007:027 Canon CanoScan N1240U/LiDE30 flatbed scanner Jun 1 23:36:41 scanbd: /usr/sbin/scanbd: start_sane_threads Jun 1 23:36:41 scanbd: /usr/sbin/scanbd: Starting poll thread for plustek:libusb:007:027 Jun 1 23:36:41 scanbd: /usr/sbin/scanbd: Thread started for device plustek:libusb:007:027 Jun 1 23:36:41 scanbd: /usr/sbin/scanbd: start dbus thread Jun 1 23:36:41 scanbd: /usr/sbin/scanbd: sane_poll Jun 1 23:36:41 scanbd: /usr/sbin/scanbd: Not Primary Owner (-1) Jun 1 23:36:41 scanbd: /usr/sbin/scanbd: Name Error (Connection ":1.71" is not allowed to own the service "de.kmux.scanbd.server" due to securit Jun 1 23:36:41 scanbd: /usr/sbin/scanbd: udev init Jun 1 23:36:41 scanbd: /usr/sbin/scanbd: get udev monitor Jun 1 23:36:41 scanbd: /usr/sbin/scanbd: udev fd is non-blocking, now setting to blocking mode Jun 1 23:36:41 scanbd: /usr/sbin/scanbd: start udev thread Jun 1 23:36:41 scanbd: /usr/sbin/scanbd: udev thread started Jun 1 23:36:41 scanbd: /usr/sbin/scanbd: found 45 options for device plustek:libusb:007:027 Jun 1 23:36:41 scanbd: /usr/sbin/scanbd: sane_find_matching_options Jun 1 23:36:41 scanbd: /usr/sbin/scanbd: found 5 actions in section (null) Jun 1 23:36:41 scanbd: /usr/sbin/scanbd: checking action scan with filter: ^scan.* Jun 1 23:36:41 scanbd: /usr/sbin/scanbd: found active option[2] mode (type: 3) for device plustek:libusb:007:027 Jun 1 23:36:41 scanbd: /usr/sbin/scanbd: found active option[3] depth (type: 1) for device plustek:libusb:007:027 Jun 1 23:36:41 scanbd: /usr/sbin/scanbd: found active option[5] resolution (type: 1) for device plustek:libusb:007:027 [...] Jun 1 23:46:45 scanbd: /usr/sbin/scanbd: checking option preview number 6 (0) for device plustek:libusb:007:027: value: 0 Jun 1 23:46:45 scanbd: /usr/sbin/scanbd: polling thread for plustek:libusb:007:027 cancellation point Jun 1 23:46:45 scanbd: /usr/sbin/scanbd: polling device plustek:libusb:007:027 [...] I did not test any scan functions yet, but I hope everything works well when the scanner shows up in the log file. I also double-checked by re-installing scanbd_jessiedist again: does not work. Re-installing scanbd_1.4.4-1rl1: works. Chris
