Comment 6 for bug 1294007

The checkbox trace suggests it's a problem in the code that tries "passing" the declared environment variables from the invoking environment into the privileged execution backend. Pending a repro procedure, my theory is this:

The job has environ: EXTERNAL_WEBCAM_DEVICE but since it doesn't have user: root, the behavior of environ: is undefined (if it *did* have user: root, we'd pass the value of EXTERNAL_WEBCAM_DEVICE to the backend, a behavior which is very well-tested).

The real solution would be to characterize and fix environ: behavior with no user: parameter. The quick workaround would be to simply remove the environ: line from the job definition.

As a historical note, use of environ: was coded into checkbox from the beginning, but it was never really used; when we ran into the problem of environment values not being sent to the backend, I had to dive into the code to see how it worked, and updated things so that when using user: root, things work as expected. Since it's not needed for non-user: jobs (since the invoking environment will by definition be available), I never continued looking into how it would behave in that case.