Hi Martin,
Wait -- this situation makes no sense.
Look at the debug symbol packages it's complaining about: they're not
old by 1 version, but instead really old. Since the dbgsyms are on your
side, how can upgrading to the latest binary packages impact the dbgsym
archive??
For example, here's what apport retracing had to say regarding bug #
973450:
Thank you for your report!
However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:
outdated debug symbol package for dmidecode: package version 2.11-4 dbgsym
version 2.9-1.2build1
outdated debug symbol package for cryptsetup: package version
2:1.4.1-2ubuntu2 dbgsym version 2:1.1.3-4ubuntu2
Look carefully; dmidecode is still at 2.11-4 !!
** Changed in: apport (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/962479
Title:
Crash report cannot be processed due to outdated debug packages on
daily-live
Status in “apport” package in Ubuntu:
New
Bug description:
Debug symbol packages are outdated on latest Live CD 22/03/12 - apport
cannot generated useful stack trace. See bug# 962455.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/962479/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
