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/1084996

Title:
   StacktraceAddressSignature is missing

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:
  Some crash reports are missing a StacktraceAddressSignature field,
  which prevents proper processing by whoopsie.

  I seem to be able to reproduce this rather reliably with some simple
  X.org programs, such as

  SRU TEST CASE:
  $ (xeyes &); sleep 1; killall -SEGV xeyes
  $ (xcalc &); sleep 1; killall -SEGV xcalc

  With the current versions in precise and quantal, these reports
  usually do not have a StacktraceAddressSignature field in the details.
  With the proposed version they should.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1084996/+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

Reply via email to