** Description changed: TEST CASE: 1) sudo vi /etc/default/apport 2) set enabled=1 3) sudo service apport start 4) install lp-grab-attachments 5) lp-grab-attachments 2039920 (should crash with a keyerror) 6) close the apport dialog regarding the application crashing (via the X in the corner) - 7) vi $(which lp-grab-attachments) + 7) sudo vi $(which lp-grab-attachments) 8) modify copyright year or some comment 9) ubuntu-bug /var/crash/_usr_bin_lp-grab-attachments.*crash 10) observe apport dialog that this is unreportable and click okay 11) ls -l /var/crash (observe _usr_bin_lp-grab-attachments .upload and .uploaded files) 12) remove _usr_bin_lp-grab-attachments files in /var/crash + 13) reinstall lptools 13) install package from -proposed, follow test case and there should *not* be a .upload or .uploaded file as seen in step 11 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://errors.ubuntu.com/bucket/?id=%2Fusr%2Fbin%2Fubuntuone-installer%3AGError%3Afinished%3Afunction (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: BugDistroRelease: Ubuntu 12.10 Package: apport 2.4-0ubuntu8 ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1 Uname: Linux 3.5.0-10-generic x86_64 ApportVersion: 2.4-0ubuntu8 Architecture: amd64 Date: Mon Aug 20 12:34:10 2012InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) PackageArchitecture: allSourcePackage: apport UpgradeStatus: Upgraded to quantal on 2012-06-11 (70 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2012-05-04T17:01:02
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1039220 Title: don't report crashes for programs that don't match the file on disk (like for kernel crashes) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1039220/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
