Apport 2.14.2

Milestone information

Martin Pitt
Release registered:
Yes. Drivers can target bugs and blueprints to this milestone.  

Download RDF metadata


Assigned to you:
No blueprints or bugs assigned to you.
No users assigned to blueprints and bugs.
No blueprints are targeted to this milestone.
No bugs are targeted to this milestone.

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon apport-2.14.2.tar.gz (md5, sig) release tarball 30
last downloaded 37 weeks ago
Total downloads: 30

Release notes 

* Delay the import of the glob and re modules in the python apport hook,
   and only import them when needed. Speeds up interpreter startup time
   by 50%. Thanks Matthias Klose! (LP: #1307684)
 * Move error handling for invalid .crash files into collect_info(), so that it
   also applies when using the "Show Details..." button in the UI. Otherwise
   the UI just hangs eternally at this point when encountering broken core
   dumps. (LP: #1282349)
 * apt/dpkg install_packages(): Try to install the requested package version
   instead of always picking the most recent one. This should improve retracing
   results for older crash reports. Thanks to Brian Murray for inspiring this.
 *, make_sandbox(): When determining packages to install from
   ProcMaps, look up and use the package versions from the reporter, to improve
   retracing results. Thanks Brian Murray for the initial patch!
 * iwlwifi_error_dump: Make reports private, and subscribe canonical-kernel-team.
   Thanks Seth Forshee. (LP: #1313818)
 * signal_crashes test: Time out after 5 seconds if the test process does not
   terminate on the specified signal, to avoid eternal hangs.
 * signal_crashes test: Ensure that we don't inherit an ignored SIGQUIT from
   the caller.


This release does not have a changelog.

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.