apport 2.13-0ubuntu1 source package in Ubuntu
Changelog
apport (2.13-0ubuntu1) trusty; urgency=medium * New upstream release. Changes since our previous merge: - Do not report keys starting with '_' to the crash database. This can be used for keeping private keys in .crash files between crash and report time, or to store data between hooks etc., without cluttering reports. - UI: In "run all pending crashes" mode, skip reports that happened during logout in a desktop (specifically, logind) session; they are uninteresting and confusing to see at the next login. (LP: #1033932) They can still be reported manually with running the .crash file directly, but this sufficiently reduces the need to explicitly flag whether the report concerns a logout crash. (LP: #1067646) - Add support for PID namespaces (Linux containers): Crashes originating from a container on a system running a >= 3.12 kernel will be automatically redirected to apport inside the container, or ignored if apport is not installed in the container. Thanks to Stéphane Graber! - Print a warning when trying to retrace a report from a foreign architecture and gdb-multiarch is not installed. (LP: #1239395) - etc/init.d/apport: Don't change core_pattern when running in a container, as this influences the host and other containers, too. * apport/ui.py: Rename "MarkForUpload" whoopsie hack field to "_MarkForUpload" and remove delta from launchpad.py. Fields starting with '_' are now considered private. * debian/apport.upstart: Add "%P" macro to core_pattern, to enable Linux container handling with upstart. * debian/apport.upstart: Don't change core_pattern when running in a container, as this influences the host and other containers, too. (LP: #1267728) -- Martin Pitt <email address hidden> Fri, 10 Jan 2014 09:07:07 +0100
Upload details
- Uploaded by:
- Martin Pitt
- Uploaded to:
- Trusty
- Original maintainer:
- Martin Pitt
- Architectures:
- all
- Section:
- utils
- Urgency:
- Medium Urgency
See full publishing history Publishing
Series | Published | Component | Section |
---|
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
apport_2.13.orig.tar.gz | 1.2 MiB | 14181a926207ae3beb76f405838a0efe5f5c4afe133b5124a0f63a6e3df8a7c4 |
apport_2.13-0ubuntu1.diff.gz | 131.3 KiB | 9927c8ac4486c19965c70e4803409f92d309a14196da2c9b1cdfc14dc67dac29 |
apport_2.13-0ubuntu1.dsc | 2.8 KiB | feed1eba04c5073177865b5bde7e5b7e7fc572ffec660d8ca58212c825c3e1b8 |
Available diffs
Binary packages built by this source
- apport: automatically generate crash reports for debugging
apport automatically collects data from crashed processes and
compiles a problem report in /var/crash/. This utilizes the crashdump
helper hook provided by the Ubuntu kernel.
.
This package also provides a command line frontend for browsing and
handling the crash reports. For desktops, you should consider
installing the GTK+ or Qt user interface (apport-gtk or apport-kde).
- apport-gtk: GTK+ frontend for the apport crash report system
apport automatically collects data from crashed processes and
compiles a problem report in /var/crash/. This utilizes the crashdump
helper hook provided by the Ubuntu kernel.
.
This package provides a GTK+ frontend for browsing and handling the
crash reports.
- apport-kde: KDE frontend for the apport crash report system
apport automatically collects data from crashed processes and
compiles a problem report in /var/crash/. This utilizes the crashdump
helper hook provided by the Ubuntu kernel.
.
This package provides a KDE frontend for browsing and handling the
crash reports.
- apport-noui: tools for automatically reporting Apport crash reports
apport automatically collects data from crashed processes and
compiles a problem report in /var/crash/. This utilizes the crashdump
helper hook provided by the Ubuntu kernel.
.
Installing this package will configure your system to automatically submit
all new Apport crash reports.
- apport-retrace: tools for reprocessing Apport crash reports
apport-retrace recombines an Apport crash report (either a file or a
Launchpad bug) and debug symbol packages (.ddebs) into fully symbolic
stack traces. This can optionally use a sandbox for installing debug symbol
packages and doing the processing, so that entire process of retracing crashes
can happen with normal user privileges without changing the system.
.
You need to install gdb-multiarch if you want to be able to retrace crash
reports which happened on a different architecture than the one you run
apport-retrace on.
- apport-valgrind: valgrind wrapper that first downloads debug symbols
apport-valgrind is a valgrind wrapper that automatically downloads related
available debug symbols and provides them to valgrind's memcheck tool, which
is executed. The output is a valgrind log file ("valgrind.log") that contains
stack traces (with as many symbols resolved as available) and that shows
memory leaks.
- dh-apport: debhelper extension for the apport crash report system
apport automatically collects data from crashed processes and
compiles a problem report in /var/crash/. This utilizes the crashdump
helper hook provided by the Ubuntu kernel.
.
This package provides a debhelper extension to make it easier for other
packages to include apport hooks.
- python-apport: Python library for Apport crash report handling
This Python package provides high-level functions for creating and
handling apport crash reports:
.
* Query available and new reports.
* Add OS, packaging, and process runtime information to a report.
* Various frontend utility functions.
* Python hook to generate crash reports when Python scripts fail.
- python-problem-report: Python library to handle problem reports
This Python library provides an interface for creating, modifying,
and accessing standardized problem reports for program and kernel
crashes and packaging bugs.
.
These problem reports use standard Debian control format syntax
(RFC822).
- python3-apport: Python 3 library for Apport crash report handling
This Python package provides high-level functions for creating and
handling apport crash reports:
.
* Query available and new reports.
* Add OS, packaging, and process runtime information to a report.
* Various frontend utility functions.
* Python hook to generate crash reports when Python scripts fail.
- python3-problem-report: Python 3 library to handle problem reports
This Python library provides an interface for creating, modifying,
and accessing standardized problem reports for program and kernel
crashes and packaging bugs.
.
These problem reports use standard Debian control format syntax
(RFC822).