apport-retrace: try older debug package versions
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
Triaged
|
Low
|
Unassigned |
Bug Description
It is the second time now that the apport retracing service tells me:
"Crash report cannot be processed" and
"However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:"
However. Before and after the incident happenend, I had updated the whole system. So I can not do anything do help and to see if the bug still occurs with newer packages because they can not be installed. At least I do not know how.
This kind of problem has three main sources:
* Retracers being broken for an extended period of time, as happened during Oneiric. Hopefully with the rewritten apport-retrace this should now happen a lot less often, as we dropped the dependency to the fragile fakechroot.
There is no single "fix" for this, it's a question of continuously maintaining the retracers.
* debug symbols missing. This is mostly a problem of Launchpad not supporting debug symbol packages yet, and our hack for fetching/publishing them just fails occasionally. This is not a bug in apport itself, but in how ddeb packages are handled in Launchpad/Ubuntu.
* apport-retrace not trying to install older versions of packages, mostly because apt does not support this really. However, we can apply some hackery to work around this in principle. This is what the bug title says, and what is actually actionable in apport itself.
Another cause could also be that the retracing service was broken for a while and only reprocessed your bugs several days later. Can you please point me to some example bugs where this happened?
Did you actually have held back packages at that time, or was that just a conjecture?