On Fri, 2013-04-12 at 07:01 -0700, deigerwutz wrote: > Dear all > > In the meanwhile I removed and installed scanbd once again. > > But now I get an "Iteration on dbus call" error. > > If scanbd runs from command line with option "f" it works perfect but not > with auto start. > If scanbd ist started via rc$.d the "Iteration on dbus call" occurs. > > echo $SANE_CONFIG_DIR results in an empty line. > > The error leaves an entry every second in the syslog file. > > What can be the reason, please help. > > Here ist the syslog from boot: > > Apr 12 15:49:39 raspberrypi scanbd: /usr/local/bin/scanbd: debug on: level: > 7 > Apr 12 15:49:39 raspberrypi scanbd: /usr/local/bin/scanbd: daemonize > Apr 12 15:49:39 raspberrypi scanbd: /usr/local/bin/scanbd: dropping privs to > uid saned > Apr 12 15:49:39 raspberrypi scanbd: /usr/local/bin/scanbd: dropping privs to > gid lp > Apr 12 15:49:39 raspberrypi scanbd: /usr/local/bin/scanbd: drop privileges > to gid: 7 > Apr 12 15:49:39 raspberrypi scanbd: /usr/local/bin/scanbd: Running as > effective gid 7 > Apr 12 15:49:39 raspberrypi scanbd: /usr/local/bin/scanbd: drop privileges > to uid: 107 > Apr 12 15:49:39 raspberrypi scanbd: /usr/local/bin/scanbd: Running as > effective uid 107 > Apr 12 15:49:39 raspberrypi scanbd: /usr/local/bin/scanbd: dbus_init > Apr 12 15:49:39 raspberrypi scanbd: /usr/local/bin/scanbd: dbus match > type='signal',interface='org.freedesktop.Hal.Manager' > Apr 12 15:49:39 raspberrypi scanbd: /usr/local/bin/scanbd: sane version 1.0 > Apr 12 15:49:39 raspberrypi scanbd: /usr/local/bin/scanbd: Scanning for > local-only devices > Apr 12 15:49:39 raspberrypi scanbd: /usr/local/bin/scanbd: > start_sane_threads > Apr 12 15:49:39 raspberrypi scanbd: /usr/local/bin/scanbd: start dbus thread > Apr 12 15:49:39 raspberrypi scanbd: /usr/local/bin/scanbd: timeout: 500 ms > Apr 12 15:49:39 raspberrypi scanbd: /usr/local/bin/scanbd: Iteration on dbus > call > Apr 12 15:49:40 raspberrypi scanbd: /usr/local/bin/scanbd: Iteration on dbus > call > Apr 12 15:49:40 raspberrypi xinetd[1443]: Reading included configuration > file: /etc/xinetd.d/chargen [file=/etc/xinetd.conf] [line=14] > Apr 12 15:49:40 raspberrypi xinetd[1443]: Reading included configuration > file: /etc/xinetd.d/daytime [file=/etc/xinetd.d/daytime] [line=28] > Apr 12 15:49:40 raspberrypi xinetd[1443]: Reading included configuration > file: /etc/xinetd.d/discard [file=/etc/xinetd.d/discard] [line=26] > Apr 12 15:49:40 raspberrypi xinetd[1443]: Reading included configuration > file: /etc/xinetd.d/echo [file=/etc/xinetd.d/echo] [line=25] > Apr 12 15:49:40 raspberrypi xinetd[1443]: Reading included configuration > file: /etc/xinetd.d/sane-port [file=/etc/xinetd.d/sane-port] [line=26] > Apr 12 15:49:40 raspberrypi xinetd[1443]: Reading included configuration > file: /etc/xinetd.d/time [file=/etc/xinetd.d/time] [line=12] > > > > > -- > View this message in context: > http://sane.10972.n7.nabble.com/scanbd-on-Raspberry-Pi-Connection-Failed-system-bus-socket-tp17350p17471.html > Sent from the SANE - Dev mailing list archive at Nabble.com. >
you scanner is not recognised. Did your startup script specify the SANE_CONFIG_DIR? Kind regards, Louis