apport should let the user see the crash details even if some packages are obsolete

Bug #267488 reported by Fabien Tassin on 2008-09-07
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
Low
Unassigned

Bug Description

Binary package hint: apport

Apport should let the user see the crash detail UI even if some packages are "obsolete".
Running intrepid/ubuntu+1, there are always a lot of updates so when a crash occurs, it's very likely that something else completely unrelated as been bumped, making apport claim it is not interested by further information about that particular crash.

It would be nice to go one step further and present crash details to the user so he can have a look at launchpad for existing bug reports (and maybe solution/workarounds), even if apport refuses to post the crash on LP by itself.

Martin Pitt (pitti) wrote :

Please note that, as a developer, you can override the check once with defining $APPORT_IGNORE_OBSOLETE_PACKAGES.

I agree that the note could be displayed in the crash details window, with the "send report" button being disabled.

Changed in apport:
importance: Undecided → Low
status: New → Triaged
Bryce Harrington (bryce) wrote :

After the .crash file has been generated, specifying APPORT_IGNORE_OBSOLETE_PACKAGES has no effect. You can edit the .crash file to remove the UnreportableReason section and then file it. Apport should provide a switch or env variable which enables this if the UnreportableReason is due to obsolete files.

One use case of this is: When I implemented the freeze hook for apport, I wanted to verify the .crash file was including the proper info. However the system was not fully up to date so the .crash file could not be posted. Having to bring the system 100% up to date and then re-trigger a new freeze in order to generate a valid .crash file was time consuming.

Māris Fogels (mars) wrote :

A second use-case for this: I'm running nightlies of Firefox and want to report a difficult-to-reproduce bug that has been occurring with enough frequency to warrant a report on LP. However, because nightly moves fast, the PPA package has likely changed since I was last able to reproduce the bug. It would be great to have some way to override the obsolete package check so that I can report a bug against yesterday's build.

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

Other bug subscribers