This bug was fixed in the package apport - 2.14.7-0ubuntu1
---------------
apport (2.14.7-0ubuntu1) utopic; urgency=medium
* New upstream release:
- Fix interpretation of core dump ulimits: they are in bytes, not KiB.
(LP: #1346497)
- apport-retrace: Don't require specifying an operation; default to
updating the given .crash file. (LP: #1361242)
- Write report even on UnreportableReasons, so that whoopsie can still
upload them. (LP: #1360417)
- apt/dpkg install_packages(): Write a "packages.txt" into sandbox root
directory to keep track of installed packages and their versions.
Prerequisite for LP #1352591.
- apt/dpkg install_packages(): Avoid re-downloading/installing packages
which are already installed into a permanent sandbox. Prerequisite for
LP #1352591.
- sandboxutils.py, make_sandbox(): Drop check for already existing files
when dynamically resolving libraries and ExecutablePaths; with that,
these packages would never get updated in a permanent sandbox. The new
version tracking from above now takes care of that. (LP: #1352591)
- Fix report.test_add_proc_info test to stop assuming that pid 1 is named
"init", as one can specify a different one on the kernel command line.
- report.py, add_gdb_info(): Check for truncated core dumps, and set
UnreportableReason and raise an IOError on them. Handle this in
apport-retrace and whoopsie-upload-all to fail properly instead of
silently producing broken Stacktraces. (LP: #1354571)
-- Martin Pitt <[email protected]> Fri, 29 Aug 2014 12:38:54 +0200
** 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/1360417
Title:
thread_collect_info can leave out information in .crash files
Status in “apport” package in Ubuntu:
Fix Released
Bug description:
I noticed there were some crash reports in the Ubuntu Error Tracker
with incomplete information in them (bug 1355546) and ended up
creating a test case that recreates one way the problem can occur.
1) in a terminal run 'sudo chmod 600 /etc/apt/sources.list'
2) run 'update-manager'
3) observe a crash and click "Leave Closed" on the crash notification dialog
4) confirm that there is in /var/crash/ a .upload and .uploaded file for the
update-manager crash
If you inspect the update-manager crash file you'll notice it is
missing Dependencies and DistroRelease so the additional apport data
collection was never done. Additionally, some information from "Show
Details" of apport dialog does not appear in the report.
UnreportableReason: E: Opening /etc/apt/sources.list...
DistroRelease: Ubuntu 14.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1360417/+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
