Comment 7 for bug 941060

The way I invoke it indirectly happens inside a shell script that itself is scheduled via cron: (or responds to another external event noninteractively, like email triggered)

#!/bin/bash
# batchjobhandler.sh
Xvfb ${DISPLAY:=:99} -ac -shmem -screen 0 1024x768x8 &
xpid=$! ; sleep 3
at now <<< "fluxbox -display $DISPLAY &> orderlog/fluxbox.$(hostname).log" # & disown # lightweight WM
#xload -display :99 -update 5 -geometry 1100x50 &

Sometimes there may already be fluxbox or another WM on that $DISPLAY, in which I expect the above fluxbox to go ahead and fail--though I don't think that's why Apport launched this crash reporter
.