Workaround 1:
Job with xvfb-run --auto-display (Cuetopia still reports the job as DEAD as it tries to kill xvfb-run instead of blender, which it can't, however, the output generated is correct). One thing to note is that I first fired up blender with xvfb-run -n 0 instead, but the job failed with something like display busy. However, I can't reproduce that right now.
Describe the documentation issue
A Blender job fails due to
Unable to open a display
Workaround 1: Job with
xvfb-run --auto-display
(Cuetopia still reports the job as DEAD as it tries to killxvfb-run
instead ofblender
, which it can't, however, the output generated is correct). One thing to note is that I first fired upblender
withxvfb-run -n 0
instead, but the job failed with something likedisplay busy
. However, I can't reproduce that right now.EDIT: Forgot to actually add some workaround II output:
I'm sure there is a better way to set up the
blender
environment withDISPLAY=:0
than prepending theblender
command incuesubmit/Constants.py
: