Comment 7 for bug 408331

Hello Roland,

Ronald McCollam [2009-09-02 13:54 -0000]:
> If there is additional processing that needs to take place before
> creating a bug based on this crash data

Yes, when the initial .crash file is written, it only contains the
bare minimum of information which needs to be collected when the
crashing process is still in limbo. All expensive bits (such as
querying the package database) are done later, to avoid taking even
more time until the crashed process can rest in peace.

> Is there a process we can automate to perform this, or is this new
> functionality that we need to look into?

The least interactive way to do it with the existing programs is

  apport-cli -c /path/to/crashfile

and press "K", then the .crash file is fully ready to be transferred
to a different system and be submitted to Launchpad (with
double-clicking in nautilus or using ubuntu-bug foo.crash).

Zero interaction is only possible with using the python Apport API and
don't collect hook information, since hooks can also ask interactive
questions.

Is one of these options suitable for you? I can give you the details
about the API if you need this.

--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)