I have the same crash again this morning. How can I associate today's
report with bug# 936560?  All the options I am offered begin with 7.

On Fri, Aug 14, 2015 at 9:29 PM, Apport retracing service <
<email address hidden>> wrote:

> *** This bug is a duplicate of bug 936560 ***
>     https://bugs.launchpad.net/bugs/936560
>
> Thank you for taking the time to report this crash and helping to make
> this software better.  This particular crash has already been reported
> and is a duplicate of bug #936560, so is being marked as such.  Please
> look at the other bug report to see if there is any missing information
> that you can provide, or to see if there is a workaround for the bug.
> Additionally, any further discussion regarding the bug should occur in
> the other report.  Please continue to report any other bugs you may
> find.
>
> ** Attachment removed: "CoreDump.gz"
>
> https://bugs.launchpad.net/bugs/1485154/+attachment/4445047/+files/CoreDump.gz
>
> ** Attachment removed: "Disassembly.txt"
>
> https://bugs.launchpad.net/bugs/1485154/+attachment/4445049/+files/Disassembly.txt
>
> ** Attachment removed: "ProcMaps.txt"
>
> https://bugs.launchpad.net/bugs/1485154/+attachment/4445050/+files/ProcMaps.txt
>
> ** Attachment removed: "ProcStatus.txt"
>
> https://bugs.launchpad.net/bugs/1485154/+attachment/4445051/+files/ProcStatus.txt
>
> ** Attachment removed: "Registers.txt"
>
> https://bugs.launchpad.net/bugs/1485154/+attachment/4445052/+files/Registers.txt
>
> ** Attachment removed: "Stacktrace.txt"
>
> https://bugs.launchpad.net/bugs/1485154/+attachment/4445053/+files/Stacktrace.txt
>
> ** Attachment removed: "ThreadStacktrace.txt"
>
> https://bugs.launchpad.net/bugs/1485154/+attachment/4445054/+files/ThreadStacktrace.txt
>
> ** This bug has been marked a duplicate of bug 936560
>    unity-2d-shell crashed with SIGSEGV
>
> ** Information type changed from Private to Public
>
> ** Tags removed: need-amd64-retrace
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1485154
>
> Title:
>   unity-2d-shell crashed with SIGSEGV
>
> Status in unity-2d package in Ubuntu:
>   New
>
> Bug description:
>   I was trying to close all my programs.
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 12.04
>   Package: unity-2d-shell 5.14.0-0ubuntu2
>   ProcVersionSignature: Ubuntu 3.2.0-89.127-generic 3.2.69
>   Uname: Linux 3.2.0-89-generic x86_64
>   ApportVersion: 2.0.1-0ubuntu17.9
>   Architecture: amd64
>   Date: Fri Aug 14 21:13:00 2015
>   ExecutablePath: /usr/bin/unity-2d-shell
>   InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
> (20120425)
>   MarkForUpload: True
>   ProcCmdline: unity-2d-shell
>   ProcEnviron:
>    PATH=(custom, no user)
>    LANG=en_US.UTF-8
>    SHELL=/bin/bash
>   SegvAnalysis:
>    Segfault happened at: 0x7fcfbbe09082:        testb  $0x4,(%rbx)
>    PC (0x7fcfbbe09082) ok
>    source "$0x4" ok
>    destination "(%rbx)" (0x6973273d65707974) not located in a known VMA
> region (needed writable region)!
>   SegvReason: writing unknown VMA
>   Signal: 11
>   SourcePackage: unity-2d
>   StacktraceTop:
>    ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4
>    ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4
>    ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4
>    ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4
>    ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
>   Title: unity-2d-shell crashed with SIGSEGV
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/1485154/+subscriptions
>