evince crashed with SIGSEGV in _cairo_pattern_acquire_surfaces()

[Anton Blanchard]

Binary package hint: evince

I upgraded to karmic and can't view any pdf, evince always SEGV's. Probably a bug in cairo.

ProblemType: Crash
Architecture: i386
Date: Tue Sep 1 10:33:05 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/evince
KernLog:
 Aug 31 16:58:38 lister kernel: [429157.507571] type=1505 audit(1251701918.753:40): operation="profile_replace" pid=27545 name=/usr/lib/cups/backend/cups-pdf
 Aug 31 16:58:38 lister kernel: [429157.508890] type=1505 audit(1251701918.757:41): operation="profile_replace" pid=27545 name=/usr/sbin/cupsd
Package: evince 2.27.90-0ubuntu6
ProcCmdline: root=UUID=f2d836ea-975f-40ee-8b23-c58c9a1140c7 ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-7.27-generic
SegvAnalysis:
 Segfault happened at: 0xb49b61 <_cairo_pattern_acquire_surfaces+17>: mov 0x8(%edx),%eax
 PC (0x00b49b61) ok
 source "0x8(%edx)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evince
StacktraceTop:
 _cairo_pattern_acquire_surfaces (src=0x0, mask=0xb74b2594, dst=0x9b1bfb8,
 _cairo_image_surface_composite (op=CAIRO_OPERATOR_OVER,
 _cairo_surface_composite (op=CAIRO_OPERATOR_OVER, src=0x0,
 _clip_and_composite_with_mask (clip=<value optimized out>,
 _clip_and_composite (clip=<value optimized out>, op=CAIRO_OPERATOR_OVER,
Title: evince crashed with SIGSEGV in _cairo_pattern_acquire_surfaces()
Uname: Linux 2.6.31-7-generic i686
UserGroups: adm audio cdrom dialout dip fax floppy fuse plugdev scanner tape video

[Sebastien Bacher (seb128)]

Thank you for your bug report, it would be nice if you could send the bug to bugs.freedesktop.org since you are the only one to get the issue apparently and you can reply to questions there

[Anton Blanchard (anton-samba)]

This bug disappeared when I built it myself, and also after the next package update. I'm happy to close the bug since it sounds like it was an issue specific to my installation, perhaps some form of on disk corruption.

[dino99 (9d9)]

This version is outdated and no more supported