Apport 1.13.4

Milestone information

Project:
Apport
Series:
trunk
Version:
1.13.4
Released:
2010-05-04  
Registrant:
Martin Pitt
Release registered:
2010-05-04
Active:
Yes. Drivers can target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
No users assigned to blueprints and bugs.
Blueprints:
No blueprints are targeted to this milestone.
Bugs:
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-1.13.4.tar.gz (md5, sig) release tarball 10
last downloaded 50 weeks ago
Total downloads: 10

Release notes 

- bash completion: Fix error message if /usr/share/apport/symptoms does not
  exist. Thanks Philip Mu┼íkovac! (LP: #562118)
- general-hooks/parse_segv.py: Report stack exhaustion more clearly and
  correctly handle register dereferencing calls.
- Save/restore environment when calling hooks, in case they change the locale,
  etc. (LP: #564422)
- hookutils.py, command_output(): Do not set $LC_MESSAGES for the calling
  process/hook, just for the command to be called.
- ui.py: When displaying strings from system exceptions, decode them into an
  unicode string, to avoid crashing the KDE UI. (LP: #567253)
- apport-retrace: Fix crash for retracing kernel vmcores, which do not have an
  ExecutablePath.
- apport-bug manpage: Clarify when apport-collect may be used. Thanks Brian
  Murray! (LP: #537273)
- generic hook: Check ProcMaps for unpackaged libraries, and ask the user if
  he really wants to continue. If he does, tag the report as "local-libs" and
  add a "LocalLibraries" field to the report with a list of them.
  (LP: #545227)

Changelog 

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.