This bug was fixed in the package apport - 2.6.1-0ubuntu9
---------------
apport (2.6.1-0ubuntu9) quantal-proposed; urgency=low
* Fix OSError crash in mark_report_upload(); regression from
2.6.1-0ubuntu8.
apport (2.6.1-0ubuntu8) quantal-proposed; urgency=low
* 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.
Backported from trunk r2541. (LP: #1084996)
* 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. Backported from trunk r2540.
(LP: #1084296)
apport (2.6.1-0ubuntu7) quantal-proposed; urgency=low
* data/general-hooks/ubuntu.py: Deal with dpkg_log file being a string
instead of bytes (LP: #1080915)
-- Martin Pitt <martin.p...@ubuntu.com> Wed, 05 Dec 2012 10:16:00 +0000
** Changed in: apport (Ubuntu Quantal)
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:
Fix Committed
Status in “apport” source package in Quantal:
Fix Released
Bug description:
[Test Case]
1) (xeyes &); sleep 1; killall -SEGV xeyes
2) check /var/crash
3) (xeyes &); sleep 1; killall -SEGV xeyes
3) check /var/crash notice that .crash is newer than .upload and .uploaded
Original 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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
