[sane-devel] scanbd with old udev version
Am 24.08.2013 15:55, schrieb Sander Devrieze: 2013/8/22 Sander Devrieze s.devrieze at gmail.com mailto:s.devrieze at gmail.com snip I got a bit further this evening: 1) saned not running + /usr/local/sbin/scanbm sleep 1 SANE_CONFIG_DIR=/usr/local/etc/scanbd/ scanimage -L -- found 2) saned not running +/usr/local/sbin/scanbm sleep 1 scanimage -L -- not found 3) saned running + scanimage -L -- not found 4) saned running + SANE_CONFIG_DIR=/usr/local/etc/scanbd/ scanimage -L -- found What to try next? Please note I also still getting this error as in the beginning: libudev: udev_monitor_enable_receiving: bind failed: Operation not permitted /usr/local/sbin/scanbd: Can't enable udev receiving /usr/local/sbin/scanbd: Can't init udev Ok, I got everything working as it should. It came out the permissions in /usr/local/etc/scanbd/saned.conf had to be fixed. Can you describe what the problem was? Which permission do you mean? Or do you mean the access-list? Maybe some note can be added to the documentation? do you feel the paragraph for saned isn't sufficient? In attachment you can find my action script which is based on some GPL script I found. Same license applies. For sending the emails, I suggest installing ssmtp if you do not want to setup your own mailserver. Thank you. Will put this into the contrib dir. -- Wilhelm w.meier at unix.net
[sane-devel] scanbd with old udev version
Am 25.08.2013 11:41, schrieb Wilhelm: Am 24.08.2013 15:55, schrieb Sander Devrieze: 2013/8/22 Sander Devrieze s.devrieze at gmail.com mailto:s.devrieze at gmail.com snip I got a bit further this evening: 1) saned not running + /usr/local/sbin/scanbm sleep 1 SANE_CONFIG_DIR=/usr/local/etc/scanbd/ scanimage -L -- found 2) saned not running +/usr/local/sbin/scanbm sleep 1 scanimage -L -- not found 3) saned running + scanimage -L -- not found 4) saned running + SANE_CONFIG_DIR=/usr/local/etc/scanbd/ scanimage -L -- found What to try next? Please note I also still getting this error as in the beginning: libudev: udev_monitor_enable_receiving: bind failed: Operation not permitted /usr/local/sbin/scanbd: Can't enable udev receiving /usr/local/sbin/scanbd: Can't init udev Ok, I got everything working as it should. It came out the permissions in /usr/local/etc/scanbd/saned.conf had to be fixed. Can you describe what the problem was? Which permission do you mean? Or do you mean the access-list? Maybe some note can be added to the documentation? do you feel the paragraph for saned isn't sufficient? ohm just found a typo in the documentation ... it must read saned.conf instead of net.conf ! In attachment you can find my action script which is based on some GPL script I found. Same license applies. For sending the emails, I suggest installing ssmtp if you do not want to setup your own mailserver. Thank you. Will put this into the contrib dir. -- Wilhelm w.meier at unix.net
[sane-devel] scanbd with old udev version
2013/8/25 Wilhelm wilhelm.meier at fh-kl.de Am 24.08.2013 15:55, schrieb Sander Devrieze: 2013/8/22 Sander Devrieze s.devrieze at gmail.com snip Ok, I got everything working as it should. It came out the permissions in /usr/local/etc/scanbd/saned.**conf had to be fixed. Can you describe what the problem was? Which permission do you mean? Or do you mean the access-list? Yes, the access list contained no entries. Maybe some note can be added to the documentation? do you feel the paragraph for saned isn't sufficient? Indeed, the documentation is very good, but it is written for people who have (much) experience with configuring sane. It will be better if you write the documentation with people in mind who do not know anything about sane. -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130825/22d0cf76/attachment-0001.html
[sane-devel] scanbd with old udev version
2013/8/22 Sander Devrieze s.devrieze at gmail.com snip I got a bit further this evening: 1) saned not running + /usr/local/sbin/scanbm sleep 1 SANE_CONFIG_DIR=/usr/local/etc/scanbd/ scanimage -L -- found 2) saned not running +/usr/local/sbin/scanbm sleep 1 scanimage -L -- not found 3) saned running + scanimage -L -- not found 4) saned running + SANE_CONFIG_DIR=/usr/local/etc/scanbd/ scanimage -L -- found What to try next? Please note I also still getting this error as in the beginning: libudev: udev_monitor_enable_receiving: bind failed: Operation not permitted /usr/local/sbin/scanbd: Can't enable udev receiving /usr/local/sbin/scanbd: Can't init udev Ok, I got everything working as it should. It came out the permissions in /usr/local/etc/scanbd/saned.conf had to be fixed. Maybe some note can be added to the documentation? In attachment you can find my action script which is based on some GPL script I found. Same license applies. For sending the emails, I suggest installing ssmtp if you do not want to setup your own mailserver. -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130824/b2b747d1/attachment.html -- next part -- A non-text attachment was scrubbed... Name: actions.script Type: application/octet-stream Size: 4974 bytes Desc: not available URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130824/b2b747d1/attachment.obj
[sane-devel] scanbd with old udev version
2013/8/21 Wilhelm wilhelm.meier at fh-kl.de Am 21.08.2013 16:04, schrieb Sander Devrieze: 2013/8/21 Wilhelm wilhelm.meier at fh-kl.de mailto:wilhelm.meier at fh-kl.de snip Mmh, looks good. So, if scanimage finds the scanner (started with the uid/gid as in scanbd.conf), scanbd should find it too, if started as root and the env-var SANE_CONFIG_DIR set. Scanimage does not find the scanner right now. It did only find the scanner when not using the net backend os sane. In that case, the genesys backend was immediately chosen. What else can I try? Line in /etc/passwd saned:x:104:109::/home/saned:/bin/false This uid and gid do match with scandb: /usr/local/sbin/scanbd: foreground /usr/local/sbin/scanbd: config-file: /usr/local/etc/scanbd/scanbd.conf /usr/local/sbin/scanbd: reading config file /usr/local/etc/scanbd/scanbd.conf /usr/local/sbin/scanbd: debug on: level: 7 /usr/local/sbin/scanbd: dropping privs to uid saned /usr/local/sbin/scanbd: dropping privs to gid saned /usr/local/sbin/scanbd: drop privileges to gid: 109 /usr/local/sbin/scanbd: Running as effective gid 109 /usr/local/sbin/scanbd: drop privileges to uid: 104 /usr/local/sbin/scanbd: Running as effective uid 104 /usr/local/sbin/scanbd: dbus_init /usr/local/sbin/scanbd: dbus match type='signal',interface='org.freedesktop.Hal.Manager' /usr/local/sbin/scanbd: sane version 1.0 /usr/local/sbin/scanbd: Scanning for local-only devices /usr/local/sbin/scanbd: found device: genesys:libusb:001:005 Canon LiDE 110 flatbed scanner /usr/local/sbin/scanbd: start_sane_threads /usr/local/sbin/scanbd: Starting poll thread for genesys:libusb:001:005 /usr/local/sbin/scanbd: sane_poll /usr/local/sbin/scanbd: Thread started for device genesys:libusb:001:005 /usr/local/sbin/scanbd: start dbus thread /usr/local/sbin/scanbd: timeout: 500 ms /usr/local/sbin/scanbd: Iteration on dbus call /usr/local/sbin/scanbd: udev init /usr/local/sbin/scanbd: get udev monitor libudev: udev_monitor_enable_receiving: bind failed: Operation not permitted /usr/local/sbin/scanbd: Can't enable udev receiving /usr/local/sbin/scanbd: Can't init udev /usr/local/sbin/scanbd: found 41 options for device genesys:libusb:001:005 /usr/local/sbin/scanbd: sane_find_matching_options /usr/local/sbin/scanbd: found 5 actions in section (null) -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130821/6600f819/attachment.html
[sane-devel] scanbd with old udev version
Am 21.08.2013 23:27, schrieb Sander Devrieze: 2013/8/21 Wilhelm wilhelm.meier at fh-kl.de mailto:wilhelm.meier at fh-kl.de Am 21.08.2013 16:04, schrieb Sander Devrieze: 2013/8/21 Wilhelm wilhelm.meier at fh-kl.de mailto:wilhelm.meier at fh-kl.de mailto:wilhelm.meier at fh-kl.de mailto:wilhelm.meier at fh-kl.de snip Mmh, looks good. So, if scanimage finds the scanner (started with the uid/gid as in scanbd.conf), scanbd should find it too, if started as root and the env-var SANE_CONFIG_DIR set. Scanimage does not find the scanner right now. It did only find the scanner when not using the net backend os sane. That's ok. For a desktop machine using scanbd and local scanning apps (like scanimage), scanbd / scanbm must be running. Please read 0.1) solution from the README.txt: scanbm acts as a proxy for saned. In that case, the genesys backend was immediately chosen. What else can I try? The below log shows, that scanbd recognizes the scanner and his options. So now you have to figure out which buttons correlate to which option value changes: just press a button and watch the log. Then you can tweak the scripts for the button actions. Line in /etc/passwd saned:x:104:109::/home/saned:/bin/false This uid and gid do match with scandb: /usr/local/sbin/scanbd: foreground /usr/local/sbin/scanbd: config-file: /usr/local/etc/scanbd/scanbd.conf /usr/local/sbin/scanbd: reading config file /usr/local/etc/scanbd/scanbd.conf /usr/local/sbin/scanbd: debug on: level: 7 /usr/local/sbin/scanbd: dropping privs to uid saned /usr/local/sbin/scanbd: dropping privs to gid saned /usr/local/sbin/scanbd: drop privileges to gid: 109 /usr/local/sbin/scanbd: Running as effective gid 109 /usr/local/sbin/scanbd: drop privileges to uid: 104 /usr/local/sbin/scanbd: Running as effective uid 104 /usr/local/sbin/scanbd: dbus_init /usr/local/sbin/scanbd: dbus match type='signal',interface='org.freedesktop.Hal.Manager' /usr/local/sbin/scanbd: sane version 1.0 /usr/local/sbin/scanbd: Scanning for local-only devices /usr/local/sbin/scanbd: found device: genesys:libusb:001:005 Canon LiDE 110 flatbed scanner /usr/local/sbin/scanbd: start_sane_threads /usr/local/sbin/scanbd: Starting poll thread for genesys:libusb:001:005 /usr/local/sbin/scanbd: sane_poll /usr/local/sbin/scanbd: Thread started for device genesys:libusb:001:005 /usr/local/sbin/scanbd: start dbus thread /usr/local/sbin/scanbd: timeout: 500 ms /usr/local/sbin/scanbd: Iteration on dbus call /usr/local/sbin/scanbd: udev init /usr/local/sbin/scanbd: get udev monitor libudev: udev_monitor_enable_receiving: bind failed: Operation not permitted /usr/local/sbin/scanbd: Can't enable udev receiving /usr/local/sbin/scanbd: Can't init udev /usr/local/sbin/scanbd: found 41 options for device genesys:libusb:001:005 /usr/local/sbin/scanbd: sane_find_matching_options /usr/local/sbin/scanbd: found 5 actions in section (null) -- Wilhelm w.meier at unix.net
[sane-devel] scanbd with old udev version
2013/8/22 Wilhelm wilhelm.meier at fh-kl.de Am 21.08.2013 23:27, schrieb Sander Devrieze: 2013/8/21 Wilhelm wilhelm.meier at fh-kl.de mailto:wilhelm.meier at fh-kl.de* * Am 21.08.2013 16:04, schrieb Sander Devrieze: 2013/8/21 Wilhelm wilhelm.meier at fh-kl.de mailto:wilhelm.meier at fh-kl.de** mailto:wilhelm.meier at fh-kl.de mailto:wilhelm.meier at fh-kl.de** snip Mmh, looks good. So, if scanimage finds the scanner (started with the uid/gid as in scanbd.conf), scanbd should find it too, if started as root and the env-var SANE_CONFIG_DIR set. Scanimage does not find the scanner right now. It did only find the scanner when not using the net backend os sane. That's ok. For a desktop machine using scanbd and local scanning apps (like scanimage), scanbd / scanbm must be running. Please read 0.1) solution from the README.txt: scanbm acts as a proxy for saned. In that case, the genesys backend was immediately chosen. What else can I try? The below log shows, that scanbd recognizes the scanner and his options. So now you have to figure out which buttons correlate to which option value changes: just press a button and watch the log. Then you can tweak the scripts for the button actions. This is the current status: 1) saned not running + scanbd not running + scanimage -L -- scanner found 2) saned not running + scanbd running + manually running scanbm -- the logs show scanbd is interrupted for a short moment 3) saned not running + scanbd running + scanimage -L -- scanner *not* found Why is case #3 not working? -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130822/42a51c95/attachment-0001.html
[sane-devel] scanbd with old udev version
Am 22.08.2013 08:58, schrieb Sander Devrieze: 2013/8/22 Wilhelm wilhelm.meier at fh-kl.de mailto:wilhelm.meier at fh-kl.de Am 21.08.2013 23:27, schrieb Sander Devrieze: 2013/8/21 Wilhelm wilhelm.meier at fh-kl.de mailto:wilhelm.meier at fh-kl.de mailto:wilhelm.meier at fh-kl.de mailto:wilhelm.meier at fh-kl.de__ Am 21.08.2013 16:04, schrieb Sander Devrieze: 2013/8/21 Wilhelm wilhelm.meier at fh-kl.de mailto:wilhelm.meier at fh-kl.de mailto:wilhelm.meier at fh-kl.de mailto:wilhelm.meier at fh-kl.de__ mailto:wilhelm.meier at fh-kl.de mailto:wilhelm.meier at fh-kl.de mailto:wilhelm.meier at fh-kl.de mailto:wilhelm.meier at fh-kl.de__ snip Mmh, looks good. So, if scanimage finds the scanner (started with the uid/gid as in scanbd.conf), scanbd should find it too, if started as root and the env-var SANE_CONFIG_DIR set. Scanimage does not find the scanner right now. It did only find the scanner when not using the net backend os sane. That's ok. For a desktop machine using scanbd and local scanning apps (like scanimage), scanbd / scanbm must be running. Please read 0.1) solution from the README.txt: scanbm acts as a proxy for saned. In that case, the genesys backend was immediately chosen. What else can I try? The below log shows, that scanbd recognizes the scanner and his options. So now you have to figure out which buttons correlate to which option value changes: just press a button and watch the log. Then you can tweak the scripts for the button actions. This is the current status: 1) saned not running + scanbd not running + scanimage -L -- scanner found this is not intended to work: scanimage should use the net backend and if saned isn't running it shouldn't work 2) saned not running + scanbd running + manually running scanbm -- the logs show scanbd is interrupted for a short moment ok 3) saned not running + scanbd running + scanimage -L -- scanner *not* found Why is case #3 not working? Presumably, scanimage is using the wrong dll.conf. -- Wilhelm w.meier at unix.net
[sane-devel] scanbd with old udev version
2013/8/22 Wilhelm wilhelm.meier at fh-kl.de Am 22.08.2013 08:58, schrieb Sander Devrieze: 2013/8/22 Wilhelm wilhelm.meier at fh-kl.de mailto:wilhelm.meier at fh-kl.de* * This is the current status: 1) saned not running + scanbd not running + scanimage -L -- scanner found this is not intended to work: scanimage should use the net backend and if saned isn't running it shouldn't work 2) saned not running + scanbd running + manually running scanbm -- the logs show scanbd is interrupted for a short moment ok 3) saned not running + scanbd running + scanimage -L -- scanner *not* found Why is case #3 not working? Presumably, scanimage is using the wrong dll.conf. How can I check this? -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130822/724fe20d/attachment.html
[sane-devel] scanbd with old udev version
2013/8/22 Wilhelm wilhelm.meier at fh-kl.de Am 22.08.2013 08:58, schrieb Sander Devrieze: snip This is the current status: 1) saned not running + scanbd not running + scanimage -L -- scanner found this is not intended to work: scanimage should use the net backend and if saned isn't running it shouldn't work 2) saned not running + scanbd running + manually running scanbm -- the logs show scanbd is interrupted for a short moment ok 3) saned not running + scanbd running + scanimage -L -- scanner *not* found Why is case #3 not working? Presumably, scanimage is using the wrong dll.conf. I got a bit further this evening: 1) saned not running + /usr/local/sbin/scanbm sleep 1 SANE_CONFIG_DIR=/usr/local/etc/scanbd/ scanimage -L -- found 2) saned not running +/usr/local/sbin/scanbm sleep 1 scanimage -L -- not found 3) saned running + scanimage -L -- not found 4) saned running + SANE_CONFIG_DIR=/usr/local/etc/scanbd/ scanimage -L -- found What to try next? Please note I also still getting this error as in the beginning: libudev: udev_monitor_enable_receiving: bind failed: Operation not permitted /usr/local/sbin/scanbd: Can't enable udev receiving /usr/local/sbin/scanbd: Can't init udev -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130822/bc845bd0/attachment.html
[sane-devel] scanbd with old udev version
Hello, I am trying to convert a WD MyBook into a scanner server. Sane detects the scanner and I was able to scan, but I cannot get scanbd to work. May this be related to the fact that I am using a *very* old udev version (0.125-7+lenny3) which cannot be upgraded? Check the debug output below. How can I get scanbd running on my system? Thanks for helping me out! /usr/local/sbin/scanbd: foreground /usr/local/sbin/scanbd: config-file: /usr/local/etc/scanbd/scanbd.conf /usr/local/sbin/scanbd: reading config file /usr/local/etc/scanbd/scanbd.conf /usr/local/sbin/scanbd: debug on: level: 7 /usr/local/sbin/scanbd: dropping privs to uid saned /usr/local/sbin/scanbd: dropping privs to gid saned /usr/local/sbin/scanbd: drop privileges to gid: 109 /usr/local/sbin/scanbd: Running as effective gid 109 /usr/local/sbin/scanbd: drop privileges to uid: 104 /usr/local/sbin/scanbd: Running as effective uid 104 /usr/local/sbin/scanbd: dbus_init /usr/local/sbin/scanbd: dbus match type='signal',interface='org.freedesktop.Hal.Manager' /usr/local/sbin/scanbd: sane version 1.0 /usr/local/sbin/scanbd: Scanning for local-only devices /usr/local/sbin/scanbd: start_sane_threads /usr/local/sbin/scanbd: start dbus thread /usr/local/sbin/scanbd: timeout: 500 ms /usr/local/sbin/scanbd: Iteration on dbus call /usr/local/sbin/scanbd: udev init /usr/local/sbin/scanbd: get udev monitor libudev: udev_monitor_enable_receiving: bind failed: Operation not permitted /usr/local/sbin/scanbd: Can't enable udev receiving /usr/local/sbin/scanbd: Can't init udev /usr/local/sbin/scanbd: Iteration on dbus call /usr/local/sbin/scanbd: Iteration on dbus call /usr/local/sbin/scanbd: Iteration on dbus call -- Kind Regards, Sander Devrieze -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130821/819f6218/attachment-0001.html
[sane-devel] scanbd with old udev version
Hi Sander, Am 21.08.2013 00:40, schrieb Sander Devrieze: Hello, I am trying to convert a WD MyBook into a scanner server. Sane detects the scanner and I was able to scan, but I cannot get scanbd to work. Which options did you use for configure? May this be related to the fact that I am using a *very* old udev version (0.125-7+lenny3) which cannot be upgraded? On Lenny you should try usind hal instead of udev. But this is only resonsible for detecting removable devices. As a fallback scanbd can be signaled (using some udev-rule, e.g.), please check the docu. Check the debug output below. How can I get scanbd running on my system? First of all scanbd doesn't detect any scanner. There may be various reasons. But most likely scanbd uses a wrong dll.conf. Did you export SANE_CONFIG_DIR=/usr/local/etc/scanbd ? please show your configs: /etc/sane/dll.conf /usr/local/sbin/scanbd/dll.conf /usr/local/etc/scanbd/scanbd.conf and show the env-vars for the user starting the scanbd (root). Thanks for helping me out! /usr/local/sbin/scanbd: foreground /usr/local/sbin/scanbd: config-file: /usr/local/etc/scanbd/scanbd.conf /usr/local/sbin/scanbd: reading config file /usr/local/etc/scanbd/scanbd.conf /usr/local/sbin/scanbd: debug on: level: 7 /usr/local/sbin/scanbd: dropping privs to uid saned /usr/local/sbin/scanbd: dropping privs to gid saned /usr/local/sbin/scanbd: drop privileges to gid: 109 /usr/local/sbin/scanbd: Running as effective gid 109 /usr/local/sbin/scanbd: drop privileges to uid: 104 /usr/local/sbin/scanbd: Running as effective uid 104 /usr/local/sbin/scanbd: dbus_init /usr/local/sbin/scanbd: dbus match type='signal',interface='org.freedesktop.Hal.Manager' /usr/local/sbin/scanbd: sane version 1.0 /usr/local/sbin/scanbd: Scanning for local-only devices /usr/local/sbin/scanbd: start_sane_threads /usr/local/sbin/scanbd: start dbus thread /usr/local/sbin/scanbd: timeout: 500 ms /usr/local/sbin/scanbd: Iteration on dbus call /usr/local/sbin/scanbd: udev init /usr/local/sbin/scanbd: get udev monitor libudev: udev_monitor_enable_receiving: bind failed: Operation not permitted /usr/local/sbin/scanbd: Can't enable udev receiving /usr/local/sbin/scanbd: Can't init udev /usr/local/sbin/scanbd: Iteration on dbus call /usr/local/sbin/scanbd: Iteration on dbus call /usr/local/sbin/scanbd: Iteration on dbus call -- Kind Regards, Sander Devrieze -- Wilhelm w.meier at unix.net
[sane-devel] scanbd with old udev version
2013/8/21 Wilhelm wilhelm.meier at fh-kl.de
Hi Sander,
Am 21.08.2013 00:40, schrieb Sander Devrieze:
Hello,
I am trying to convert a WD MyBook into a scanner server. Sane detects
the scanner and I was able to scan, but I cannot get scanbd to work.
Which options did you use for configure?
None, I just did a plain ./configure.
May this be related to the fact that I am using a *very* old udev
version (0.125-7+lenny3) which cannot be upgraded?
On Lenny you should try usind hal instead of udev. But this is only
resonsible for detecting removable devices. As a fallback scanbd can be
signaled (using some udev-rule, e.g.), please check the docu.
I am running Debian Squeeze. Only the udev package is from Lenny. This is
needed because otherwise the special MyBook Linux kernel will not boot.
Check the debug
output below. How can I get scanbd running on my system?
First of all scanbd doesn't detect any scanner. There may be various
reasons. But most likely scanbd uses a wrong dll.conf.
Did you
export SANE_CONFIG_DIR=/usr/local/etc/scanbd ?
Yes, and I also run scanbd like this to be sure:
/usr/local/sbin/scanbd -d7 -f -c /usr/local/etc/scanbd/scanbd.conf
When running scanbm, one of the lines reads like this:
scanbm: Setting environment: SANE_CONFIG_DIR=/usr/local/etc/scanbd/sane.d
please show your configs:
/etc/sane/dll.conf
# /etc/sane.d/dll.conf - Configuration file for the SANE dynamic backend
loader
#
# Backends can also be enabled by configuration snippets under
# /etc/sane.d/dll.d directory -- packages providing backends should drop
# a config file similar to dll.conf in this directory, named after the
package.
#
# The next line enables the network backend; comment it out if you don't
need
# to use a remote SANE scanner over the network - see sane-net(5) and
saned(8)
net
#abaton
#agfafocus
#apple
snip all lines commented out below this
/usr/local/sbin/scanbd/dll.**conf
Ok, that seems to help. Maybe the readme file should be more clear that you
need to copy the config files and not the directory sane.d in here.
scanbd seems to work. However, sane does not recognize the scanner:
scanimage: no SANE devices found
Any idea what can be wrong?
/usr/local/etc/scanbd/scanbd.**conf
# global settings
global {
# turn on debugging
# log to console
debug = true
# debug logging
# 1=error, 2=warn, 3=info, 4-7=debug
debug-level = 7
# drop priviliges to this user
#=
# Linux:
# user= saned # root
# *BSD
# user= root
user= saned
# Group to be used
#=
# Linux (most distributions use the lp group to access scanners)
# group = lp
# ArchLinux (ArchLinux uses the scanner group)
# group = scanner
#
# *BSD (no group lp here, use daemon instead)
# group = daemon # root
#
group = saned
# the saned executable for manager-mode
saned = /usr/sbin/saned
saned_opt = {} # string-list
saned_env = { SANE_CONFIG_DIR=/usr/local/etc/scanbd } # list of
environment vars for saned
# Scriptdir specifies where scanbs normally looks for scripts.
# The scriptdir option can be defined as:
# - a path relative to the configuations (path/etc/scanbd)
directory
# - an abosolute path
# Examples:
# scriptdir = scripts
# sets scriptdir to path/etc/scripts.
# scriptdir = /some/path
# sets scriptdir to the specified absolute path
# Default scriptdir is path/etc/scanbd, this is normally
appropriate
# scriptdir =
# scanbuttond_backends_dir sets the path where scanbd looks for the
scanbuttond backends
# It can be defined as relative path, starting from the scanbd
config directory or
# as an absolute path
# Default is libdir/scanbd/scanbutond/backends
# Example
# scanbuttond_backends_dir =
/usr/local/lib/scanbd/scanbuttond/backends
# poll timeout in [ms]
# (for polling the devices)
timeout = 500
pidfile = /var/run/scanbd.pid
# env-vars for the scripts
environment {
# pass the device label as below in this env-var
device = SCANBD_DEVICE
# pass the action label as below in this env-var
action = SCANBD_ACTION
}
# function definitions
# values of the options are simply passed via env-vars
function function_knob {
filter = ^message.*
desc = The value of the function knob / wheel / selector
env= SCANBD_FUNCTION
}
function function_mode {
filter = ^mode.*
desc = Color mode
env= SCANBD_FUNCTION_MODE
}
[sane-devel] scanbd with old udev version
Am 21.08.2013 07:56, schrieb Sander Devrieze:
2013/8/21 Wilhelm wilhelm.meier at fh-kl.de mailto:wilhelm.meier at
fh-kl.de
Hi Sander,
Am 21.08.2013 00:40, schrieb Sander Devrieze:
Hello,
I am trying to convert a WD MyBook into a scanner server. Sane
detects
the scanner and I was able to scan, but I cannot get scanbd to work.
Which options did you use for configure?
None, I just did a plain ./configure.
May this be related to the fact that I am using a *very* old udev
version (0.125-7+lenny3) which cannot be upgraded?
On Lenny you should try usind hal instead of udev. But this is only
resonsible for detecting removable devices. As a fallback scanbd can
be signaled (using some udev-rule, e.g.), please check the docu.
I am running Debian Squeeze. Only the udev package is from Lenny. This
is needed because otherwise the special MyBook Linux kernel will not boot.
Check the debug
output below. How can I get scanbd running on my system?
First of all scanbd doesn't detect any scanner. There may be various
reasons. But most likely scanbd uses a wrong dll.conf.
Did you
export SANE_CONFIG_DIR=/usr/local/etc/scanbd ?
Yes, and I also run scanbd like this to be sure:
/usr/local/sbin/scanbd -d7 -f -c /usr/local/etc/scanbd/scanbd.conf
When running scanbm, one of the lines reads like this:
scanbm: Setting environment: SANE_CONFIG_DIR=/usr/local/etc/scanbd/sane.d
please show your configs:
/etc/sane/dll.conf
# /etc/sane.d/dll.conf - Configuration file for the SANE dynamic backend
loader
#
# Backends can also be enabled by configuration snippets under
# /etc/sane.d/dll.d directory -- packages providing backends should drop
# a config file similar to dll.conf in this directory, named after the
package.
#
# The next line enables the network backend; comment it out if you don't
need
# to use a remote SANE scanner over the network - see sane-net(5) and
saned(8)
net
#abaton
#agfafocus
#apple
snip all lines commented out below this
/usr/local/sbin/scanbd/dll.__conf
what is the contents of this file?
Ok, that seems to help. Maybe the readme file should be more clear that
you need to copy the config files and not the directory sane.d in
here. scanbd seems to work. However, sane does not recognize the scanner:
scanimage: no SANE devices found
Any idea what can be wrong?
/usr/local/etc/scanbd/scanbd.__conf
# global settings
global {
# turn on debugging
# log to console
debug = true
# debug logging
# 1=error, 2=warn, 3=info, 4-7=debug
debug-level = 7
# drop priviliges to this user
#=
# Linux:
# user= saned # root
# *BSD
# user= root
user= saned
# Group to be used
#=
# Linux (most distributions use the lp group to access scanners)
# group = lp
# ArchLinux (ArchLinux uses the scanner group)
# group = scanner
#
# *BSD (no group lp here, use daemon instead)
# group = daemon # root
#
group = saned
# the saned executable for manager-mode
saned = /usr/sbin/saned
saned_opt = {} # string-list
saned_env = { SANE_CONFIG_DIR=/usr/local/etc/scanbd } # list
of environment vars for saned
# Scriptdir specifies where scanbs normally looks for scripts.
# The scriptdir option can be defined as:
# - a path relative to the configuations (path/etc/scanbd)
directory
# - an abosolute path
# Examples:
# scriptdir = scripts
# sets scriptdir to path/etc/scripts.
# scriptdir = /some/path
# sets scriptdir to the specified absolute path
# Default scriptdir is path/etc/scanbd, this is normally
appropriate
# scriptdir =
# scanbuttond_backends_dir sets the path where scanbd looks for
the scanbuttond backends
# It can be defined as relative path, starting from the scanbd
config directory or
# as an absolute path
# Default is libdir/scanbd/scanbutond/backends
# Example
# scanbuttond_backends_dir =
/usr/local/lib/scanbd/scanbuttond/backends
# poll timeout in [ms]
# (for polling the devices)
timeout = 500
pidfile = /var/run/scanbd.pid
# env-vars for the scripts
environment {
# pass the device label as below in this env-var
device = SCANBD_DEVICE
# pass the action label as below in this env-var
action = SCANBD_ACTION
}
# function definitions
# values of the options are
[sane-devel] scanbd with old udev version
2013/8/21 Wilhelm wilhelm.meier at fh-kl.de
snip
/usr/local/sbin/scanbd/dll.__**conf
what is the contents of this file?
The directory /usr/local/sbin/scanbd does not exist. I think you mean
/usr/local/etc/scanbd. These are the items in that directory:
abaton.conf bh.conf coolscan3.conf dll.d
genesys.conf hp.conf ma1509.confmustek_usb.conf
plustek_pp.conf scanbd.conf st400.conftest.script
action.script canon630u.conf coolscan.conf dmc.conf
geniusvp2.conf hpsj5s.conf magicolor.confnec.conf qcam.conf
scanner.d stv680.confu12.conf
agfafocus.conf canon.conf dc210.conf epjitsu.conf
gphoto2.conf hs2p.conf matsushita.confnet.conf
ricoh.conf sceptre.conf tamarack.confumax1220u.conf
apple.conf canon_dr.conf dc240.conf epson2.conf
gt68xx.conf ibm.conf microtek2.confp5.conf
rts8891.conf sharp.conf teco1.confumax.conf
artec.conf canon_pp.conf dc25.conf epson.conf
hp3900.conf kodak.confmicrotek.confpie.conf s9036.conf
sm3840.conf teco2.confumax_pp.conf
artec_eplus48u.conf cardscan.conf dell1600n_net.conf example.script
hp4200.conf leo.conf mustek.confpixma.conf saned.conf
snapscan.conf teco3.confv4l.conf
avision.conf coolscan2.conf dll.conf fujitsu.conf
hp5400.conf lexmark.conf mustek_pp.confplustek.conf
scanadf.script sp15c.conf test.confxerox_mfp.conf
Which one do you need to see? I already showed you dll.conf.
Ok, that seems to help. Maybe the readme file should be more clear that
you need to copy the config files and not the directory sane.d in
here. scanbd seems to work. However, sane does not recognize the scanner:
scanimage: no SANE devices found
Any idea what can be wrong?
/usr/local/etc/scanbd/scanbd._**_conf
This file does not exist. I only have /usr/local/etc/scanbd/scanbd.conf as
shown in my previous mail:
# global settings
global {
# turn on debugging
# log to console
debug = true
# debug logging
# 1=error, 2=warn, 3=info, 4-7=debug
debug-level = 7
# drop priviliges to this user
#=
# Linux:
# user= saned # root
# *BSD
# user= root
user= saned
# Group to be used
#=
# Linux (most distributions use the lp group to access scanners)
# group = lp
# ArchLinux (ArchLinux uses the scanner group)
# group = scanner
#
# *BSD (no group lp here, use daemon instead)
# group = daemon # root
#
group = saned
# the saned executable for manager-mode
saned = /usr/sbin/saned
saned_opt = {} # string-list
saned_env = { SANE_CONFIG_DIR=/usr/local/**etc/scanbd } #
list
of environment vars for saned
# Scriptdir specifies where scanbs normally looks for scripts.
# The scriptdir option can be defined as:
# - a path relative to the configuations (path/etc/scanbd)
directory
# - an abosolute path
# Examples:
# scriptdir = scripts
# sets scriptdir to path/etc/scripts.
# scriptdir = /some/path
# sets scriptdir to the specified absolute path
# Default scriptdir is path/etc/scanbd, this is normally
appropriate
# scriptdir =
# scanbuttond_backends_dir sets the path where scanbd looks for
the scanbuttond backends
# It can be defined as relative path, starting from the scanbd
config directory or
# as an absolute path
# Default is libdir/scanbd/scanbutond/**backends
# Example
# scanbuttond_backends_dir =
/usr/local/lib/scanbd/**scanbuttond/backends
# poll timeout in [ms]
# (for polling the devices)
timeout = 500
pidfile = /var/run/scanbd.pid
# env-vars for the scripts
environment {
# pass the device label as below in this env-var
device = SCANBD_DEVICE
# pass the action label as below in this env-var
action = SCANBD_ACTION
}
# function definitions
# values of the options are simply passed via env-vars
function function_knob {
filter = ^message.*
desc = The value of the function knob / wheel /
selector
env= SCANBD_FUNCTION
}
function function_mode {
filter = ^mode.*
desc = Color mode
env= SCANBD_FUNCTION_MODE
}
multiple_actions = true # allow multiple actions per option
[sane-devel] scanbd with old udev version
Am 21.08.2013 12:19, schrieb Sander Devrieze:
2013/8/21 Wilhelm wilhelm.meier at fh-kl.de mailto:wilhelm.meier at
fh-kl.de
snip
/usr/local/sbin/scanbd/dll.conf
what is the contents of this file?
The directory /usr/local/sbin/scanbd does not exist. I think you mean
/usr/local/etc/scanbd.
Sorry, yes.
So please show:
/etc/sane.d/dll.conf
and
/usr/local/etc/scanbd/dll.conf
or whatever dir SANE_CONFIG_DIR points to.
Please see section: 6) sane config, form the README.txt.
These are the items in that directory:
abaton.conf bh.conf coolscan3.conf dll.d
genesys.conf hp.conf ma1509.confmustek_usb.conf
plustek_pp.conf scanbd.conf st400.conftest.script
action.script canon630u.conf coolscan.conf dmc.conf
geniusvp2.conf hpsj5s.conf magicolor.confnec.conf
qcam.conf scanner.d stv680.confu12.conf
agfafocus.conf canon.conf dc210.conf
epjitsu.conf gphoto2.conf hs2p.conf matsushita.conf
net.conf ricoh.conf sceptre.conf tamarack.conf
umax1220u.conf
apple.conf canon_dr.conf dc240.conf epson2.conf
gt68xx.conf ibm.conf microtek2.confp5.conf
rts8891.conf sharp.conf teco1.confumax.conf
artec.conf canon_pp.conf dc25.conf epson.conf
hp3900.conf kodak.confmicrotek.confpie.conf
s9036.conf sm3840.conf teco2.confumax_pp.conf
artec_eplus48u.conf cardscan.conf dell1600n_net.conf example.script
hp4200.conf leo.conf mustek.confpixma.conf
saned.conf snapscan.conf teco3.confv4l.conf
avision.conf coolscan2.conf dll.conf fujitsu.conf
hp5400.conf lexmark.conf mustek_pp.confplustek.conf
scanadf.script sp15c.conf test.confxerox_mfp.conf
Which one do you need to see? I already showed you dll.conf.
Ok, that seems to help. Maybe the readme file should be more
clear that
you need to copy the config files and not the directory sane.d in
here. scanbd seems to work. However, sane does not recognize the
scanner:
scanimage: no SANE devices found
Any idea what can be wrong?
/usr/local/etc/scanbd/scanbd.conf
This file does not exist. I only have /usr/local/etc/scanbd/scanbd.conf
as shown in my previous mail:
# global settings
global {
# turn on debugging
# log to console
debug = true
# debug logging
# 1=error, 2=warn, 3=info, 4-7=debug
debug-level = 7
# drop priviliges to this user
#=
# Linux:
# user= saned # root
# *BSD
# user= root
user= saned
# Group to be used
#=
# Linux (most distributions use the lp group to access
scanners)
# group = lp
# ArchLinux (ArchLinux uses the scanner group)
# group = scanner
#
# *BSD (no group lp here, use daemon instead)
# group = daemon # root
#
group = saned
# the saned executable for manager-mode
saned = /usr/sbin/saned
saned_opt = {} # string-list
saned_env = {
SANE_CONFIG_DIR=/usr/local/__etc/scanbd } # list
of environment vars for saned
# Scriptdir specifies where scanbs normally looks for
scripts.
# The scriptdir option can be defined as:
# - a path relative to the configuations
(path/etc/scanbd)
directory
# - an abosolute path
# Examples:
# scriptdir = scripts
# sets scriptdir to path/etc/scripts.
# scriptdir = /some/path
# sets scriptdir to the specified absolute path
# Default scriptdir is path/etc/scanbd, this is normally
appropriate
# scriptdir =
# scanbuttond_backends_dir sets the path where scanbd
looks for
the scanbuttond backends
# It can be defined as relative path, starting from
the scanbd
config directory or
# as an absolute path
# Default is libdir/scanbd/scanbutond/__backends
# Example
# scanbuttond_backends_dir =
/usr/local/lib/scanbd/__scanbuttond/backends
# poll timeout in [ms]
[sane-devel] scanbd with old udev version
2013/8/21 Wilhelm wilhelm.meier at fh-kl.de Am 21.08.2013 12:19, schrieb Sander Devrieze: 2013/8/21 Wilhelm wilhelm.meier at fh-kl.de mailto:wilhelm.meier at fh-kl.de* * snip /usr/local/sbin/scanbd/dll.___**_conf what is the contents of this file? The directory /usr/local/sbin/scanbd does not exist. I think you mean /usr/local/etc/scanbd. Sorry, yes. So please show: /etc/sane.d/dll.conf # /etc/sane.d/dll.conf - Configuration file for the SANE dynamic backend loader # # Backends can also be enabled by configuration snippets under # /etc/sane.d/dll.d directory -- packages providing backends should drop # a config file similar to dll.conf in this directory, named after the package. # # The next line enables the network backend; comment it out if you don't need # to use a remote SANE scanner over the network - see sane-net(5) and saned(8) net #abaton snip commented out backends #microtek and /usr/local/etc/scanbd/dll.conf or whatever dir SANE_CONFIG_DIR points to. # /etc/sane.d/dll.conf - Configuration file for the SANE dynamic backend loader # # Backends can also be enabled by configuration snippets under # /etc/sane.d/dll.d directory -- packages providing backends should drop # a config file similar to dll.conf in this directory, named after the package. # # The next line enables the network backend; comment it out if you don't need # to use a remote SANE scanner over the network - see sane-net(5) and saned(8) #net abaton agfafocus apple avision artec artec_eplus48u as6e bh canon canon630u canon_dr #canon_pp cardscan coolscan #coolscan2 coolscan3 #dc25 #dc210 #dc240 dell1600n_net dmc epjitsu #epson epson2 fujitsu #gphoto2 genesys gt68xx hp hp3900 hpsj5s hp3500 hp4200 hp5400 hp5590 hpljm1005 and so forth snip -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130821/07c9fb53/attachment.html
[sane-devel] scanbd with old udev version
Am 21.08.2013 16:04, schrieb Sander Devrieze: 2013/8/21 Wilhelm wilhelm.meier at fh-kl.de mailto:wilhelm.meier at fh-kl.de Am 21.08.2013 12:19, schrieb Sander Devrieze: 2013/8/21 Wilhelm wilhelm.meier at fh-kl.de mailto:wilhelm.meier at fh-kl.de mailto:wilhelm.meier at fh-kl.de mailto:wilhelm.meier at fh-kl.de__ snip /usr/local/sbin/scanbd/dll.__conf what is the contents of this file? The directory /usr/local/sbin/scanbd does not exist. I think you mean /usr/local/etc/scanbd. Sorry, yes. So please show: /etc/sane.d/dll.conf # /etc/sane.d/dll.conf - Configuration file for the SANE dynamic backend loader # # Backends can also be enabled by configuration snippets under # /etc/sane.d/dll.d directory -- packages providing backends should drop # a config file similar to dll.conf in this directory, named after the package. # # The next line enables the network backend; comment it out if you don't need # to use a remote SANE scanner over the network - see sane-net(5) and saned(8) net #abaton snip commented out backends #microtek and /usr/local/etc/scanbd/dll.conf or whatever dir SANE_CONFIG_DIR points to. # /etc/sane.d/dll.conf - Configuration file for the SANE dynamic backend loader # # Backends can also be enabled by configuration snippets under # /etc/sane.d/dll.d directory -- packages providing backends should drop # a config file similar to dll.conf in this directory, named after the package. # # The next line enables the network backend; comment it out if you don't need # to use a remote SANE scanner over the network - see sane-net(5) and saned(8) #net abaton agfafocus apple avision artec artec_eplus48u as6e bh canon canon630u canon_dr #canon_pp cardscan coolscan #coolscan2 coolscan3 #dc25 #dc210 #dc240 dell1600n_net dmc epjitsu #epson epson2 fujitsu #gphoto2 genesys gt68xx hp hp3900 hpsj5s hp3500 hp4200 hp5400 hp5590 hpljm1005 and so forth Mmh, looks good. So, if scanimage finds the scanner (started with the uid/gid as in scanbd.conf), scanbd should find it too, if started as root and the env-var SANE_CONFIG_DIR set. -- Wilhelm w.meier at unix.net
