[sane-devel] scanbd with old udev version

[Sander Devrieze]

2013/8/21 Wilhelm 

> Am 21.08.2013 16:04, schrieb Sander Devrieze:
>
>> 2013/8/21 Wilhelm mailto:wilhelm.meier at 
>> fh-kl.de>
>>
>



> 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] [sane-pixma] Canon MF4150 v. PIXMA_CAP_LINEART

[Rolf Bensch]

Hi Samuel,

I prepared a quick patch to implement lineart for imageclass scanners.

To use this patch you must install SANE from git, as described here:
http://www.sane-project.org/README.linux

and

patch pixma_imageclass.c with the attached file ('patch
pixma_imageclass.c pixma_imageclass.c.diff1').

If you only need the Pixma backend you can reduce compiling time with
'./configure BACKENDS=pixma'.

The patch can be buggy. If so, I need all debug output from scanimage
enabled with 'export SANE_DEBUG_PIXMA=4'.

Cheers,
Rolf


Am 20.08.2013 15:36, schrieb Samuel Adam:
> I know experientially that the Canon imageCLASS MF4150 is possessed of
> a 1-bpp lineart mode.  Pages fly through the automatic feeder, and
> text is accorded an OCR-friendly crispiness lacking in the greyscale
> mode.  The Canon-provided Windows-only software provides two modes it
> respectively terms "Black and White" (not too good) and "Black and
> White Text" (much better).[1]  I do not currently have a Windows
> machine available, and I need to make some scans *yesterday*.
>
> sane-pixma permits only --mode Color or --mode Gray with the MF4150,
> and `scanimage -A` shows only these options.
>
> What would happen if I simply ORed in PIXMA_CAP_LINEART at the
> appropriate line in pixma_imageclass.c?
>
> -   DEV ("Canon imageCLASS MF4150", "MF4100", MF4100_PID, 600, 640,
> 877, PIXMA_CAP_ADF),
> +   DEV ("Canon imageCLASS MF4150", "MF4100", MF4100_PID, 600, 640,
> 877, PIXMA_CAP_ADF | PIXMA_CAP_LINEART),
>
> I expect this would lead to Bad Things, what with all the moving parts
> I skimmed past.  But is any other way to make it work right quickly?
>
> Sorry to return ENOTIME on the project to actually familiarize myself
> with sane-pixma code, beyond a simple grep.  And thanks to the folks
> who reverse-engineered the Canon protocols, so I can use scanner at all.
>
> Samuel Adam
>
>
> [1] The idiot-friendly software has a checkbox captioned "Show Scanner
> Driver".  Check it, and options galore do arise.
>
>
>

-- next part --
--- ./pixma_imageclass.c2013-08-21 21:58:41.0 +0200
+++ ../sane-backends/backend/pixma_imageclass.c 2013-08-21 21:58:46.0 
+0200
@@ -247,7 +247,7 @@
   pixma_set_be32 (mf->raw_width, data + 0x10);
   pixma_set_be32 (s->param->h, data + 0x14);
   data[0x18] = (s->param->channels == 1) ? 0x04 : 0x08;
-  data[0x19] = s->param->channels * s->param->depth;   /* bits per pixel */
+  data[0x19] = s->param->channels * ((s->param->software_lineart) ? 8 : 
s->param->depth);  /* bits per pixel */
   data[0x1f] = 0x7f;
   data[0x20] = 0xff;
   data[0x23] = 0x81;
@@ -499,8 +499,36 @@
 {
   UNUSED (s);
 
+  PDBG (pixma_dbg (4, "*iclass_check_param* Initially: channels=%u, 
depth=%u, x=%u, y=%u, w=%u, line_size=%u , h=%u*\n",
+   sp->channels, sp->depth, sp->x, sp->y, sp->w, 
sp->line_size, sp->h));
+
   sp->depth = 8;
+  sp->software_lineart = 0;
+  if (s->param->mode == PIXMA_SCAN_MODE_LINEART)
+  {
+sp->software_lineart = 1;
+sp->channels = 1;
+sp->depth = 1;
+  }
+
+  /* for software lineart w must be a multiple of 8 */
+  if (sp->software_lineart == 1 && sp->w % 8)
+  {
+unsigned w_max;
+
+sp->w += 8 - (sp->w % 8);
+
+/* do not exceed the scanner capability */
+w_max = s->cfg->width * s->cfg->xdpi / 75;
+w_max -= w_max % 8;
+if (sp->w > w_max)
+  sp->w = w_max;
+  }
   sp->line_size = ALIGN_SUP (sp->w, 32) * sp->channels;
+
+  PDBG (pixma_dbg (4, "*iclass_check_param* Finally: channels=%u, 
depth=%u, x=%u, y=%u, w=%u, line_size=%u , h=%u*\n",
+   sp->channels, sp->depth, sp->x, sp->y, sp->w, 
sp->line_size, sp->h));
+
   return 0;
 }
 
@@ -634,7 +662,23 @@
   n = mf->blk_len / s->param->line_size;
   if (n != 0)
 {
-  if (s->param->channels != 1 &&
+  PDBG (pixma_dbg (4, "*iclass_fill_buffer* Processing with n=%u, 
w=%i, line_size=%u, raw_width=%u * \n",
+   n, s->param->w, s->param->line_size, 
mf->raw_width));
+
+  /* gray to lineart convert */
+  if (s->param->mode == PIXMA_SCAN_MODE_LINEART)
+  {
+int i;
+uint8_t *sptr, *dptr;
+
+sptr = mf->blkptr;
+dptr = mf->lineptr;
+
+/* process ALL lines */
+for (i = 0; i < n; i++, sptr += s->param->line_size, dptr += 
(s->param->line_size / 8))
+  pixma_binarize_line (s->param, dptr, sptr, s->param->line_size, 
1);
+  }
+  else if (s->param->channels != 1 &&
   s->cfg->pid != MF3010_PID &&
   s->cfg->pid != MF4410_PID &&
  s->cfg->pid != MF4550_PID &&
@@ -752,6 +796,7 @@
 0, 0, /* adftpu_min_dpi & adftpu_max_dpi not 
used in this subdriver */ \
 0, 0, /* tpuir_min_dpi & tpuir_max_dpi not 
used in this subdriver */   \
 w, h,   

[sane-devel] libsane-problem?

[Betreuungsbüro Jenetzky]

Sorry for being late.
I had been out of office until tonight.

Am 19.08.2013 03:03, schrieb Olaf Meeuwissen:
> Can you provide debug logs obtained using scanimage?
>
>$ SANE_DEBUG_EPKOWA=HEX scanimage --device=epkowa:interpreter:002:004 
> --help 2> gt-1500.log
Here we go.
Attached is the output file.

Sorry, if there are no binairies wanted here, I could also post the 
output, if desired.

Regards

-jj-
-- 
Betreuungsb?ro J?rg Jenetzky
Postfach 500 640 * 22706 Hamburg
Telefon: 040 - 55 77 35 50
Telefax: 040 - 55 77 35 51
B?rozeiten MO, MI, FR, 10.00 - 14.00 Uhr
-- next part --
A non-text attachment was scrubbed...
Name: 20130821_gt-1500.log
Type: text/x-log
Size: 150770 bytes
Desc: not available
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130821/e65060f5/attachment-0001.bin>

[sane-devel] scanbd with old udev version

[Wilhelm]

Am 21.08.2013 16:04, schrieb Sander Devrieze:
> 2013/8/21 Wilhelm mailto:wilhelm.meier at 
> fh-kl.de>>
>
> Am 21.08.2013 12:19, schrieb Sander Devrieze:
>
> 2013/8/21 Wilhelm    __>>
>
>  
>
>
>   /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
> 
> #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
> 

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

[sane-devel] scanbd problem with dbus permission ?

[Michael Markusch]

Hi Wilhelm,

I figured out the problem: it's about the permissions. It seems to be
this issue:

http://sane.10972.n7.nabble.com/scanbd-works-but-not-buttons-td16867.html

- edit scanbd.conf user = root, group = root
- login as root, sudo su
- export SANE_CONFIG_DIR=/usr/local/etc/scanbd
- /usr/local/sbin/scanbd -d -f -c /usr/local/etc/scanbd/scanbd.conf

Now I see the debug output and the pressed buttons.

Thanks,
Michael

Am 20.08.2013 20:54, schrieb Wilhelm:
> Am 20.08.2013 18:17, schrieb Michael Markusch:
>> Hi Wilhelm,
>>
>> thanks for your answer.
>>
>> I followed your notes but it still does not work.
>
> sad but true ;-)
>
> Looks like scanbd uses the 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).
>
>>
>> - make distclean
>> - ./configure
>> - make
>> - set in /usr/local/sbin/scanbd/dll.confonly "genesys"
>> - sudo /usr/local/sbin/scanbd -d -f -c /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 lp
>>> /usr/local/sbin/scanbd: drop privileges to gid: 7
>>> /usr/local/sbin/scanbd: Running as effective gid 7
>>> /usr/local/sbin/scanbd: drop privileges to uid: 112
>>> /usr/local/sbin/scanbd: Running as effective uid 112
>>> /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: udev init
>>> /usr/local/sbin/scanbd: get udev monitor
>>> /usr/local/sbin/scanbd: timeout: 500 ms
>>> /usr/local/sbin/scanbd: udev fd is non-blocking, now setting to
>>> blocking mode
>>> /usr/local/sbin/scanbd: Iteration on dbus call
>>> /usr/local/sbin/scanbd: start udev thread
>>> /usr/local/sbin/scanbd: udev thread started
>>> /usr/local/sbin/scanbd: Iteration on dbus call
>>> /usr/local/sbin/scanbd: Iteration on dbus call
>>> /usr/local/sbin/scanbd: Iteration on dbus call
>>> /usr/local/sbin/scanbd: Iteration on dbus call
>>> ...
>>
>> What else can I try?
>>
>> Thanks,
>> Michael
>>
>>
>> Am 20.08.2013 07:50, schrieb Wilhelm:
>>> Hi Michael,
>>>
>>> Am 18.08.2013 14:33, schrieb Michael Markusch:
 Hi,

 I tried to install scanbd and I guess that's very easy, but now I
 have a
 permission problem. In the past I use my scanner with sane as
 scanserver
 and everything worked.

 My system:
 Debian Wheezy, Kernel 3.6.11 on Raspberry Pi

 Scanner:
 Canon canoscan lide 35


 Here my installation steps:

 - install libconfuse-dev libsane-dev libudev-dev libusb-dev
 - I use scanbd from SVN
 - ./configure --enable-scanbuttond (no problems)
>>>
>>> why did you enable scanbuttond-drivers. Your scanner should be fully
>>> supported by the sane-backends (and as you said, scanimage is working)
>>>
 - make (no problems)
 - make install (no problems)
 - copy scanbd_dbus.conf to /etc/dbus-1/system.d/
 - install xinetd
 - generate /etc/xinetd.d/sane-port
 - edit /etc/sane.d/dll.conf set only "net"
 - edit /usr/local/etc/scanbd/dll.conf set "#net"
>>>
>>> be sure to include the backend for your scanner
>>>
 - edit /etc/sane.d/net.conf set localhost and connect_timeout = 60
 - copy backends /etc/sane.d/ to /usr/local/etc/scanbd/
 - export SANE_CONFIG_DIR=/usr/local/etc/scanbd
 - /usr/local/sbin/scanbd -d -f -c /usr/local/etc/scanbd/scanbd.conf
 (with problems)

 Log:

> /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 lp
> /usr/local/sbin/scanbd: drop privileges to gid: 7
> /usr/local/sbin/scanbd: Can't set the effective gid to 7
> /usr/local/sbin/scanbd: drop privileges to uid: 112
> /usr/local/sbin/scanbd: Can't set the effective uid to 112
>>>
>>> If you start scanbd as unprivileged user it isn't possible to changed
>>> the euid/egid. Start it as root and it will itself change the euid /
>>> egid to the ones in the config file.
>>>
> /usr/local/sbin/scanbd: dbus_init
> /usr/local/sbin/scanbd: dbus match
> type='signal',interface='org.freedesktop.Hal.Manager'
> /usr/local/sbin/scanbd: Loading
> /usr/local/lib/scanbd/scanbuttond/backends/meta.so
> /usr/local/sbin/scanbd: meta-backend: init
> /usr/local/sbin/scanbd: libusbi: initializing...
> /usr/local/sbin/scanbd: Loading
> /usr/local/lib/scanbd/scanbuttond/backends/hp3500.so
> /usr/local/sbin/scanbd: meta-backend: attaching backend: HP3500 USB

[sane-devel] scanbd with old udev version

[Sander Devrieze]

2013/8/21 Wilhelm 

> Am 21.08.2013 12:19, schrieb Sander Devrieze:
>
>> 2013/8/21 Wilhelm mailto:wilhelm.meier at 
>> fh-kl.de*
>> *>>
>>
>> 
>>
>>
>>  /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

#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



-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130821/07c9fb53/attachment.html>

[sane-devel] scanbd problem with dbus permission ?

[Wilhelm]

Am 20.08.2013 20:54, schrieb Wilhelm:
> Am 20.08.2013 18:17, schrieb Michael Markusch:
>> Hi Wilhelm,
>>
>> thanks for your answer.
>>
>> I followed your notes but it still does not work.
>
> sad but true ;-)
>
> Looks like scanbd uses the 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

Sorry, I meant:

/usr/local/etc/scanbd/dll.conf

> /usr/local/etc/scanbd/scanbd.conf
>
> and show the env-vars for the user starting the scanbd (root).
>
>>
>> - make distclean
>> - ./configure
>> - make
>> - set in /usr/local/sbin/scanbd/dll.confonly "genesys"
>> - sudo /usr/local/sbin/scanbd -d -f -c /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 lp
>>> /usr/local/sbin/scanbd: drop privileges to gid: 7
>>> /usr/local/sbin/scanbd: Running as effective gid 7
>>> /usr/local/sbin/scanbd: drop privileges to uid: 112
>>> /usr/local/sbin/scanbd: Running as effective uid 112
>>> /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: udev init
>>> /usr/local/sbin/scanbd: get udev monitor
>>> /usr/local/sbin/scanbd: timeout: 500 ms
>>> /usr/local/sbin/scanbd: udev fd is non-blocking, now setting to
>>> blocking mode
>>> /usr/local/sbin/scanbd: Iteration on dbus call
>>> /usr/local/sbin/scanbd: start udev thread
>>> /usr/local/sbin/scanbd: udev thread started
>>> /usr/local/sbin/scanbd: Iteration on dbus call
>>> /usr/local/sbin/scanbd: Iteration on dbus call
>>> /usr/local/sbin/scanbd: Iteration on dbus call
>>> /usr/local/sbin/scanbd: Iteration on dbus call
>>> ...
>>
>> What else can I try?
>>
>> Thanks,
>> Michael
>>
>>
>> Am 20.08.2013 07:50, schrieb Wilhelm:
>>> Hi Michael,
>>>
>>> Am 18.08.2013 14:33, schrieb Michael Markusch:
 Hi,

 I tried to install scanbd and I guess that's very easy, but now I
 have a
 permission problem. In the past I use my scanner with sane as
 scanserver
 and everything worked.

 My system:
 Debian Wheezy, Kernel 3.6.11 on Raspberry Pi

 Scanner:
 Canon canoscan lide 35


 Here my installation steps:

 - install libconfuse-dev libsane-dev libudev-dev libusb-dev
 - I use scanbd from SVN
 - ./configure --enable-scanbuttond (no problems)
>>>
>>> why did you enable scanbuttond-drivers. Your scanner should be fully
>>> supported by the sane-backends (and as you said, scanimage is working)
>>>
 - make (no problems)
 - make install (no problems)
 - copy scanbd_dbus.conf to /etc/dbus-1/system.d/
 - install xinetd
 - generate /etc/xinetd.d/sane-port
 - edit /etc/sane.d/dll.conf set only "net"
 - edit /usr/local/etc/scanbd/dll.conf set "#net"
>>>
>>> be sure to include the backend for your scanner
>>>
 - edit /etc/sane.d/net.conf set localhost and connect_timeout = 60
 - copy backends /etc/sane.d/ to /usr/local/etc/scanbd/
 - export SANE_CONFIG_DIR=/usr/local/etc/scanbd
 - /usr/local/sbin/scanbd -d -f -c /usr/local/etc/scanbd/scanbd.conf
 (with problems)

 Log:

> /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 lp
> /usr/local/sbin/scanbd: drop privileges to gid: 7
> /usr/local/sbin/scanbd: Can't set the effective gid to 7
> /usr/local/sbin/scanbd: drop privileges to uid: 112
> /usr/local/sbin/scanbd: Can't set the effective uid to 112
>>>
>>> If you start scanbd as unprivileged user it isn't possible to changed
>>> the euid/egid. Start it as root and it will itself change the euid /
>>> egid to the ones in the config file.
>>>
> /usr/local/sbin/scanbd: dbus_init
> /usr/local/sbin/scanbd: dbus match
> type='signal',interface='org.freedesktop.Hal.Manager'
> /usr/local/sbin/scanbd: Loading
> /usr/local/lib/scanbd/scanbuttond/backends/meta.so
> /usr/local/sbin/scanbd: meta-backend: init
> /usr/local/sbin/scanbd: libusbi: initializing...
> /usr/local/sbin/scanbd: Loading
> /usr/local/lib/scanbd/scanbuttond/backends/hp3500.so
> /usr/local/sbin/scanbd: meta-backend: attaching backend: HP3500 USB
> /usr/local/sbin/scanbd: hp3500-backend: init
> /usr/local/sbin/scanbd: Loading
> /usr/local/lib/scanbd/scanbuttond/backends/snapscan.so
> /usr/local/sbin/scanbd: meta-backend: attaching backend: Snapscan USB
> /usr/local/sbin/scanbd: snapscan-backend: init
> /usr/local/sbin/scanbd: Loading
> /usr/local/lib/scanbd/scanbuttond/backends/niash.so
> 

[sane-devel] scanbd with old udev version

[Wilhelm]

Am 21.08.2013 12:19, schrieb Sander Devrieze:
> 2013/8/21 Wilhelm mailto:wilhelm.meier at 
> fh-kl.de>>
>
> 
>
>
>  /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
> (/etc/scanbd)
> directory
>   #   - an abosolute path
>   # Examples:
>   # scriptdir = scripts
>   # sets scriptdir to /etc/scripts.
>   # scriptdir = /some/path
>   # sets scriptdir to the specified absolute path
>   # Default scriptdir is /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 /scanbd/scanbutond/__backends
>   # Example
>   # scanbuttond_backends_dir =
> "/usr/local/lib/scanbd

[sane-devel] scanbd with old udev version

[Sander Devrieze]

2013/8/21 Wilhelm 

> 
>
>>
>> /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 (/etc/scanbd)
>> directory
>>  #   - an abosolute path
>>  # Examples:
>>  # scriptdir = scripts
>>  # sets scriptdir to /etc/scripts.
>>  # scriptdir = /some/path
>>  # sets scriptdir to the specified absolute path
>>  # Default scriptdir is /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 /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 {
>>  fil

[sane-devel] scanbd with old udev version

[Wilhelm]

Am 21.08.2013 07:56, schrieb Sander Devrieze:
> 2013/8/21 Wilhelm 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
> 
>
> /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 (/etc/scanbd)
> directory
>  #   - an abosolute path
>  # Examples:
>  # scriptdir = scripts
>  # sets scriptdir to /etc/scripts.
>  # scriptdir = /some/path
>  # sets scriptdir to the specified absolute path
>  # Default scriptdir is /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 /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 = "SCA

[sane-devel] scanbd with old udev version

[Sander Devrieze]

2013/8/21 Wilhelm 

> 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




> /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 (/etc/scanbd)
directory
#   - an abosolute path
# Examples:
# scriptdir = scripts
# sets scriptdir to /etc/scripts.
# scriptdir = /some/path
# sets scriptdir to the specified absolute path
# Default scriptdir is /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 /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"
}

multipl

[sane-devel] scanbd with old udev version

[Wilhelm]

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

[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.

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>