GNOME Bugzilla – Bug 408682
crash in Document Viewer: Loading a .PDF file.
Last modified: 2007-04-17 04:41:15 UTC
Version: 0.6.1 What were you doing when the application crashed? Loading a .PDF file. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 67010560 vsize: 0 resident: 67010560 share: 0 rss: 16687104 rss_rlim: 0 CPU usage: start_time: 1171652700 rtime: 0 utime: 70 stime: 0 cutime:58 cstime: 0 timeout: 12 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/evince' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1229609296 (LWP 17110)] [New Thread -1231635552 (LWP 17113)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 111316
Thread 1 (Thread -1229609296 (LWP 17110))
Thanks for the bug report. Unfortunately it lacks some information that may help us in finding the cause of the bug. Can you, if possible, attach the file causing the crash? Also this may be a Poppler Bug (the backend used by Evince to render PDF), could you please supply the poppler version and type? You can find it in the Help->About menu in Evince.
*** Bug 415586 has been marked as a duplicate of this bug. ***
The file causing the crash is too large to attach (2.5 MB), but can be found by going to http://princessauto.com/downloadz/ then once past the login (simple random number input verification), the file in question is the 'Surplus' section of the catalog choices listed. Additionally, I think a couple of the other files on that page cause the same problem. Opening the PDF in nano reveals in the header that it uses PDF encoding v1.4. Maybe that info could be useful too? Hope this all helps. If need be, I can e-mail the file directly to whomever requests it. Also, Poppler version is 0.5.4 (splash)
It's a poppler issue. I've just filed https://bugs.freedesktop.org/show_bug.cgi?id=10216. Thanks a lot for your help.
*** Bug 418308 has been marked as a duplicate of this bug. ***