evince crashed with SIGSEGV in IA__g_closure_invoke()

[oli z]

Binary package hint: evince

Description: Ubuntu karmic (development branch)
Release: 9.10

evince:
  Installiert: 2.27.90-0ubuntu7
  Kandidat: 2.27.90-0ubuntu7
  Versions-Tabelle:
 *** 2.27.90-0ubuntu7 0
        500 http://de.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: amd64
Date: Mon Aug 31 21:09:18 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/evince
NonfreeKernelModules: wl
Package: evince 2.27.90-0ubuntu7
ProcCmdline: BOOT_IMAGE=/vmlinuz-2.6.31-9-generic root=/dev/mapper/hostname-root ro splash quiet splash
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-9.29-generic
SegvAnalysis:
 Segfault happened at: 0x7fa20aa2bae0: movsd (%r12),%xmm1
 PC (0x7fa20aa2bae0) ok
 source "(%r12)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%xmm1" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evince
StacktraceTop:
 ?? () from /usr/lib/libevview.so.1
 ?? () from /usr/lib/libevview.so.1
 ?? () from /usr/lib/libevview.so.1
 IA__g_closure_invoke (closure=0x22ce890,
 signal_emit_unlocked_R (node=0x22ce940,
Title: evince crashed with SIGSEGV in IA__g_closure_invoke()
Uname: Linux 2.6.31-9-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[oli z (oliver-z)]

i can't reproduce the problem because sometimes it occurs and then for some times it doesnt
is there any way without using gdb to get a backtrace? i dont want to always run gdb to work with evince

[Charlie Kravetz (cjkgeek)]

Since you reported this against a development version of Xubuntu Karmic and it lacks the information needed to investigate the problem, we are closing this report. If this can be reproduced using the latest development version of Xubuntu Lucid, please comment and change the status to 'new' in the yellow line.