APPORT_IGNORE_OBSOLETE_PACKAGES not working for reprocessing .crash files

Bug #427810 reported by Sebastien Bacher
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
Expired
Wishlist
Unassigned

Bug Description

Binary package hint: apport

Using the current karmic version using "APPORT_IGNORE_OBSOLETE_PACKAGES=1 ubuntu-bug software.crash" still displays errors about the outdated versions

Revision history for this message
Marco Rodrigues (gothicx) wrote :

I think APPORT_STAGING is also not working.

Changed in apport (Ubuntu):
status: New → Confirmed
Revision history for this message
Marco Rodrigues (gothicx) wrote :

I figured out the problem. How to reproduce:

I've modified apport/ui.py to add coreutils to my crash report as an obsolete package.

$ bash -c 'kill -SEGV $$'
$ /usr/share/apport/apport-gtk -c /var/crash/obsolete_crash.crash
$ vim /var/crash/_bin_bash.1000.crash

Look at the end of file for this:

UnreportableReason:
 You have some obsolete package versions installed. Please upgrade the following packages and check if the problem still occurs:

 coreutils

So, now if you run:
$ APPORT_IGNORE_OBSOLETE_PACKAGES=1 /usr/share/apport/apport-gtk -c /var/crash/_bin_bash.1000.crash

It always shows the 'Problem bash' window. So this variable should be also verified when sending the report and not only when regenerating it.

Changed in apport (Ubuntu):
assignee: nobody → Marco Rodrigues (gothicx)
Revision history for this message
Martin Pitt (pitti) wrote :

Marco,

http://bazaar.launchpad.net/~gothicx/apport/ignore_obsolete_packages/revision/1597 is wrong, it would instantly disable _all_ unreportable reasons, not just the "obsolete packages" one.

The problem here is that apparently Sebastien and you tried to re-process a .crash file which already went through data collection in the UI earlier? As soon as it collects data once, then it updates the .crash file, and UnreportableReason will be written to the .crash file. Specifying $APPORT_IGNORE_OBSOLETE_PACKAGES later on doesn't help. So either put APPORT_IGNORE_OBSOLETE_PACKAGES into your general environment, or don't collect information from the Apport notification which opens automatically (through update-notifier).

Supporting this properly would mean that ui.py needs to dump all the package, hooks, and UnreportableReason data fields, and re-collect information again. It should probably be sufficient to just del report['Stackrace'], that's the field that collect_info() uses to determine whether or not it needs to collect information.

Martin Pitt (pitti)
summary: - APPORT_IGNORE_OBSOLETE_PACKAGES not working
+ APPORT_IGNORE_OBSOLETE_PACKAGES not working for reprocessing .crash
+ files
Changed in apport (Ubuntu):
status: Confirmed → Triaged
importance: Undecided → Wishlist
Changed in apport (Ubuntu):
assignee: Marco Rodrigues (gothicx) → nobody
Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

Changed in apport (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for apport (Ubuntu) because there has been no activity for 60 days.]

Changed in apport (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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