evince crashed with SIGABRT in _recategorize_composite_operation()

Bug #939760 reported by Pavel Kukacka
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evince (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Evince crashed on Pangolin while opening large (24 MB) pdf file. Small files ( < 1 MB) are opened without problems.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: evince 3.3.90-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic i686
NonfreeKernelModules: fglrx
ApportVersion: 1.93-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Thu Feb 23 20:22:47 2012
ExecutablePath: /usr/bin/evince
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.2)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.2.0-17-generic root=UUID=d25463d9-c60d-4ac7-b4b3-5242216e80a4 ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: evince
StacktraceTop:
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /usr/lib/i386-linux-gnu/libcairo.so.2
Title: evince crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to precise on 2012-02-19 (3 days ago)
UserGroups: adm admin cdrom dialout lpadmin nopasswdlogin plugdev sambashare

Revision history for this message
Pavel Kukacka (pavel-kukacka) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __libc_message (do_abort=2, fmt=0x8a95f3c "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:201
 malloc_printerr (action=<optimized out>, str=<optimized out>, ptr=0x233cab48) at malloc.c:5007
 _recategorize_composite_operation (dst=0x233c9ea8, op=<optimized out>, src=0x0, src_attr=0x0, have_mask=1) at /build/buildd/cairo-1.10.2/src/cairo-xlib-surface.c:1982
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in evince (Ubuntu):
importance: Undecided → Medium
summary: - evince crashed with SIGABRT in raise()
+ evince crashed with SIGABRT in __libc_message()
tags: removed: need-i386-retrace
visibility: private → public
tags: removed: apparmor
summary: - evince crashed with SIGABRT in __libc_message()
+ evince crashed with SIGABRT in _recategorize_composite_operation()
Revision history for this message
penalvch (penalvch) wrote :

Pavel Kukacka, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please provide an example document that demonstrates this problem?

Changed in evince (Ubuntu):
status: New → Incomplete
Revision history for this message
Pavel Kukacka (pavel-kukacka) wrote : Re: [Bug 939760] Re: evince crashed with SIGABRT in _recategorize_composite_operation()

Hello Chris,

    not anymore, since I upgraded.

Cheers,
Pavel Kukačka

On Čt, 2014-12-18 at 01:21 +0000, Christopher M. Penalver wrote:
> Pavel Kukacka, this bug was reported a while ago and there hasn't been
> any activity in it recently. We were wondering if this is still an
> issue? If so, could you please provide an example document that
> demonstrates this problem?
>
> ** Changed in: evince (Ubuntu)
> Status: New => Incomplete
>

Revision history for this message
penalvch (penalvch) wrote :

Pavel Kukacka, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/evince/+bug/939760/comments/6 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in evince (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.