Apport 1.94
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
Bug fixes:
- apport: Set the group of written reports to "whoopsie" if that group exists.
- Fix tests to run properly against the system-installed modules and binaries.
- test/run: Run under LC_MESSAGES=C to avoid test failures due to translated
strings.
- general-
to libgtk-3.
- launchpad.py: Properly handle "Expired" status, to avoid marking new bugs as
duplicates of expired ones. (LP: #941854)
- apport: Fix crash if the "whoopsie" group does not exist. (LP: #942326)
- report.py, crash_signature(): Do not put "<module>" frames into Python crash
signatures that happen outside of function/method calls. Fall back to the
file/line number as a frame description instead. This will do a much better
job at disambiguating e. g. different ImportError crashes. (LP: #920403)
- Make "binary changed since the time of the crash" error message more
comprehensible, thanks Paolo Rotolo. (LP: #942830)
- crashdb.py, check_duplicate(): It can happen that a bug gets identified as
being a duplicate of bug S by symbolic signatures and a duplicate of bug A
by address signatures. Empirical evidence shows that this is due to the
unavoidable jitter in stack traces (A and S not being identified as
duplicates as their signatures differ slightly) and not a logic error. So
instead of erroring out, duplicate all three bugs and keep the lowest number
as the master ID. (LP: #943117)
- Revert the usage of multiple nested threads during data collection, and
switch back to only using one UI thread. The UI implementations can, and now
do, decide between showing a spinner and showing a progress dialog in the
ui_*
multiple UI threads do changes concurrently (LP: #901675), and also avoids
multi-thread induced crashes in Pango (LP: #943661). The removal of the
collect() method also fixes the new crashes in it. (LP: #942098, #939803)
- ui.py, get_desktop_
- data/unkillable
while the report is created. (LP: #546369)
- apport/
lspci. (LP: #904489)
- Drop hardcoded "Ubuntu" words again which crept in with the whoopsie support
merge. Use the DistroRelease: field.
- apport-kde: Fix Home page URL in KApplication metadata.
- apport-gtk: Fix resizability and size after hiding details. (LP: #405418)
Improvements:
- test/run: Drop "local" argument. This now tests against the source tree when
run in the source tree root, and against the system libraries/programs when
run from anywhere else.
- test/run: Consider command line arguments as test names and only run those
when given. Also support just running a single test.
- testsuite: Force the skipping of online tests when $SKIP_ONLINE_TESTS is
set.
- hookutils.py, xsession_errors(): Add a reasonable default pattern which
matches glib-style warnings, errors, criticals etc. and X window errors.
In data/general-
rather incomplete custom pattern. (LP: #932660)
- packaging.py: Add get_package_
apt-dpkg.
- report.py, add_package_info(): Add "[origin: ...]" tag to "Package" and
"Dependencies" fields for any package which is not native to the
distribution. If any such package is present, tag the report with
"third-
- apport/
for the test suite. Use it instead of a hardcoded Debian/Ubuntu specific
name in test/test_hooks.py.
- test/test_
reporting a bug against an installed/
crash with and without showing details. This reproduces the recent crashes
like LP #901675 or LP #943661.
- test_ui.py: Add a test case for reporting a complete report on uninstalled
package. This happens when reporting a problem from a different machine
through copying a .crash file.
- test/run: Add a test that there are no hardcoded "Ubuntu" words in the
source. The code should use the DistroRelease: field or lsb_release.
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.