program works only when called directly from the command line

Bug #1401389 reported by Rolf Leggewie
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
scanbd (Ubuntu)
Fix Released
High
Rolf Leggewie

Bug Description

the program works for me only when called directly from the command line, not when started by init. init in my case is sysvrc on trusty.

Rolf Leggewie (r0lf)
Changed in scanbd (Ubuntu):
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Rolf Leggewie (r0lf) wrote :

The tar-file contains the log from the console in scanbd.console-log and from syslog in scanbd-syslog.log

First is a startup via init (19:00:53 to 19:07:46, lines 71 to 503). This is followed by a call to scanbd straight from the user command line (19:08:04 to 19:08:56, lines 504 to 1999). The Canon device is found in both cases (19:07:42, line 84 and 19:08:07, line 517). A "file" button press is registered at 19:08:42 that triggers the copy.script (line 1655). Line numbers refer to the syslog since only that one has time-stamps.

Rolf Leggewie (r0lf)
Changed in scanbd (Ubuntu):
status: Confirmed → In Progress
assignee: nobody → Rolf Leggewie (r0lf)
milestone: none → ubuntu-15.03
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package scanbd - 1.4.1-3

---------------
scanbd (1.4.1-3) experimental; urgency=medium

  * configure the backends automatically as much as possible. LP: #1401389
  * init: actually abort on error, but for now do NOT trigger an actual
    non-zero error exit code

 -- Rolf Leggewie <email address hidden> Thu, 26 Feb 2015 11:08:38 +0800

Changed in scanbd (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.