GNOME Bugzilla – Bug 563638
evince segmentation fault from pdf file
Last modified: 2008-12-08 23:01:06 UTC
Steps to reproduce: Unfortunately this crash is created with pdf articles from jstor which cannot be distributed. I have notified jstor of this bug and will ask if there is a way I can pass the file on. 1. Open pdf with evince (Document Viewer in ubuntu) 2. scroll down to 4th page or any page beyond. 3. program crashes Stack trace: I followed the directions for a stack trace but bug buddy does not come up. I don't know how to do it from here. Other information: This was reported originally on launchpad https://bugs.launchpad.net/ubuntu/+source/evince/+bug/306144. The report looks like this. "Binary package hint: evince I believe apport is going to attach information to this. Im running a 64bit 8.10 with Document Viewer 2.24.1 (i think this is evince) using poppler 0.8.7 (cairo). I have a pdf that crashes with a segmentation fault every time I scroll down to the 4th page. The article is from jstor, after reading the terms of service I don't believe I am allowed to upload it here. I could not find it anywhere else online. If anyone has access to jstor the article is Raising Rivals' Costs. Steven C. Salop and David T. Scheffman. The American Economic Review, Vol. 73, No. 2, Papers and Proceedings of the Ninety-Fifth Annual Meeting of the American Economic Association (May, 1983), pp. 267-271 Published by: American Economic Association. When opening the file in GIMP I get this GIMP Message: "Opening 'FILENAME.pdf' failed: Procedure 'file-pdf-load' returned no return values". I don't know what this means yet. I will try to report this upstream as it appears to be an upstream bug with evince. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 8.10 ExecutablePath: /usr/bin/evince Package: evince 2.24.1-0ubuntu1 ProcEnviron: SHELL=/bin/bash PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/gamusernames LANG=usernamen_US.UTF-8 SourcePackage: evince Uname: Linux 2.6.27-10-generic x86_64"
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance! http://live.gnome.org/GettingTraces/Details#gdb-not-yet-running has details on how to get a stacktrace with gdb if Bug Buddy isn't getting you one.
Created attachment 124212 [details] backtrace for evince I was able to follow the second link you provided to get a stack trace. Evince crashed differently when run through gdb instead of closing by disappearing it just froze by not responding. I had evince-gdb install but no other debug packages. If I can be of any use let me know.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 555375 ***