apport-retrace fails with crash files with libraries not from the release pocket
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Apport |
Fix Released
|
Undecided
|
Brian Murray |
Bug Description
If one uses apport-retrace with a .crash file from a release other than the tracing system's release the retrace of the .crash file will fail with error messages similar to the following (provided the crashing system has packages installed from -updates or -proposed):
dynamically loaded /lib/x86_
WARNING: /usr/lib/
dynamically loaded /usr/lib/
dynamically loaded /usr/lib/
WARNING: /usr/lib/
This is due to the fact that only the Contents.gz file from the release pocket is searched and the Contents.gz file from -proposed, -updates or -security are not. This issue appears on the retracers for the Ubuntu Error tracker with the following message:
16:12:56,
66f9fd24-
2013-12-13
16:13:32,
back to Cassandra
2013-12-13
16:13:32,
not retrace.
2013-12-13
16:13:32,
processing /tmp/tmp0Y3y84-
The apport error is reproducable with a command like the following:
/usr/bin/
Related branches
- Martin Pitt (community): Approve
-
Diff: 97 lines (+49/-38)1 file modifiedbackends/packaging-apt-dpkg.py (+49/-38)
This is a d-feet crash file from precise for testing with.