Crash database requirements (was: The need for apport hooks (was: Re: SRUs for typo fixes in descriptions))

Robert Collins robertc at
Tue Aug 9 06:46:58 UTC 2011

On Tue, Aug 9, 2011 at 5:37 PM, Christopher James Halse Rogers
<raof at> wrote:
> While we're using the terminology "crash report", I want to ensure that
> there's a sufficiently general understanding of what this means.  I
> think we'd want this to cover at least:
>  * Actual C-style crashes, with core.
>  * Unhandled exceptions, such as you'd get from Python et al
>  * Kernel oops and panics
>  * Intel GPU dump output
>  * dmesg & Xorg.0.log, triggered by GPU hangs

All of those fit what I've been talking about :) - I'd extend the list with:
 * Nonfatal but significant issues (e.g. in LP a page that is slower
than N seconds is logged with full data gathering but does not show an
error to the user.) A desktop example might be requested X extensions
that a driver doesn't support well (giving data to inform development
decisions such as optimisation efforts).


More information about the ubuntu-devel mailing list