Hi Rolf, Am 11.12.2014 um 12:47 schrieb Rolf Leggewie: > On 11.12.2014 15:39, Wilhelm wrote: >> Well, I see for in syslog.log >> >> Nov 15 19:08:43 localhost scanbd: scanbd: exec for >> /usr/share/scanbd/scripts/copy.script >> Nov 15 19:08:43 localhost scanbd: scanbd: execlp: No such file or directory >> >> which meens that your script isn't found ... but the action is triggered >> from the scanner (once in this log). > > > Hello Wilhelm, > > thank you for the quick response. Like I said, the binary package and > my installation still has many rough edges. They will need to be dealt > with one at a time, in the proper order. > > The part you refer to is the one that is "actually working", where the > call to the script at least happens. Maybe the script does not exist > but that is irrelevant at this time because I want to start scanbd from > init but it doesn't even try to call any script (existing or > non-existing). It only does that when I call it from the command-line. > > Lines 71 to 503 are the ones that show the call where button presses do > not trigger any kind of response. >
I must admit, actually I have no idea whar ist going wrong here. I see that the scanner and all options are recognized as in the call-from-shell case. So, the buttons presses (value changes) should be recognized as well ... On my system (arch linux) there are no problems ... Wilhelm -- Wilhelm w.me...@unix.net -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org