Thank you for you answer. I will update the package. But perhaps i miss something, how can it be a configuration problem? i'm using the same conf file with systemd (not working) and with command line (working).
2015-05-10 14:21 GMT+02:00 Debian Bug Tracking System <ow...@bugs.debian.org >: > This is an automatic notification regarding your Bug report > which was filed against the scanbd package: > > #783873: scanbd does not work as a service but works fine from a console > > It has been closed by Rolf Leggewie <debian-b...@rolf.leggewie.biz>. > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Rolf Leggewie < > debian-b...@rolf.leggewie.biz> by > replying to this email. > > > -- > 783873: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783873 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > > > ---------- Message transféré ---------- > From: Rolf Leggewie <debian-b...@rolf.leggewie.biz> > To: 783873-d...@bugs.debian.org > Cc: > Date: Sun, 10 May 2015 14:19:27 +0200 > Subject: Re: scanbd does not work as a service but works fine from a > console > On Thu, 30 Apr 2015 22:10:37 +0200 Mathieu Ruellan > <mathieu.ruel...@gmail.com> wrote: > > Package: scanbd > > Version: 1.4.0-2 > > Severity: important > > > > Dear Maintainer, > > > > When i launch scanbd with systemctl and i press a button, nothing > > happens. There is no error or event message in syslog at start or if i > > press a button. > > > > When i launch it from a console "sudo -u saned -g scanner scanbd -f", it > > works. > > > > I don't really see what could be the problem. > > This sounds pretty familiar. In the end, it is almost certainly a > configuration problem. scanbd 1.4.1-2 and later have some improved > detection algorithms to find common configuration errors. You might > want to install that version. > > ---------- Message transféré ---------- > From: Mathieu Ruellan <mathieu.ruel...@gmail.com> > To: Debian Bug Tracking System <sub...@bugs.debian.org> > Cc: > Date: Thu, 30 Apr 2015 22:10:37 +0200 > Subject: scanbd does not work as a service but works fine from a console > Package: scanbd > Version: 1.4.0-2 > Severity: important > > Dear Maintainer, > > When i launch scanbd with systemctl and i press a button, nothing > happens. There is no error or event message in syslog at start or if i > press a button. > > When i launch it from a console "sudo -u saned -g scanner scanbd -f", it > works. > > I don't really see what could be the problem. > > Kind regards, > > Mathieu Ruellan > > > -- System Information: > Debian Release: 8.0 > APT prefers stable > APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing') > Architecture: i386 (x86_64) > Foreign Architectures: amd64 > > Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/bash > Init: systemd (via /run/systemd/system) > > Versions of packages scanbd depends on: > ii libc6 2.19-18 > ii libconfuse0 2.7-5 > ii libdbus-1-3 1.8.16-1 > ii libsane 1.0.24-9 > ii libudev1 215-17 > ii sane-utils 1.0.24-9 > > scanbd recommends no packages. > > scanbd suggests no packages. > > -- Configuration Files: > /etc/scanbd/scanbd.conf changed: > /* > * $Id: scanbd.conf 191 2013-09-23 09:55:27Z wimalopaan $ > * > * scanbd - KMUX scanner button daemon > * > * Copyright (C) 2008 - 2013 Wilhelm Meier (wilhelm.me...@fh-kl.de) > * > * This program is free software; you can redistribute it and/or modify > * it under the terms of the GNU General Public License as published by > * the Free Software Foundation; either version 2 of the License, or > * (at your option) any later version. > * > * This program is distributed in the hope that it will be useful, > * but WITHOUT ANY WARRANTY; without even the implied warranty of > * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the > * GNU General Public License for more details. > * > * You should have received a copy of the GNU General Public License > * along with this program; if not, write to the Free Software > * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA > 02110-1301, USA. > */ > global { > # turn on debugging > > # log to console > debug = true > # debug logging > # 1=error, 2=warn, 3=info, 4-7=debug > debug-level = 2 > > # drop priviliges to this user > #============================= > # Linux (most distributions use the saned user): > # user = saned > # ArchLinux (ArchLinux doesn't have saned user) > # user = daemon > # *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 = scanner > # the saned executable for manager-mode > saned = "/usr/sbin/saned" > saned_opt = {} # string-list > saned_env = { "SANE_CONFIG_DIR=/etc/scanbd" } # list of > environment vars for saned > # Scriptdir specifies where scanbd 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/scanbd/scripts. > # scriptdir = /some/path > # sets scriptdir to the specified absolute path > # Default scriptdir is <path>/etc/scanbd, this is normally > appropriate > # scriptdir = > > # Scripts to execute upon device insertion/removal. > # It can be necessary to load firmware into the device when it is > first > # inserted. For example, scanbuttond backend does not know how to > load > # scanner firmware, and it can be rectified by making a custom > script. > # A simple command like "scanimage -L" in an example insert.script > # invokes saned and it loads the appropriate firmware if necessary. > # These scripts receive environmental variables named in the > "environment" subsection: > # SCANBD_DEVICE - device name (fixed string "dbus device" for dbus > notification) > # SCANBD_ACTION - "insert" or "remove", so one script can be used. > # device_insert_script = "insert.script" > # device_remove_script = > # 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/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 (up to > the total amount of options) > # action definitions > # if the filter matches and the value changes > # from from-value to to-value, > # <script> is executed > # <script> is the full pathname (do not include any parameters) > # if parameters are needed, write a script > > # since we can have only at most one action for each option, the > action-script > # can use the function definition (see above) to distinguish > different tasks > # (e.g. use the env-var SCANBD_FUNCTION defined above) > > action scan { > filter = "^scan.*" > numerical-trigger { > from-value = 1 > to-value = 0 > } > desc = "Scan to file" > # script must be an relative path starting from scriptdir > (see above), > # or an absolute pathname. > # It must contain the path to the action script without > arguments > # Absolute path example: script = "/some/path/foo.script > script = "test.script" > } > action email { > filter = "^email$" > string-trigger { > from-value = "" > to-value = "^email.*" > } > desc = "Scan to email" > # script must be an relative path starting from scriptdir > (see above), > # or an absolute pathname. > # It must contain the path to the action script without > arguments > # Absolute path example: script = "/some/path/foo.script > script = "test.script" > } > action copy { > filter = "^copy$" > string-trigger { > from-value = "" > to-value = "^copy.*" > } > desc = "Copy to printer" > # script must be an relative path starting from scriptdir > (see above), > # or an absolute pathname. > # It must contain the path to the action script without > arguments > # Absolute path example: script = "/some/path/foo.script > script = "test.script" > } > action preview { > filter = "^preview$" > numerical-trigger { > from-value = 1 > to-value = 0 > } > desc = "Preview" > # script must be an relative path starting from scriptdir > (see above), > # or an absolute pathname. > # It must contain the path to the action script without > arguments > # Absolute path example: script = "/some/path/foo.script > script = "test.script" > } > action globaltest { > filter = "^message.*" > desc = "Test (print all env vars)" > # script must be an relative path starting from scriptdir > (see above), > # or an absolute pathname. > # It must contain the path to the action script without > arguments > # Absolute path example: script = "/some/path/foo.script > script = "test.script" > } > } > include(scanner.d/biniou.conf) > > > -- no debconf information > >
