Comment 5 for bug 1152338

On Fri, Mar 8, 2013 at 1:19 AM, Ernest Boyd <email address hidden> wrote

Bug 1044002 appears to be a private bug and is therefore NOT accessible.

>
>
> On Thu, Mar 7, 2013 at 11:10 PM, Apport retracing service <
> <email address hidden>> wrote:
>
>> *** This bug is a duplicate of bug 1044002 ***
>> https://bugs.launchpad.net/bugs/1044002
>>
>> 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 #1044002, 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/1152338/+attachment/3562813/+files/CoreDump.gz
>>
>> ** Attachment removed: "Disassembly.txt"
>>
>> https://bugs.launchpad.net/bugs/1152338/+attachment/3562815/+files/Disassembly.txt
>>
>> ** Attachment removed: "ProcMaps.txt"
>>
>> https://bugs.launchpad.net/bugs/1152338/+attachment/3562817/+files/ProcMaps.txt
>>
>> ** Attachment removed: "ProcStatus.txt"
>>
>> https://bugs.launchpad.net/bugs/1152338/+attachment/3562818/+files/ProcStatus.txt
>>
>> ** Attachment removed: "Registers.txt"
>>
>> https://bugs.launchpad.net/bugs/1152338/+attachment/3562819/+files/Registers.txt
>>
>> ** Attachment removed: "Stacktrace.txt"
>>
>> https://bugs.launchpad.net/bugs/1152338/+attachment/3562821/+files/Stacktrace.txt
>>
>> ** Attachment removed: "ThreadStacktrace.txt"
>>
>> https://bugs.launchpad.net/bugs/1152338/+attachment/3562822/+files/ThreadStacktrace.txt
>>
>> ** This bug has been marked a duplicate of private bug 1044002
>>
>> ** Tags removed: need-amd64-retrace
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1152338
>>
>> Title:
>> evince crashed with SIGSEGV Following Ctrl-F
>>
>> Status in “evince” package in Ubuntu:
>> New
>>
>> Bug description:
>> 64-bit D07-1304 3.8.0-11-generic #20-Ubuntu SMP Tue Mar 5 20:32:48 UTC
>> 2013
>>
>> Open a PDF.
>> Prepare to search for text by pressing Control F
>> CRASH!
>>
>> ProblemType: Crash
>> DistroRelease: Ubuntu 13.04
>> Package: evince 3.6.1-1ubuntu3
>> ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
>> Uname: Linux 3.8.0-11-generic x86_64
>> ApportVersion: 2.9.1-0ubuntu1
>> Architecture: amd64
>> CrashCounter: 1
>> Date: Thu Mar 7 13:31:53 2013
>> ExecutablePath: /usr/bin/evince
>> InstallationDate: Installed on 2013-02-26 (9 days ago)
>> InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64
>> (20130225)
>> MarkForUpload: True
>> ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-11-generic
>> root=UUID=ee725bf1-d26e-498a-8cdb-1c14e1ec571f ro quiet splash vt.handoff=7
>> ProcEnviron:
>> PATH=(custom, no user)
>> XDG_RUNTIME_DIR=<set>
>> LANG=en_US.UTF-8
>> SHELL=/bin/bash
>> SegvAnalysis:
>> Segfault happened at: 0x7fa4c6d873e8: cmpq $0x0,0x30(%r12)
>> PC (0x7fa4c6d873e8) ok
>> source "$0x0" ok
>> destination "0x30(%r12)" (0x00000030) not located in a known VMA
>> region (needed writable region)!
>> Stack memory exhausted (SP below stack segment)
>> SegvReason: writing NULL VMA
>> Signal: 11
>> SourcePackage: evince
>> StacktraceTop:
>> ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
>> ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
>> ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
>> ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
>> ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
>> Title: evince 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/evince/+bug/1152338/+subscriptions
>>
>
>