desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #67092
[Bug 914220] Re: crash reports with DBus.Error.NoReply should be blacklisted
This bug was fixed in the package apport - 1.91-0ubuntu1
---------------
apport (1.91-0ubuntu1) precise; urgency=low
* New upstream release:
- crashdb.py, check_duplicate(): If a crash has a signature but no
existing duplicate in the DB, also check for an existing address
signature duplicate in the DB.
- apport-retrace: Use DistroRelease specific subdirectory of the cache dir
for mapping a file to a package, as these maps are release specific.
- packaging-apt-dpkg.py: Refresh Contents.gz cache if it is older than one
day.
- crashdb.py: Ensure that address_signature duplicate db table does not
have multiple identical signatures by making it a primary key. Bump the
db format to "3". Existing databases need to be migrated manually as
SQLite does not allow adding a "PRIMARY KEY" constraint to existing
tables.
- crashdb.py: Do not add a new address signature entry if one already
exists.
- apport-cli: Fix UnicodeDecodeError on unicode report values.
(LP: #275972)
- launchpad.py: Only set bug task importance if it is undecided.
- apport-retrace: Fix "an useful" typo. (LP: #911437)
- report.py: Filter out frames which are internal kernel/glibc
implementation details and not stable across duplicates. In particular,
filter out __kernel-syscall() and the SSE stubs.
- crashdb.py: Remove debugging leftover which completely disabled bug
pattern checking.
- report.py: Update reading AssertionMessage. Current (e)glibc turned
__abort_msg from a simple static string into a struct.
- Change permissions of .crash files from 0600 to 0640, so that /var/crash
can be made g+s and crash handling daemons can access those.
- Python exceptions: Blacklist DBus.Error.NoReply. It does not help to get
these traces from the client-side application, you need the actual
exception in the D-Bus server backend instead. (LP: #914220)
- Support /etc/apport/whitelist.d/ similarly to /etc/apport/blacklist.d/,
for cases like installer environments where only crashes of a few selected
programs should be reported.
-- Martin Pitt <martin.pitt@xxxxxxxxxx> Wed, 18 Jan 2012 09:56:00 +0100
** Changed in: apport (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/914220
Title:
crash reports with DBus.Error.NoReply should be blacklisted
Status in “apport” package in Ubuntu:
Fix Released
Bug description:
We receive lots of crash reports with DBus.Error.NoReply in them that
are not useful in their current state as the dbus error message is
generic and can happen for a lot of reasons, subsequently these
reports should be blacklisted and no longer reported.
For example bug 907416, bug 715523 and bug 864563.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: apport 1.90-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-8.14-generic 3.2.0
Uname: Linux 3.2.0-8-generic x86_64
ApportLog:
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
CheckboxSubmission: 2e6ecd139611830c78226ad04ff4c093
CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
Date: Tue Jan 10 12:28:20 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
PackageArchitecture: all
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: Upgraded to precise on 2012-01-04 (5 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/914220/+subscriptions