+1
> What is interesting (and we might make that an option) is that the 'no
> display' error results in the image being saved 'headfull' so that you can
> start it up using a display to debug it (suspended process/debugger).
>>
>> That could be done.. but not as userful as simply report an error.
>> Usually we (developers) knowing what we want to do,
>> and what i don't want to see in my headless image is any attempts to
>> access display/ui.
>
> Yeah, that's why I said it would better be an option. The first thing to do
> is simply report the error (and quit, or maybe that should be an option too).
> But many people playing with headless images (myself included) have had
> blocking/locked up images: having a log would be great, but adding this
> option to debug the cause further would be great.
>
> Sven
>
>
