apport generates crash files that are incomplete according to apport-retrace

Bug #145358 reported by Laurent Bonnaud
2
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Hi,

here is the problem:

# apport-retrace /var/crash/_usr_bin_evolution.1000.crash
report file does not contain required fields: CoreDump Package ExecutablePath

This is with the latest apport version in gutsy:

ii apport 0.97 automatically generate crash reports for deb
ii apport-gtk 0.97 GTK frontend for the apport crash report sys
ii apport-qt 0.97 Qt4 frontend for the apport crash report sys
ii apport-retrace 0.97 tools for reprocessing Apport crash reports

This bug looks very much like bug #95396, but this is an old bug that has been fixed.

I will attach the crash file ASAP.

Revision history for this message
Laurent Bonnaud (laurent-bonnaud) wrote :
Revision history for this message
Martin Pitt (pitti) wrote :

This is done on purpose. When the crash happens, we only collect a minimal amount of information, and the expensive bits (like package versions, md5sum checks, invoking gdb) are moved to the frontend.

However, if you do not want to run the .crash file through the UI first, you can call apport-retrace with

  -R, --rebuild-package-info
                        Rebuild report's Package information

(from --help output).

Changed in apport:
status: New → Won't Fix
Revision history for this message
TJ (tj) wrote :

Just got caught out by this on Jaunty. Wasn't aware of the -R option since the man page is, it seems, out fo date quite significantly.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.