crash reports with DBus.Error.NoReply should be blacklisted
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
Fix Released
|
Medium
|
Martin Pitt |
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
ProcVersionSign
Uname: Linux 3.2.0-8-generic x86_64
ApportLog:
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
CheckboxSubmission: 2e6ecd139611830
CheckboxSystem: bb422ca46d02494
Date: Tue Jan 10 12:28:20 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
PackageArchitec
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)
Changed in apport (Ubuntu): | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → Martin Pitt (pitti) |
Fixed in trunk r2122.