Apport 1.10
Milestone information
- Active:
- No. Drivers cannot target bugs and blueprints to this milestone.
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
Release notes
New features:
- Add a mode for updating an existing problem report to ui.py (-u/--update).
This is similar to the Ubuntu specific "apport-collect" tool, but
implemented the right way now: In particular, this has access to the UI and
thus can use interactive hooks (LP: #385811) and show you what is being sent
for confirmation/
- apport-bug: If invoked as "apport-collect" or "apport-update-bug" (i. e.
through a symlink), run apport in update mode (-u <number>). This provides a
convenient no-options command line program. Please note that setup.py does
not currently install such a symlink. Update the apport-bug manpage
accordingly.
Improvements:
- launchpad.py: Use new login_with() to clean up code, and specify allowed
access levels (WRITE_PRIVATE is the only sensible one anyway). (LP: #410205)
- New hookutils functions:
xsession_errors (match lines from ~/.xsession-errors)
shared_libraries (determine which libraries a binary links with)
links_
- New CrashDatabase API: get_affected_
- Rename CrashDatabase.
- Add CrashDatabase.
primarily useful for collecting local standard and package hook data for an
already existing bug report which was not filed through Apport. This checks
can_
particular bug. (LP: #485880)
Bug fixes:
- Ignore SIGXCPU and SIGXFSZ; thanks to Kees Cook. (LP: #498074)
- launchpad.py: Do not mark non-Ubuntu bugs as needs-retrace, since there is
no retracer right now. (LP: #489794)
- packaging-
malformed Dependencies.txt lines. (LP: #441709)
- use-local: Fix for new source tree location of "apport" binary.
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.