I've been trying to make this work all day. I'm almost there but something is still missing. Here's the story so far:
- Debian Jessie 8.3 headless home server
- Canon MP140 MFP scanner/printer fully supported by SANE, via USB
- SANE dll.conf configured and working (everything commented out except net and pixma)
scanimage -p --resolution 300 --format=tiff --mode Gray -x 210 -y 297 > test300.tiff
...scans an A4 paper in grayscale and saves it as tiff just fine.
sudo service scanbd status ● scanbd.service - Scanner button polling Service Loaded: loaded (/lib/systemd/system/scanbd.service; disabled) Active: active (running) since Fri 2016-02-19 19:24:03 CET; 23min ago Main PID: 1740 (scanbd) CGroup: /system.slice/scanbd.service └─1740 /usr/sbin/scanbd -f Feb 19 19:24:03 server scanbd: /usr/sbin/scanbd: dbus match type='signal',interface='org.freedesktop.Hal.Manager'
It appears to be running but it does not react to the buttons at all.
I tried stopping the service and starting scanbd as root - AND IT WORKS!
sudo scanbd -f scanbd: dbus match type='signal',interface='org.freedesktop.Hal.Manager' scanbd: trigger action for button-1 for device pixma:04A9172B_ABCDEF with script example.script
So, my guess was it's some kind of a permissions problem. I tried to change /etc/scanbd.conf and replace
user = scand group = scanner
user = root group = root
but then when I restart the scanbd service this is what I get, and the buttons don't work again:
● scanbd.service - Scanner button polling Service Loaded: loaded (/lib/systemd/system/scanbd.service; disabled) Active: active (running) since Fri 2016-02-19 20:07:11 CET; 4s ago Main PID: 2562 (scanbd) CGroup: /system.slice/scanbd.service └─2562 /usr/sbin/scanbd -f Feb 19 20:07:11 server scanbd: /usr/sbin/scanbd: dbus match type='signal',interface='org.freedesktop.Hal.Manager' Feb 19 20:07:11 server scanbd: /usr/sbin/scanbd: Not Primary Owner (-1) Feb 19 20:07:11 server scanbd: /usr/sbin/scanbd: Name Error (Connection ":1.96" is not allowed to own the service "de.kmux.scanbd.server" due to security policies in the configuration file)
I'm probably overlooking some obvious detail, but I can't really figure out what it is. Any help would be greatly appreciated.