Comment 0 for bug 1039220
Revision history for this message
| Steve Langasek (vorlon) wrote we should not report crashes to daisy that are not reported to LP due to out-of-date binaries on disk | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Every crash report that gets fixed in a package upload winds up with some fuzziness in the bucket showing a small number of crash reports in the very version that fixes it. E.g.:
https:/
(bug #853060)
This makes it impossible to tell with certainty by looking at errors.ubuntu.com if a crash is really fixed, or if it's just been made less frequent. We need to have good data here to be able to use errors.u.c for decision making around SRU publication.
The suspicion is that the rule preventing launchpad bugs from being filed when the running process doesn't match the file on disk is not being applied correctly to whoopsie. It definitely should be.
(It's possible that this is therefore a duplicate of bug #1020994. I'm not sure, I haven't looked at the code.)
I would also argue that, if this happens in the "system service" case, we should not show the user any crash dialog for it either, so long as we don't have support for leading them to a targeted update to fix the crash. We get no useful crash information from the user in this case, and the risk of confusion from the dialog is great when it's a system service crash. As a matter of policy, front-end applications need to be resilient in the face of failures of back-end daemons.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: apport 2.4-0ubuntu8
ProcVersionSign
Uname: Linux 3.5.0-10-generic x86_64
ApportVersion: 2.4-0ubuntu8
Architecture: amd64
Date: Mon Aug 20 12:34:10 2012
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
PackageArchitec
SourcePackage: apport
UpgradeStatus: Upgraded to quantal on 2012-06-11 (70 days ago)
modified.
mtime.conffile.