Fixed in trunk r2540, thanks Brian!

** Changed in: apport
       Status: New => Fix Released

** Changed in: apport (Ubuntu)
       Status: New => Fix Committed

-- 
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 Committed

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

Reply via email to