Apport 1.21

Milestone information

Project:
Apport
Series:
trunk
Version:
1.21
Released:
2011-06-08  
Registrant:
Martin Pitt
Release registered:
2011-06-08
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.21.tar.gz (md5, sig) release tarball 11
last downloaded 49 weeks ago
Total downloads: 11

Release notes 

This release does not have release notes.

Changelog 

View the full changelog

Improvements:
 - Supply --desktop option to kdesudo to improve the description which program
   is requesting administrative privileges.
 - apport-checkreports: Exit with status 2 if there are new reports, but apport
   is disabled. This helps crash notification GUIs to not display new crash
   reports in that case. Thanks to Michael Vogt for the original patch.
 - Add data/is-enabled: Shell script to check if apport is enabled. Non-Python
   programs (which can't use apport.packaging.enabled() ) can call this instead
   of having to parse /etc/default/apport themselves, and just check the exit
   code. Inspired by original patch from Michael Vogt, thanks!

Bug fixes:
 - apport-gtk: HTML-escape text for dialogs with URLs. (LP: #750870)
 - dump_acpi_tables.py: Check to see if acpi/tables dir is mounted first.
   Thanks Brian Murray. (LP: #729622)
 - man/apport-cli.1: Document recently added -w/--window option. Thanks Abhinav
   Upadhyay! (LP: #765600)
 - Use kde-open instead of kfmclient to open URLs under KDE. Thanks Philip
   Mu┼íkovac. (LP: #765808)

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.