This bug was fixed in the package apport - 2.8-0ubuntu1
---------------
apport (2.8-0ubuntu1) raring; urgency=low
* New upstream release:
- Factor out sandbox management functions from apport-retrace into
apport/sandboxutils.py, so that other programs can re-use the API
easily. Thanks to Kyle Nitzsche for the initial work on this.
- Generate a crash signature for kernel OOPSes.
- Add "apport-valgrind" tool to produce valgrind reports in a temporary
sandbox with debug symbols (similar to apport-retrace). Thanks Alex
Chiang and Kyle Nitzsche!
- Fix StacktraceAddressSignature generation on ARM. (LP: #1089778)
- debian.py: Fix TypeError crash in payload generation. Thanks Ritesh Raj
Sarraf.
- apport_python_hook.py: Update "ExecutableTimestamp" field when mangling
"ExecutablePath". (LP: #1077253)
* Add new apport-valgrind binary package.
* Re-enable Launchpad crash reports for raring.
-- Martin Pitt <[email protected]> Tue, 08 Jan 2013 08:39:35 +0100
** Changed in: apport (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1077253
Title:
possible for ExecutableTimestamp to not be for the binary in
ExecutablePath
Status in “apport” package in Ubuntu:
Fix Released
Status in “apport” source package in Quantal:
Triaged
Bug description:
I was testing bug 1067542 again and ran into a situation where release
upgrade crash was unreportable because the binary had changed.
Digging into the issue DistUpgradeApport.py from update-manager /
ubuntu-release-upgrader sets ExecutablePath = '/usr/bin/do-release-
upgrade', however ProcCmdline = '/usr/bin/python /tmp/update-manager-
xyz/quantal' (from the dist upgrade tarball).
Then when add_proc_info calls _check_interpreted (in apport/report.py)
ExecutablePath is temporarily set to '/tmp/update-manager-xyz/quantal'
and the ExecutableTimestamp is calculated using that ExecutablePath.
Later, on when collect_info (in apport/ui.py) is run we use the "real"
ExecutablePath, '/usr/bin/do-release-upgrade' in this example, which
will have a different ExecutableTimestamp than the one written to the
report during _check_interpreted.
This ultimately, makes reporting crashes in the release upgrader not
reportable.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1077253/+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
