Evince crashes after opening pdf

Bug #160539 reported by chefweb
4
Affects Status Importance Assigned to Milestone
libcairo
Fix Released
Unknown
libcairo (Ubuntu)
New
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evince

after open this pdf: http://rhw.ul.ie/universityarena/rates.pdf , evince is crashing.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in evince:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
chefweb (ulrich-timm-uni-rostock) wrote :
Download full text (4.9 KiB)

GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) set pagination 0
(gdb) run
Starting program: /usr/bin/evince
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1231190336 (LWP 12909)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging s...

Read more...

Revision history for this message
Pedro Villavicencio (pedro) wrote :

there's no crash in the trace, can you try again and attach the output to the report?

Revision history for this message
André Klitzing (misery) wrote :

Hi there,

I have another crash in evince with that file: http://www.bademeister.com/v7/pix/visions1107_opener.pdf
I attached the output of gdb. I have strace and valgrind output if you need it.

Revision history for this message
André Klitzing (misery) wrote :

well, some more debugging symbols...

Revision history for this message
André Klitzing (misery) wrote :

same happens with epdfview

Revision history for this message
André Klitzing (misery) wrote :

seems to be a cairo bug.
chefweb: Do you have the same crash?

Changed in evince:
status: Incomplete → New
Revision history for this message
chefweb (ulrich-timm-uni-rostock) wrote :

when I open evince on terminal and open the pdf, appears this message: " cairo context error: out of memory" ergo, seems like cairo bug!

Revision history for this message
André Klitzing (misery) wrote :

Yes, seems to be the same bug and should be fixed in cairo HEAD. (if you look into the bug comments of freedesktop's bugzilla)

Changed in libcairo:
status: Unknown → Confirmed
Changed in libcairo:
status: Confirmed → Fix Released
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.