This bug was fixed in the package apport - 2.6.3-0ubuntu1
---------------
apport (2.6.3-0ubuntu1) raring; urgency=low
* New upstream release. Changes since our previous snapshot:
- debian.py: Only reject reports with useless stack traces if the report
actually has a stack trace at all.
- debian.py: Fix UTF-8 string handling. Thanks Ritesh Raj Sarraf.
- debian.py: Fix crash on broken "Package" fields, as generated by current
Debian/Ubuntu dkms package.
- data/apport: Call fsync when writing upstart crash reports.
- report.py, add_gdb_info(): Handle libnih's assertion messages.
(LP: #997359)
- apport-gtk, apport-kde: Don't provide an option to restart a crashed
application when the crash occurred in a thread (LP: #1033902).
- apport-retrace: Disallow option -C without option -S. Thanks Kyle
Nitzsche.
- fileutils.py, mark_report_upload(): Refresh the .upload stamps if a
previous version of the report was already uploaded, but another
instance of the problem happened since then. Thanks Brian Murray. (LP:
#1084296)
- Ignore implausibly low addresses when computing
StacktraceAddressSignature. These are usually artifacts from gdb when
not having debug symbols, and having too many of them prevents proper
client-side duplicate detection and proper bucketing in daisy.
(LP: #1084996)
- fileutils.py: Ignore .desktop files with NoDisplay=true. (LP: #1048524)
* debian/tests/control: Run tests as root, just like before switching our
autopkgtests to run as user "ubuntu" by default. This enables a couple of
extra tests, and avoids some confusion because the distro and the user
name are identical.
* data/package-hooks/source_linux-nexus7.py: Fix PEP-8 error.
-- Martin Pitt <[email protected]> Fri, 30 Nov 2012 18:00:01 +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/1084296
Title:
possible for a 2nd occurrence of a crash not to be sent to errors
Status in Apport crash detection/reporting:
Fix Released
Status in “apport” package in Ubuntu:
Fix Released
Status in “apport” source package in Precise:
Triaged
Status in “apport” source package in Quantal:
Triaged
Bug description:
I was testing errors in the cloud using juju and created a crash
report for d-feet. The first time I did this the a .crash file was
created and then a corresponding .upload and .uploaded file were
created. The second time I did this a new .crash file was created but
a new .upload file was not and subsequently the 2nd occurrence of this
crash was not sent to the error tracker.
My /var/crash directory:
-rw-rw-r-- 1 bdmurray whoopsie 0 Nov 28 10:25
_usr_bin_d-feet.1000.upload
-rw------- 1 whoopsie whoopsie 0 Nov 28 13:14
_usr_bin_d-feet.1000.uploaded
-rw-r----- 1 bdmurray whoopsie 3401262 Nov 28 13:43 _usr_bin_d-feet.1000.crash
In apport/fileutils.py we can see that there are no checks done to see
if there is already a .upload or .uploaded file:
def mark_report_upload(report):
report = '%s.upload' % report.rsplit('.', 1)[0]
with open(report, 'a'):
pass
So if a .upload for the crash already exists a new one is not created
nor is the existing one modified.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1084296/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
